Fleet ## Parent

[Jhazy33]

Parent

#1 (fleet spec)

What to build

Notifications are per-machine end to end. Titles carry the machine name ("[Mac mini] Claude finished…"), taps route by machine id to that machine + conversation, and a notification with no machine id (old daemon) resolves by session id across machines — else opens the machine list, never a wrong conversation. The push token registers with every daemon on every successful pairing and re-registers on token rotation. Near-simultaneous notifications about the same event from different machines collapse into one via cross-machine dedupe in the existing pure notification policy. Demoable: two daemons finishing near-simultaneously produce one notification each (or one, when the same event), titled per machine, and taps land correctly.

Acceptance criteria

• Titles: "[Machine] …"; ADR 0006 leak accepted and noted in the rename UI copy where room allows
• Tap with machine id → that machine + conversation
• Tap without machine id (old daemon): session-id resolution across machines, else machine list — never a wrong conversation
• Tap to an offline machine behaves sensibly (parked machine + sheet, not a dead end)
• Push token registered with every daemon on pairing; re-registered on token rotation
• Cross-machine dedupe: same event via different daemons collapses; pure policy module stays Expo-free with machine-aware tests
• Routing logic is pure and table-driven tested

Blocked by

• Fleet ## Parent #3 (machine-identity) — machine names/ids on notifications
• Fleet ## Parent #7 (app-wiring) — routing targets exist
• Fleet ## Parent #8 (device-browser-ui) — machine list as the no-match fallback destination