From 77122fed8e7bca1afdccd6ae42e1cf00cb45a1bb Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN Date: Sat, 3 Oct 2026 18:11:08 -0400 Subject: [PATCH] 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. --- docs/TEST_INTEGRITY.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/TEST_INTEGRITY.md b/docs/TEST_INTEGRITY.md index 19deb55..9051c12 100644 --- a/docs/TEST_INTEGRITY.md +++ b/docs/TEST_INTEGRITY.md @@ -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: