fix: recover legacy tournament code transitions
This commit is contained in:
1 parent
489d040d8f
commit
ef47de7e4f
5 files changed
+775
-5
No files matched your search
@@ -301,6 +301,19 @@ Migration builds new collections without dual canonical writes.
|
||||
stale timestamps from a previous binding are not copied into the new assignment.
|
||||
Riot match identity is likewise carried only for the current `used` or `voided`
|
||||
binding, never from a restored `reserved` or `released` pool document.
|
||||
- Historical result collection and repair paths stored Riot occurrence time (archive
|
||||
game end/game creation, or game creation plus duration) in legacy `usedAt`, whereas
|
||||
Competition assignments define `usedAt` as the persisted state-transition time.
|
||||
Migration maps recognized legacy occurrence values to `TournamentCode.updatedAt`
|
||||
for every `used` assignment only when an archive-backed accepted game has the same
|
||||
Riot identity and
|
||||
`max(reservedAt, original usedAt) <= updatedAt <= fact.recordedAt`. This also
|
||||
safely covers post-game attachment where legacy `usedAt < reservedAt`. Source
|
||||
values, evidence strategy, slot identity, and normalized time are emitted as an
|
||||
audit warning. A recognized occurrence value without a valid persisted transition,
|
||||
and any uncorroborated inverted lifecycle, remains quarantined. A chronological
|
||||
`usedAt` that does not match a known occurrence encoding continues through the
|
||||
ordinary lifecycle validation because it may already represent transition time.
|
||||
- Dry-run is the default and emits machine-readable and human-readable reports. Every
|
||||
ready/apply result includes a deterministic `planHash` over the graph, facts, and
|
||||
TournamentCode targets so audits detect target changes even when counts stay equal.
|
||||
|
||||
Reference in new issue
Block a user