gate-adjudication-and-foldslisted

# Gate Adjudication and Folds Canonical verdict rules: `skills/cross-model-review/SKILL.md` (findings are claims, §3; the loop is bounded, §4). This file pins the adjudication patterns the 2026-07-29/30 campaigns used, each with its public record. On disagreement, the canon skill wins. ## Fold discipline - Reproduce a finding against the actual file/repo before folding it. - Fold commits are named `Fold gate rN: <what>` — single-PR campaigns prefix the target, e.g. `Fold #91 gate r1: …` — and state which lens produced each item and why the fix is right (see `6fa6154`, `5fa241b`, `83a038d`, `1560b97`). - Your own folds are attack surface for the NEXT round: #90's gate caught the staged-diff gate's circular trigger, a defect an earlier fold itself introduced (the catch is listed in #90's body; the fold-introduced attribution is session-recorded). Do not close on a round whose folds no lens has seen, except under the bounded-loop close below, where exactly that residual is disclosed by name. ## Rejections carry in-repo counter-evidence - A reviewer finding you reject gets a recorded counter-fact in the fold commit and PR body. #90's body records the aggregate — "7 findings rejected with in-repo counter-evidence"; the two worked examples below are session-recorded, their counter-facts re-derived in-repo 2026-07-30: - a lens called `→` a banned glyph — rejected by reading checks.py's banned class (invisible/bidi/Tag-Block only; U+2192 is not in i