Current State — Codex Recheck 9 V2 FIX7 Packet Needs T1 Fix
Current State — Codex Recheck 9 V2 FIX7 Packet Needs T1 Fix
Status: CODEX_RECHECK_9_V2_NEEDS_T1_FIX
Production mutation: NO
N7/N8/P7: NOT SEALED
Blueprint approval: NOT AUTHORIZED
Packet V2 is KB-native and nominally reproducible: fresh governed-MCP reconstruction matched tree 21752e19c76f76613ba1680b734686c558a130e05d64dbc9eb5131b822fba480; RERUN passed; current real missing/extra/invalid/absent-dir CLI paths return 4 and suppress candidates; current canonicalizer SSOT rev3 bytes hash to candidate 49c386a9b9666c09786fc4f89bc79776b6046eaee6f4da6d8537d2c753b734d0.
Codex found one blocking evidence defect: the packet's negative tests do not execute the actual CLI exit contract. They synthesize cli_exit_contract=4 from function state. On a copied, self-consistently republished packet where the CLI error branch was changed to exit 0, full RERUN still passed and adversarial suite remained 22/22, while missing-doc actual CLI exited 0. Therefore R9-B1/R9-B3 and Article 14 remain open.
T1 must add actual CLI-exit execution/assertions for missing/extra/invalid/absent-dir and a fail-open-wrapper regression that forces RERUN failure, then route a fresh Codex rerun. No implementation or production action is authorized.
Full report: knowledge/dev/reports/architecture/codex-fix7-blueprint-recheck-9-v2-packet-rerun-and-seal-review-2026-06-10/00-readme-first.md