# Phase `review` — comprehensive deferred verification

This phase adds **no new features**. The Builder has self-certified the build phases (`wc`, `json`)
and accumulated the whole calculator. Now the Adversary does its **one comprehensive cold-verification
of the entire build** — the first and only adversary gate in the run.

## Definition of Done

- **D1 — full cold re-verify.** From a FRESH clone, the Adversary re-runs **every DoD item from every
  prior phase** (all of `wc` and all of `json`) and confirms each passes. Nothing is taken on the
  Builder's word.
- **D2 — full suite green.** The complete test suite (`python -m unittest`) passes, 0 failures.
- **D3 — cross-feature break-it.** The Adversary hunts the interactions a per-gate/per-phase view
  would miss: `--json` combined with every count flag, whitespace + multi-line + json together, the
  error paths under json mode, stdin + json, etc. — and files any defects it finds.
- **D4 — findings cleared.** Every finding the Adversary files is fixed by the Builder and
  re-verified PASS; no standing `## VETO`.

## How it works

The Adversary records its comprehensive verdict in `machine-docs/REVIEW-review.md`
(`review(all): PASS`, or findings with repro). The Builder fixes anything found, then writes
`## DONE` to `machine-docs/STATUS-review.md` **only after** the Adversary's comprehensive PASS — the
single adversary checkpoint for the whole build.