review

# procoder:review Review the diff. Every rung must hold before it ships. ## Procedure 1. **Get the diff.** `git diff --stat HEAD` for scope; `git diff HEAD` for content. If nothing is uncommitted, review `git diff origin/main...HEAD` instead and say which range you reviewed. If `$ARGUMENTS` named a range or path, use that. 2. **Read what the diff claimed to do**, before judging how it does it: the commit message, the PR body, the task, or the request that produced it. Then name the two gaps, both of which are findings: - behavior in the diff that the stated goal does not ask for — a renamed symbol nobody asked to rename, a second fix riding along, a default quietly changed; - a part of the stated goal the diff does not deliver. Report either as `[2 TRUE]` with `(scope)` before the message. Code that is correct and does something other than what was asked is the failure mode of generated diffs, and no other rung looks for it. 3. **Run the engine.** `node <plugin>/bin/procoder.js check <changed files>`. These findings are deterministic — report them verbatim, in the order given. Do not re-derive by eye what the engine already computed, and do not omit a finding because it looks minor. The engine exits 1 when a finding blocks at the active level; that alone blocks the ship. It exits 0 at `pragmatic` when only OBVIOUS and ALONE findings remain — still report them, as advisory. 4. **Read the diff for what the engine cannot se...