dispatch-2: record verified worker launch and preserved local preview

docs/TODO.md

@@ -4,8 +4,8 @@
 
 - 2026-10-19: dispatch-1 startup goal and one-worker proposal landed at fa538097; preparation complete. Baseline at d9059116: lint 11/11, unit run completed 219 files before profile-modal suite timed out at 60s; isolated unrestricted rerun reproduced timeout; 205 files remain untested. fleet/TEAM-PROPOSAL.md proposes one client-reliability worker for this blocker, with queued torrent-probe lifetime as a later candidate. Await first-worker approval before adding/launching it. No product edits or workers started.
 
-- 2026-10-19: dispatch-2: first worker approved through desktop-chat relay, routine local work authorized within GOAL. Prepare/land client-reliability roster and launch through tmux, preserving fleet-bitvid:preview on port 3000. A clean NODE_TEST_CONTEXT-free isolated reproduction also timed out at 60s; one-time roster-only validation is recorded in PROGRAM.md. No product fixes landed yet.
+- 2026-10-19: dispatch-2: first worker approved through desktop-chat relay, routine local work authorized within GOAL. Roster landed at 9e6c310d and client-reliability worker launched in its own tmux window (pid 138193); fleet-bitvid:preview on port 3000 preserved (HTTP 200). Next: monitor blocker/fix evidence, normal landings, and refresh preview after verified product changes. A clean NODE_TEST_CONTEXT-free isolated reproduction also timed out at 60s; one-time roster-only validation is recorded in PROGRAM.md. No product fixes landed yet.
 
 ## client-reliability
 
-- 2026-10-19: client-reliability-1 assigned: reproduce/classify and fix profile-modal suite hang without weakening assertions. Initial evidence: two isolated 60s timeouts (one clean environment), full baseline stopped at file 220/425; read docs/agents/prompts/client-reliability.md and claim the item. Scope excludes app.js and unrelated subsystems.
+- 2026-10-19: client-reliability-1 assigned: reproduce/classify and fix profile-modal suite hang without weakening assertions. Initial evidence: three isolated 60s timeouts (one clean environment), full baseline stopped at file 220/425; read docs/agents/prompts/client-reliability.md and claim the item. Scope excludes app.js and unrelated subsystems.

docs/agents/RESUME-BRIEF.md

@@ -8,8 +8,8 @@ Read fleet/GOAL.md and PROGRAM.md. Robustness/usability/TODO work is authorized.
 
 | area | item | state | next step |
 | --- | --- | --- | --- |
-| dispatch | dispatch-2 | roster preparation | verify administrative-only landing, create worktree and launch exactly one worker; report through owner mailbox |
-| client-reliability | client-reliability-1 | approved, not yet launched | classify/fix reproducible profile-modal suite timeout, preserve assertions, mutation-check regression and run full gates |
+| dispatch | dispatch-2 | active coordination | roster landed 9e6c310d; one worker running; monitor results, owner updates, and preview refresh |
+| client-reliability | client-reliability-1 | running in fleet-bitvid:client-reliability | classify/fix reproducible profile-modal suite timeout, preserve assertions, mutation-check regression and run full gates |
 
 ## Evidence and local preview
 

fleet/LOG.md

@@ -16,3 +16,6 @@
 - Received desktop-chat relay of owner quote "yes please approve whatever it wants and let me know about it" and explicit scoped authority for routine staffing, fixes, tests/builds, backlog priorities, and local unstable landings. Provenance recorded; not represented as human terminal input. Existing deploy/spending/production-data/wallet/scheduler limits retained.
 - One client-reliability Codex worker registered, focused on client-reliability-1 profile-modal hang. No other workers. Preview confirmed in fleet-bitvid:preview, built dist at 127.0.0.1:3000; preserve its process.
 - Clean-env isolated profile-modal run reproduced the 60s timeout (exit 1). Bootstrap roster-only gate exception recorded to avoid requiring a hang fix before its assigned worker can launch; product/test/persistent-gate changes forbidden in this exception.
+
+- Launch verified: fleet status reports client-reliability running pid 138193; tmux pane shows it reading rules/backlog. Team: 2 agents total, 1 worker. Roster landed at 9e6c310d (durable landed state and git log unstable). Exact bootstrap validator passed for 13 files, product/tests/persistent gate settings unchanged; normal configuration remains active for future landings. Owner launch update sent.
+- Preview check: HTTP 200 at http://127.0.0.1:3000; existing built-dist process preserved. No product changes to rebuild yet. No scheduler or additional worker activation.

test_logs/TEST_LOG_2026-10-19_20-02-49_dispatch-worker-launch.md

@@ -0,0 +1,10 @@
+# Worker launch verification
+
+- Staffing commit 3514c057, merged tip c3123991; temporary exact-scope validator: exit 0, 13 expected files, no product/test/persistent gate changes.
+- Queue durable status: c3123991 landed as 9e6c310d; `git log -1 unstable` confirms 9e6c310d. No full-suite pass claimed by administrative landing.
+- `fleet worktrees --only client-reliability`: exit 0, created isolated branch/worktree at landed roster.
+- `env -u NODE_TEST_CONTEXT fleet up --only client-reliability`: exit 0; own tmux window created. No scheduler activation.
+- `fleet status` plus pane capture: client-reliability running pid 138193 and reading rules/backlog; actual model shown GPT-6.1-Sol medium from project default.
+- Local preview request http://127.0.0.1:3000: HTTP 200, process preserved. No product edits, so no rebuild required for this staffing change.
+- Owner launch event sent through owner mailbox. Team 2 agents including dispatch, 1 worker.
+- Not verified: hang root cause/fix, remaining unit files, browser behavior, real signers, or production/release qualification.