thread-receiptlisted

# Close a thread Read [threads.md](../wiki/references/threads.md). Tools: `threads`, `thread`, and `status`, `route`, `plan`, `apply` for the knowledge base. 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. ## 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. Before `completed`: run the tests and the checks the plan names, now, and read the result. A thread does not complete on tests that fail or were not run. When the work sits on a branch, it merges after they pass. ## Write the receipt Call `thread` with `id`, `stage: receipt`, `outcome`, and the receipt as `text`: - **Completed:** what was delivered, in the user's terms; where it is (commits, files, pages); how it was verified, with the commands and the result; where the work left the spec or the plan, and why; what is left undone. - **Killed:** the reason, and what to keep from the work so far. Keep it short and exact. The earlier documents stay as they are: they are the record of how the thread went. The card moves to `threads/archive/`. Report the receipt's path. When the thread's phase is now finished, say so. ## What is left Work left undone is a new thread: offer a stub for each item, in the same phase, a