Record first pilot verification blocker and provider handover gate

docs/TODO.md

@@ -72,6 +72,12 @@ pilot reliability issues have also been added to the same backlog:
   handling instead of equating installed files with an operational timer.
 - [ ] `TASK-pilot-executor-outcomes`: zero exit plus timeout/error/signal cannot
   produce a successful lifecycle/wake receipt; qualify before automatic wakes.
+- [ ] `TASK-pilot-generated-check-artifacts`: retain exact-commit check artifacts
+  outside the tested tree and safely recover proven generated outputs so a gate
+  does not make the following required gate fail WORKTREE_DIRTY.
+- [ ] `TASK-provider-handover`: after release qualification, checkpoint and safely
+  switch one session then the fleet to reviewed Claude Code/Pi profiles; preserve
+  TORCH identity/tasks/messages but never reuse another harness's native session ID.
 
 ## First real self-host run (2026-09-30)
 

reports/audit/first-development-pilot-2026-09-30.md

@@ -81,6 +81,16 @@ issues were added through audited owner intake: starting presence, native unit
 rendering/operational status and executor timeout/outcome semantics. The manager
 backlog remains the authoritative queue, separate from this narrative report.
 
+Recovery follow-up: the specialist produced regression commit `2f1ca15` but exact
+TORCH check planning was blocked by five tracked report images generated by the
+dashboard gate. The owner/arbiter gave narrow reversible archive-and-restore
+directions for proven check-owned outputs, not permission to rewrite expectations.
+`TASK-pilot-generated-check-artifacts` records the durable fix. The explicitly
+requested post-quality-release whole-fleet provider migration now has its own
+`TASK-provider-handover`, dependent on release qualification. Total intake is
+39 items (34 original follow-ups plus five later pilot/handover items); one real
+implementation assignment does not imply the rest are dispatched.
+
 1. Finish diagnostics regression evidence and independent QA review.
 2. Fix executor outcome/launch-presence guards and qualify one real bounded wake.
 3. Complete reviewed automatic init/install onboarding and persistent operations.