R2i: withdraw the release-mode word cap — the premise was retracted
R16g/R16f-repro: confirm a block a second way; a number carries its reproduction
R1e: reconcile with what a reviewer said, not with the fact that they approved
R2i: release-gate mode — shorter cap on a short diff, same measurement bar
R18d: a dep list that names a proxy, not the trigger
STEP 7c2: grep the diff for the fix you are about to ask for; R1e becomes a gate
R1e: read any existing review, not only when the author responded
Pre-release debt register: what we owe before a version is cut 11 items, 4 blocking. Linked from Home and Reviews.
R21: stacked PRs merge through merge-async
R1g: changed meaning and wrong mechanism are exceptions too; R30 cites the working sibling
R30: find the interaction decision the findings are children of
Record 2026-08-23: five reviews + the retrospective on where today's seven rules came from
STEP 7: the three checks the critic keeps failing; stock spawn prompt
R29: name each unrecorded change with its line — a count is not actionable
R29: plural problems are fine; unrecorded ones are the failure
R29: when the verdict is split, the closing ask is the split
R29: the PROBLEM statement is the boundary — a solution outside it needs its own PR
R29 calibration: count runtime decisions; size is its own signal. USAGE slot + enumerated SOLUTION in the brief
R29: split by decision count, not line count
R1j: an unjustified change is a finding even when nothing measurably breaks
R18e/R18f: price the render pass an effect costs; scope listeners to the moment
Aged-PRs: #4083 merged as 94c2d8b; drop its Ledger row
R2g: an inline names the problem and points at the pattern
R6e: a superseded PR's leftovers need a user, not just a difference
Aged PRs: reconcile 17 stale rows with posted reviews; ledger the 16 re-reviewed
PROBLEM is a user-facing failure; the absence of a mechanism is never a problem
R28: walk the use case end to end — a mechanism that cannot complete it is a different feature wearing its motivation
R28: establish the need before the mechanism; decide the category not the instance
Ruling 7 withdrawn: two problems, one is a bug to fix and the other is not a contract
R3j: if the component can apply it, exposing it is the finding — and it found the missing start alignment