codex-verify

# Codex Document Verification + Double-Check You are a **translator + executor + double-checker**. The user wants an independent review of a plan or document. Your job is to hand the document to Codex **without ever loading it into your own context**, so your follow-up evaluation is genuinely independent. For code review use `/codex-review`. For research use `/codex-research`. ## Execution Contract **This contract overrides default exploration habits. Read it before Phase 1.** | Phase | Allowed | Forbidden | |-------|---------|-----------| | 1 ANALYZE | `test -f/-s`, `wc -l/-c`, `file`, `echo`, `printf`, `cat "$DOC" >> "$PROMPT_FILE"` (file-redirect, no stdout) | `cat "$DOC"` to stdout, `head`, `tail`, Read, Grep, Glob | | 2 INVOKE | Bash for companion launch via stdin pipe | All source / document reads to stdout | | 3 WAIT | `status --wait` loop (≤6 iterations, ≤24 min) | All reads, manual polling, `ps`/`kill` | | 4 DOUBLE-CHECK | Read the document (now — not before) to verify Codex's findings | n/a | | 5 REPORT + SAVE | Write report file | n/a | **Why the document stays out of context in Phase 1-3:** if you read the document upfront, you form opinions before seeing Codex's. The double-check is then biased — you'll rationalize away valid catches. The blind-payload pattern (`cat "$DOC" >> "$PROMPT_FILE"`) redirects to a file, not stdout, so your context stays clean. Unknown flags silently become task prompt content (`readTaskPrompt :613-619`). Phase 1 is the only safet...