dispatch-1: record fleet goal, baseline, and first worker proposal

docs/TODO.md

@@ -1,8 +1,5 @@
 # TODO — what each area did NOT finish
 
-One section per area. Each session updates its own section before it stops: what is
-half-done, where it is, and what the next step is. Newest first inside a section.
+## dispatch
 
-## <area id>
-
-- YYYY-MM-DD: <what is unfinished> — <where (branch, file, SHA)> — next: <step>
+- 2026-10-19: dispatch-1 startup goal and one-worker proposal prepared. 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.

docs/agents/PROGRAM.md

@@ -1,30 +1,25 @@
 # Program — the owner's priorities and rulings
 
-Kept by the session manager. Short on purpose: the backlog holds the tasks, RESUME-BRIEF.md
-what is mid-flight. Every ruling is DATED and QUOTES the owner; session-manager calls are
-marked vetoable.
-
-Last updated: YYYY-MM-DD
+Last updated: 2026-10-19
 
 ## Current milestone
 
-TODO: one paragraph.
+Work through the existing TODO backlog and fix reproducible bugs that make the client less robust or usable. Validate old reports at current HEAD before assigning them; deliver small, checked changes through local unstable.
 
-## Priorities (owner's order)
+## Priorities
 
-1. TODO
-2. TODO
+1. Owner direction: TODO backlog progress, bug fixes, robustness, and usability.
+2. Session-manager sequencing (vetoable): prioritize reproducible failures in core user flows and small changes with clear completion checks.
 
 ## Rulings log (newest first)
 
-<!-- Format:
-### YYYY-MM-DD HH:MM — <short title>
-> "<the owner's exact words>" — owner
-Applies to: <areas>. Recorded by: <session>.
+### 2026-10-19 — Initial goal
+> "lets try to work our way through some of the issues in the TODO backlog and find and bugs and generaly make the client more robust and usable. ." — owner
+Applies to: all areas. Recorded by: dispatch.
 
-### YYYY-MM-DD HH:MM — <short title> (session manager call, VETOABLE)
-What was decided and why, in two lines. The owner overrides by saying so.
--->
+### 2026-10-19 — Conservative startup limits (session manager call, VETOABLE)
+
+No deploys, spending, production data, real-wallet operations, or scheduler activation. Present the first team for owner approval before starting workers.
 
 ## Standing rules
 

docs/agents/backlog/dispatch-1.json

@@ -0,0 +1,9 @@
+{
+ "id": "dispatch-1",
+ "area": "dispatch",
+ "status": "in-progress",
+ "title": "Record owner goal, establish baseline, and prepare first worker proposal",
+ "blockedOn": null,
+ "addedOn": "2026-10-19",
+ "filedAt": "d90591163f3db6ff99c1cfad6b736bbb1ee98a59"
+}