close-worklisted

# Close The practitioner has decided a piece of work is over — delivered, or abandoned. Your job is to make that decision durable and complete, and then let the work disappear. ## Closure is theirs alone Never infer that work is finished. Never suggest closing anything, never ask whether they want to close something, never treat a merged PR, a passing test, an evaluation, or your own sense of completion as a reason to raise it. If they have not said to close it, there is nothing to do here. Closure needs nothing tidied first. Do not require a final summary, a resolved observation, a retrospective, or an evaluation. Do not raise new work items for anything left over — a loose end you noticed is not work. ## Confirm what will vanish, then close it Show them what is about to be archived — the item's files, so they can see nothing they care about is only there: ```sh ls -R .remit/<slug> ``` Ask whether any commit or pull request shipped this work. You may offer what the repository actually shows (`git log`, `gh pr list`) for them to confirm; never write a link they have not confirmed, and never invent one. Abandoned work has no links, and that is fine. ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" close <slug> <<'DELIVERY' - <commit or PR link, one per line, in their words> DELIVERY ``` With nothing to record, close it with empty input instead: ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" close <slug> < /dev/null ``` `remit` sets the item's state to c