Environment for both captures: real web client in Chromium, 1280x800 CSS viewport, light theme, device scale factor 2. Real Claude provider; fresh separate worktree T3 homes, T3CODE_DEV_SEED=0 vp run dev. The same empty scratch git project and identical CLI prompt were used on both commits. Capture crops retain the conversation and remove private runtime metadata from surrounding UI. 1. Add scratch project through project add. 2. Start parent through thread start with the prompt in driver.py, using the same configured inexpensive provider model on both sides. 3. Parent delegates an app-owned child. Child starts unawaited sleep 25 and ends turn. Original task completes. 4. On background completion, child is woken and starts background sleep 900, calls t3_background_wait, then ends turn. 5. Read-only inspection confirms idle child provider thread with awaited pendingBackgroundTasks and a completed app-owned provider-continuation row on parent referencing that provider thread. 6. Open child conversation and start recording. Gracefully SIGTERM the confirmed server-port owner; trigger node --watch restart by touching src/bin.ts. Confirm shutdown reconciliation and recovery logs. Reload the same conversation after recovery. 7. Base: no restart notice or child continuation. Persisted roster empty, child idle, only runs 1 and 2, both without restartCancelledBackgroundWork. UI still shows its old Waiting row. 8. Head: restart notice appears; child resumes and acknowledges cancellation, then restarts its command. Run 2 carries restartCancelledBackgroundWork and subsequent runs exist. The commands were executed manually. driver.py provides the identical CLI prompt and a reusable automated version of the precondition checks and restart. inspect-state.py was executed against both real databases to produce the attached privacy-filtered state files. No tests or direct database writes were used. The two cropped screenshots were each compared against another capture taken more than 500ms later: zero differing pixels within each crop. Both screenshots and sampled frames throughout both recordings were opened and inspected before upload. AI-assisted; verified with the tests and tools listed above.