remit-closelisted

# Close The practitioner has ruled a piece of work over. Closure is theirs alone: never infer it, never raise it, and never read a merged pull request or a green suite as a reason to. Show them what their ruling covers first — every finding still without a disposition is sealed by closure as pre-authorised: ```sh grep -n '^- finding ' .remit/work-items/<slug>/log.md ``` Read that list to them plainly, with no recommendation. Then ask whether any commit or pull request shipped the work, offering what the repository actually shows — never a link they have not confirmed. Abandoned work has no links, and that is fine. ## The command ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" close <slug> <<'DELIVERY' - <a link they confirmed, one per line> DELIVERY ``` With nothing to record, close with empty input: `... close <slug> < /dev/null`. ## Report it, and then it is gone Report what it printed, verbatim in substance. Exit 3: committed here, NOT accepted by the remote — say so; the item is closed either way. Exit 2: nothing changed. Exit 4: the close escalated; the item's `log.md` carries the reason, and that turn asks them to rule. Closure is final: the item leaves every listing and nothing about it returns as an instruction, a reminder, or an account of current behaviour. If a constraint from the work still governs the software, it belongs in the code — a test, a name, a comment; say that once. When they deliberately ask for closed work, read it from `.remit/work-i