docs: specify legacy slot migration rules
This commit is contained in:
1 parent
ee96f8d48b
commit
640e593676
1 file changed
+13
@@ -273,6 +273,19 @@ Migration builds new collections without dual canonical writes.
|
|||||||
boundary restores the historical Match default only when `gameMode` is absent or
|
boundary restores the historical Match default only when `gameMode` is absent or
|
||||||
`null`, mapping it to `pair`; an explicitly stored unknown mode remains
|
`null`, mapping it to `pair`; an explicitly stored unknown mode remains
|
||||||
quarantined instead of being guessed.
|
quarantined instead of being guessed.
|
||||||
|
- A persisted legacy round-robin `gameSchedule` is authoritative. Migration
|
||||||
|
normalizes it into explicit seed-based pairings on the Competition format so the
|
||||||
|
immutable Series graph reproduces the historical opponents and rounds instead of
|
||||||
|
generating a different canonical schedule. Matches without a persisted schedule
|
||||||
|
continue to use deterministic canonical round-robin generation.
|
||||||
|
- Legacy TournamentCode `gameNumber` is a global GameSlot number, not a Series
|
||||||
|
ordinal. Migration resolves it through accepted Riot evidence first, then the
|
||||||
|
persisted format topology (`gameSchedule` or double-elimination bracket layout),
|
||||||
|
and only uses canonical flattened graph order when no persisted topology exists.
|
||||||
|
- TournamentCode `bracketMatchId`, global `gameNumber`, Riot evidence, and resolved
|
||||||
|
Series/GameSlot must agree. A multi-slot Series is never assigned to its first
|
||||||
|
GameSlot as a fallback; missing, conflicting, duplicated, or out-of-range evidence
|
||||||
|
is quarantined without changing the legacy Match or TournamentCode.
|
||||||
- Dry-run is the default and emits machine-readable and human-readable reports.
|
- Dry-run is the default and emits machine-readable and human-readable reports.
|
||||||
- Apply is resumable, idempotent, transactionally scoped per Match, and verifies fact
|
- Apply is resumable, idempotent, transactionally scoped per Match, and verifies fact
|
||||||
replay equality after every write.
|
replay equality after every write.
|
||||||
|
|||||||
Reference in new issue
Block a user