reviewlisted

# Code Review The delta beyond an unstructured single-pass review is scope provenance, risk-adaptive lanes, evidence gates, bounded correction, and cold escalation. ## 1. Bind scope 1. Read `AGENTS.md` or `CLAUDE.md` when present. 2. Resolve the base from the PR, upstream, or merge-base; print the base and changed-file list. Never silently review the whole repository. 3. Read the issue, brief, or request that defines intent. If none exists, report `INTENT GAP` and infer only from the diff. 4. Check branch state and uncommitted changes; use history only to explain scope. ## 2. Choose the risk lane - **low:** local, reversible, with no trust boundary, persistent data, concurrency, public interface, generated contract, or production operation. - **medium:** shared behavior, multiple files, compatibility, or concurrency. - **high:** auth, secrets, money, permissions, migrations, destructive writes, production infrastructure, or unfamiliar costly behavior. Choose the lane from the diff and intent. Promote when the first pass reveals a risk trigger, candidate finding, coverage gap, or scope drift. ### Low-risk fast path Only in the low lane with explicit scope and intent: trace the changed path, match acceptance and branches to tests, and self-refute the likeliest defect. An `INTENT GAP` promotes rather than entering this fast path. If no finding, gap, or drift remains: Do not load review learnings; enumerate no lenses, print no empty scope-drift or cold-review fi