closelisted

## Steps 1. **`pdkit close <issue> --json`** — the facts: what merged and when, which amendments happened, what the journal recorded as notable, which worktrees are still on disk. It re-reads every pull request the record still calls open before it answers. The merge happens in the browser, usually long after anything local last ran `pdkit pr refresh`, so the stale copy is the normal case rather than the exception — and this is the one command where believing it would end the issue in the wrong state. A read that could not be made is in `refreshFailed`, with how old the record it could not replace is. That is not a reason to stop: the facts on disk are still worth reading, and `--finish` refuses on a pull request whose state nobody could establish anyway. 2. **Check the rollup before anything else.** An issue is finished when *every* one of its pull requests has landed. One merged slice of three is not a finished issue, and a pull request the maintainer closed is unfinished work rather than finished work — that is the entry to the `redo` route, not the exit. `pdkit close --finish` refuses while anything is open, and it is right to. 3. **Harvest.** Read the facts and decide what belongs in `knowledge/`: - a trap that cost time and would cost it again (the `RunOptions` class of thing); - a review expectation nobody had written down; - a package boundary that turned out to be different from what the plan a