remit-resumelisted

# Resume The practitioner has said an item may move. Run one command, report where it stopped and why, and stop there yourself. ```sh sh "$(git rev-parse --show-toplevel)/bin/remit" resume <slug> [--until refined|accepted|closed [--park]] ``` Give `--until` only when they named a stop just now. Parking outright and ending a running chain are their own commands — `park <slug>` and `stop <slug>`. `resume` is also the one verb that continues a `crashed` row. The command runs the chain — nothing in it is yours to perform, brief, sequence or repeat, and no step of it happens in this conversation. It raises real fresh contexts and takes minutes to hours: run it backgrounded, the way AGENTS.md's session rules say every raise is run. ## The leave line Before the run takes you away, say one line, written fresh in your own words: that you have what you need, the work in a few words, and a rounded-up duration — then nothing at all until the run comes back. Read the estimate from the record, never invent it: the `- raise:` lines in items' `log.md` files (`bin/remit`'s header fixes that line's fields) say what runs of the same kind actually took. Round up; where the record holds nothing comparable, say plainly that you will report when it is done. ## Report what it printed Report the row and the reason verbatim in substance. Exit 0: it stopped where it was told to; that is the design working, and there is nothing to add — no reading of your own on whether it should have gone furth