Fleet-polish bundle — boot-survival symmetry (disable-on-remove + add-enable + init-R5) #611

Closed
opened 2026-06-22 07:44:29 +00:00 by jason.woltje · 0 comments
Owner

Fleet-polish bundle — boot-survival symmetry

From the Lead's Codex symmetry-gap finding. Three fixes completing add/remove boot-survival symmetry:

  1. disable-on-remove (bug). mosaic fleet remove stops + deletes roster/env/heartbeat but does NOT systemctl --user disable mosaic-agent@NAME.service — so a removed-but-enabled unit can resurrect on reboot pointing at deleted config. Add disable-on-remove (+ test).
  2. add-enable. mosaic fleet add should enable the new agent's unit for boot-survival.
  3. init-R5 guarantee. mosaic fleet init must guarantee exactly one orchestrator (hard-fail non-minimal mismatch instead of warning).
## Fleet-polish bundle — boot-survival symmetry From the Lead's Codex symmetry-gap finding. Three fixes completing add/remove boot-survival symmetry: 1. **disable-on-remove (bug).** `mosaic fleet remove` stops + deletes roster/env/heartbeat but does NOT `systemctl --user disable mosaic-agent@NAME.service` — so a removed-but-enabled unit can resurrect on reboot pointing at deleted config. Add disable-on-remove (+ test). 2. **add-enable.** `mosaic fleet add` should enable the new agent's unit for boot-survival. 3. **init-R5 guarantee.** `mosaic fleet init` must guarantee exactly one orchestrator (hard-fail non-minimal mismatch instead of warning).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#611