thread-receiptlisted

# Close a thread The receipt is the record of how the thread ended. A thread may close from any stage: a stub that was never worth doing gets a receipt as much as a feature that shipped. Tools: `status`, `threads`, `thread`. Reads [threads.md](../thread/references/threads.md). Sends the `thread-review` agent. ## Decide the outcome Call `threads` with the `id` and read the documents. `completed` means the spec's definition of done holds, or the plan's when there is no spec. `killed` means the work stops for good. Ask when it is unclear. ## Verify before completed 1. **Run the checks.** The tests and every check the plan names, now, and read the result. A thread does not complete on tests that fail or were not run. 2. **Review the work.** When the thread changed code, send the `thread-review` agent: a fresh reader with the spec, the plan, and the range of commits the work made (`git log` since the plan was filed, or the branch). It reports what the work misses from the spec, what it breaks, and what it leaves untested, each with the file and line. In a host without workers, do the same read yourself, as a reviewer who did not write the code. 3. **Act on it.** A finding that is right and small is fixed now, in its own commit, and the checks run again. A finding that is right and large goes back to `thread-run`, and the thread stays open. A finding you reject gets a reason in the receipt. When the work sits on a branch, it merges after the