# Documentation proof driver

Compared base b883156e269de2002873aebdef6019f336b687a7 with head 316f40749392d33b72a243cd36504265c6e3c5e1.

1. Install each checkout with `vp i` and start each separately with `T3CODE_DEV_SEED=0 vp run dev`, using its own fresh `.t3` state.
2. Seed each through the CLI commands in seed.sh. The only thread is a synthetic replay of “Read cancellation documentation”. No live database is copied.
3. Pair the browser with that development server, then open the returned thread. Wait for “first fixture turn complete”.
4. In the real web app, press Ctrl+P. Type `orchestrator-mcp-server`, wait for the matching option, then press Enter.
5. Click Show rendered markdown, Maximize panel, and Hide file explorer. Hide the main sidebar. Scroll the `task_cancel` heading to the top of the document viewport.
6. Use the same light theme and 1280×800 CSS viewport, device scale 2 (2560×1600 PNG), on both sides. No content or styling is injected.
7. Take two stills at least 500 ms apart and compare pixels. Keep a capture only when the difference is zero. Open and inspect both retained PNGs before uploading.

Observed before: “A nonterminal task with no interruptible run is rejected.” The paragraph omits queued-only cancellation and waiting/orphan exceptions.

Observed after: the task's own queued turn is cancelled even when held, unrelated queued prompts remain held for Resume, rejection accounts for outstanding child work, and orphaned follow-ups are reported cancelled.

This is static documentation evidence, not a claim that task_cancel runtime behavior changed. No runtime cancellation turn was needed or claimed.

AI-assisted; verified with the tests and tools listed above.