legion-simplify

Run the legion-simplify review on `git diff main...HEAD`, write a markdown articulation with one entry per changed file, then record it with `legion quality-gate check`. A clean recorded gate lets `legion pr create` proceed.

The review checks for duplicate logic, unnecessary abstraction, stringly-typed state, hand-rolled helpers duplicating std utilities, unnecessary parameters, copy-paste variations, error swallowing, and change-narrating comments. Style preferences and pre-existing issues outside the diff are explicitly not flagged.

Refusals happen when a changed file lacks an entry, an entry is under roughly 12 words, or the prose cites no within-file locator such as a file:line, line number, symbol, or Evidence line. Headings must also match git's reported paths byte-for-byte.

No. Passing `--findings-json` together with `--result clean` is refused. A clean verdict also requires that no prior HIGH/MED finding on the branch is still pending and no prior LOW finding remains un-acked.

Findings auto-resolve when a later commit touches the flagged file, or you can disposition one with `finding-disposition` and a reason, or batch-ack LOW findings with `finding-ack`. Use `finding-list` to see pending finding IDs for the branch.

The validator checks structure only: file coverage, minimum word count, and the presence of a locator. It cannot judge whether the reasoning is correct, so a plausible-sounding but wrong verdict can still pass; review quality remains the reviewer's responsibility.