review-looplisted

# Review Loop ## Objective Find material problems, resolve or adjudicate them, and reach an honest stopping point without turning review into an endless search for minor novelty. Keep the reviewed artifact, evidence epoch, scope, and claim ceiling explicit. Read `references/evidence-and-state.md` when creating review state, findings, coverage, convergence, or final-gate records. ## Choose one mode 1. **`companion-preflight`** — one read-only orientation pass before another skill asks questions or edits. Return structure, risks, unknowns, evidence gaps, and only consequential questions. 2. **`review-only`** — inspect and adjudicate without modifying the artifact. Convergence still requires two clean passes over one frozen epoch. 3. **`improve`** — review, create a verified backup, apply the smallest authorized fix, verify it, and review the new epoch again. 4. **`final-gate`** — freeze the candidate and evidence, then decide whether the stated claim is supported. Do not silently modify the candidate; reopen `improve` mode if a fix is required. If the user does not name a mode, use `companion-preflight` before a build and `final-gate` before completion; use `improve` only when the request authorizes changes. ## Automatic entry protocol 1. Restate the intended outcome in one sentence. 2. Identify the artifact, authority, privacy/licence boundary, current candidate, protected surfaces, and permitted actions. 3. Inspect available files, structure, tests, history, and evide