remit-reviewlisted

# Review The standing findings are what the last verdict at each gate still carried with no disposition — read from the verdicts, so a closed item's seal changes nothing. Run the one that matches what they asked: ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" review # every item sh "$(git rev-parse --show-toplevel)/bin/remit" review today # or yesterday, week sh "$(git rev-parse --show-toplevel)/bin/remit" review since <YYYY-MM-DD> sh "$(git rev-parse --show-toplevel)/bin/remit" review <slug> [<slug>...] ``` Report the rows verbatim in substance — item, stage, gate, verdict date, finding number, the finding's first line, and the delivery it stood against — and stop. If it prints nothing, say nothing is standing in that window. No ranking, no triage, no proposal: a standing finding is a fact the record holds, and what becomes of it is theirs. ## When they say "attest" Only on their word. This raises ONE fresh context, in the primary worktree at HEAD, to say of each standing finding whether it still stands, is fixed, or is moot — and records what it said on every item's `log.md`, the archive included. Run it as a backgrounded task of your own harness with a generous explicit timeout, exactly as a resume is run: ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" review [<window> | <slug>...] --attest ``` Its stdout is the rows, then the count per category. Give them that turn in the shape `AGENTS.md` fixes for a turn that asks them to