fix: normalize reused tournament code lifecycle
This commit is contained in:
1 parent
6b1c450752
commit
489d040d8f
3 files changed
+188
-21
No files matched your search
@@ -295,6 +295,12 @@ Migration builds new collections without dual canonical writes.
|
||||
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.
|
||||
- TournamentCode pool documents may retain timestamps from an earlier binding after
|
||||
reuse. Migration preserves only the lifecycle reachable from the current state
|
||||
(`reserved`, `used`, `released`, or `voided`) and validates that current lifecycle;
|
||||
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.
|
||||
- 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