pr-synclisted

The reviewer spent their time. This command exists so it does not have to be spent twice. ## Steps 1. **Read.** `pdkit pr refresh <k>` then `pdkit pr threads <k> --json`. What comes back is already sorted mechanically: who is a bot, which file and slice each thread belongs to, which task owns that file, which requirement that task satisfies. None of it is classified — that part is yours. **Do not stop at threads.** The output includes review submissions and top-level comments, and on a stale pull request that is usually where the blocking feedback is. #17577 has two open threads, both a bot's, while the reason it is stuck is a four-line `CHANGES_REQUESTED` body. 2. **Bots.** Collapsed to one line with a link, never dropped. A thread the escalation words expanded is read in full, like a person's. If a collapsed line looks like it might matter, open the link: collapsing is about attention, not a decision that it was worthless. 3. **Classify each open item**, and say which it is: - `accept` — we change something; - `discuss` — an answer, not a change; - `defer` — a separate issue, and **record it**: ``` pdkit defer new --issue <n> --pr <k> --raised-by <who> --what "<what was set aside>" --url <comment> ``` Saying "we will open an issue for that" in a reply and leaving it there is how the promise ends up existing only on GitHub, on a pull request that is about to merge. The command writes it to the jour