two-lens-review

# two-lens-review (v1.1) — the review gate + the whole-codebase audit ONE protocol, two SCOPES over the SAME factors: - **Diff scope** — the repo's **mandatory** merge gate ("Don't merge a PR without the two-lens review" — workspace `CLAUDE.md`, "Things NOT to do"; PR #23 merged unreviewed with a critical path-traversal). 2+ differentiated-lens agents on the diff, disposition in the PR thread. - **Whole-codebase scope** — the periodic / pre-release AUDIT. A diff review and an audit scan DIFFERENT populations (fix-introduced-in-one-change vs existing code + cross-PR accumulation), so the audit is a SEPARATE pass, not a bigger PR review — but it runs the same factors, verify contract, and disposition. The factors, the fill-in-the-slots lens briefs, the five hard requirements, the escalation triggers, AND the whole-codebase fan-out orchestration are all canonical in [`.github/prompts/pr-review.prompt.md`](../../../.github/prompts/pr-review.prompt.md) — **read it; fill from THAT file, never a paraphrase here** (a copy here is the exact two-copies-drift class Lens 2 hunts — when the prompt gains a factor or trigger, a copy here silently lags). This skill owns only *when* to invoke each scope, *how* to orchestrate, and the red-flag self-checks. ## When to use **Diff scope:** - Before merging any PR (no exceptions — it's the gate, not a nicety; no size exemption — lens count can shrink, the gate can't). - User says "review this branch/PR", "two-lens review", "is t...