fresh-eyeslisted

# fresh-eyes Audit a finished diff with fresh eyes. The mechanism is **double-blind reconciliation**: a subagent that never saw the conversation reads the diff blind and reports what it *thinks* the change does. The main context — which holds the real intent — compares that blind read against what the work was meant to do. The divergence is the signal. Not *only* a bug-hunt. The primary lens is completeness and intent — did the change do what it was meant to, fully. Catching bugs and oversights is a secondary byproduct of that check, welcome but not the goal. For a dedicated correctness sweep, use `/code-review` or `/codex review` instead. ## Workflow Run these steps in order. Do not skip step 1 — it is the integrity gate. 1. **Pre-register intent (BEFORE any review).** Write down, in the conversation, a short brief: *what we set out to do, what is in scope, what is out of scope.* This must happen before reading the blind report, or the main context will rationalize the blind read into false agreement and the signal is lost. Show it to the user. 2. **Capture the change to audit.** Try these sources in order; use the first that yields a non-empty change: - **Override arg** (if given): a commit range, `--staged`, or an explicit path. - **Git, uncommitted:** working changes exist → `git diff HEAD`. - **Git, branch vs base:** no uncommitted changes → `git diff <base>...HEAD`, where `<base>` is the repo's default branch (resolve via `git symbol