Files
stack/docs/fleet/reference/status-and-drift.md
jason.woltje 499090508e
All checks were successful
ci/woodpecker/push/publish Pipeline was successful
ci/woodpecker/push/ci Pipeline was successful
feat(fleet): reconcile local roster state (#785)
2026-07-15 15:03:31 +00:00

1.1 KiB

Local Fleet Status and Drift

mosaic fleet status [name], verify, and doctor are observational roster-v2 commands. They emit one JSON result and do not write projections, change desired state, start services, stop services, restart services, or mutate tmux.

The report distinguishes:

  • missing-session: an enabled agent desired running has no exact roster-named tmux session.
  • unexpected-session: a desired-stopped agent still has its exact session.
  • disabled-running: a disabled roster agent has its exact session.
  • unmanagedSessions: sessions on the configured named socket that are neither the exact holder nor an exact roster agent.
  • holder: owned, missing, or ownership-mismatch after exact holder, private install identity, and complete global tmux environment validation.

doctor and status classify rather than adopt, destroy, or repair unmanaged state. verify is observational too, but exits non-zero if ownership cannot be proven, unmanaged sessions exist, or drift is present. Reconciliation fails closed under those conditions and never kills or adopts an unmanaged session.