Verify direct-dispatch v1 (#36) works end-to-end

## Goal Verify **direct-dispatch v1 (#36)** works end-to-end on real Solo agents before v2 (#104) is built — the operator-requested gate between v1 and v2. ## Depends on #36 (v1 must ship first) · Blocks #104 (v2 stays blocked until this passes) ## What to verify (v1 acceptance, exercised live — not just the faked test seam) 1. Brief-detail "Dispatch direct" lists a project's daemons grouped by worktree with correct liveness; only idle agents are selectable. 2. Selecting an idle agent + dispatching **pushes the brief packet into that agent's Solo process via solo-cli** and the agent actually receives + acts on it (the core v1 mechanism — verify the packet lands and wakes the idle agent). 3. A `direct` dispatch_request is recorded on the brief trace + dispatch history. 4. When an active orchestrator exists it receives the heads-up inbox message; when none exists (the motivating case) dispatch still works with no orchestrator. 5. Failure/edge behavior: agent not actually idle, solo-cli unreachable / `stale_discovery`, bad process id. ## Deliverable A pass/fail verification report on this brief covering the above, run on a REAL Solo agent. If issues are found, file them (feedback/bug) before v2 proceeds. ## Acceptance - Documented end-to-end verification of v1 on a live agent; an explicit pass so #104 can unblock. - `Brief: #103` trailer. ## Provenance Operator-requested middle verification gate (#36 answer, 2026-07-01). Depends on #36; blocks #104. Created + chained by flower-refine (2026-07-03).

Chained gate between #36 (direct-dispatch v1: direct-to-existing-idle-agent via solo-cli) and its v2. Verify v1 actually works end-to-end against real Solo agents before v2 is built. Blocked on #36. Per operator's #36 answer (2026-07-01): a middle brief to verify v1 works properly before v2 can be chained after it. Full spec via brief_update_spec.