TASK-f40126ee: clarify replay spec correction

Record why stale revision CAS, rather than a generic post-state refusal, is the first observable loser boundary in the controlling replay scenario.
This commit is contained in:
thePR0M3TH3AN committed 2026-10-03 18:11:08 -04:00
1 parent 4a5f3d0c94
commit 77122fed8e
1 file changed
+2
+2
View File
@@ -3233,6 +3233,8 @@ test_integrity_note:
observable_outcomes:
- "The replay loser reports the stale journal-revision boundary, not a generic post-state refusal"
- "Exactly one private-ref integration request and requested audit transition exist"
spec_correction_basis:
- "The former ADOPTION_REQUEST_STATE_INVALID replay expectation was wrong: after the serialized winner commits, the loser carries an obsolete journal revision, so revision CAS is the first observable refusal boundary under SCN-integration-adoption-request-replay."
determinism_controls:
- "Two independently opened local API processes over disposable Git and SQLite fixture state"
anti_cheat_rationale: