fix: normalize missing legacy match game mode

This commit is contained in:
dahyeon committed 2026-07-13 03:13:28 +00:00
1 parent 683d602d63
commit ee96f8d48b
3 files changed
+66

No files matched your search

+7
View File
@@ -269,6 +269,10 @@ Migration builds new collections without dual canonical writes.
- Ambiguous mappings, evidence conflicts, or already-played invalid descendants are
quarantined.
- Legacy `bracket` format becomes `paired-series` with a warning.
- Native Mongo migration reads do not receive Mongoose defaults. The hydration
boundary restores the historical Match default only when `gameMode` is absent or
`null`, mapping it to `pair`; an explicitly stored unknown mode remains
quarantined instead of being guessed.
- Dry-run is the default and emits machine-readable and human-readable reports.
- Apply is resumable, idempotent, transactionally scoped per Match, and verifies fact
replay equality after every write.
@@ -361,6 +365,9 @@ its `teamId` in the same object.
- Double-elimination seeds are persisted before the finalized team-build timestamp is
exposed, and an expired reserved code can be provisioned again automatically.
- Migration dry-run reports zero unclassified documents before apply.
- Historical Matches without a persisted `gameMode` plan as `paired-series`, while
an explicitly invalid legacy mode is still reported as
`UNSUPPORTED_LEGACY_GAME_MODE`.
- Competition unique/partial indexes are verified before the first apply write, and
repeated limited apply runs advance without rescanning the first page.
- API tests and API/web production builds pass.