Fleet ## Parent

[Jhazy33]

Parent

#1 (fleet spec)

What to build

The app's root renders through the machines registry instead of a single daemon hookup, with single-machine behaviour unchanged. Root/Pew2 gate on the pairings store (zero machines → pairing screen), the active machine drives the existing screen, and switching machines swaps the conversation list. The active machine dropping mid-conversation leaves the composer read-only with the existing offline treatment plus a banner. Demoable: the app works exactly as today with one machine paired; with two, switching active machines swaps conversations.

Acceptance criteria

• Zero machines → pairing screen; ≥1 machine → main screen (parity with today's single-machine gate)
• Single-machine flow unchanged (existing tests green)
• Switching active machine swaps conversation list, projects, and composer target
• Active machine drop mid-conversation: composer read-only + banner; queued drafts deliver on reconnect
• Typecheck, tests, lint green

Blocked by

• Fleet ## Parent #5 (machines-registry) — wiring rides the registry