Status: PASS / LIVE_FAIL_CLOSED / PRODUCTION_NO_GO

Date: 2026-08-29 UTC.

The live relay had advanced to R8-SCOPED-DEVICE-TOKENS, but acceptance_selftest.ts and README.md still described the older R4/R5/R6 contract.

The stale self-test rejected the healthy R8 runtime with ACCEPTANCE_RUNTIME_REVISION_MISMATCH. This was a test/documentation drift defect, not evidence of a runtime failure.

The self-test now validates the active V2 acceptance contract:

• exact runtime R8-SCOPED-DEVICE-TOKENS;
• V1 explicitly superseded by V2;
• V2 unauthenticated access rejected;
• exact V2 challenge id and SHA-256;
• current R8 capability set;
• deadline-related fail-closed states;
• no false PASS without mechanical checks and final GPT ACK;
• V2 lane state readable;
• audit hash chain valid;
• production_go=false.

The README now describes R8 scoped device tokens, launcher v2.4, exact current hashes, active V2 acceptance, the real Codex execution evidence contract and the separate dedicated R2 authorizer boundary.

Branch self-test evaluation:

01a04b9f-0860-7438-80e2-67b91515b82d

Result: PASS.

Observed:

• runtime: R8-SCOPED-DEVICE-TOKENS
• unauthenticated V2 acceptance: 401
• V1 state: SUPERSEDED_BY_CODEX_REAL_RUNTIME_ACCEPTANCE_V2
• V2 state: PENDING_CODEX_ACK
• mechanical checks: false
• lane revision: 1
• lane checkpoint SHA-256: 946af2f769106a1da7cdeef6d3f98d3983a682805e2617c4a42e25f28aea607a
• audit chain: PASS
• production_go: false

This reconciliation fixes stale verification and documentation. It does not synthesize a Codex ACK, does not authorize merge/deployment, and does not change product production state.