ainb-fleetdaemons

# ainb fleet:daemons — daemon health view The runtime-health answer for the fleet's four background daemons. Reads the on-disk liveness signals each daemon already maintains and renders one typed row per daemon. The same aggregator (`fleet::daemons::collect`) backs the TUI Daemons screen, so the CLI and the TUI can never drift. This is the question `ainb fleet bridge status` could never answer: that verb reports only **install** state. `daemons` reports whether the process is actually **running and serving** right now — a crashed-but-installed bridge shows `stopped` with a stale-heartbeat reason here. ## The four daemons | daemon | id | how it's probed | |---|---|---| | **phone bridge** | `bridge` | heartbeat file (`~/.agents-in-a-box/daemons/bridge.json`) + pid-identity cross-check | | **notifyd** | `notifyd` | PID-file liveness + bound Unix socket + sqlite DB file present | | **ATC** | `atc` | most-recently-beating provisioned instance's `heartbeat-state.json` (timer-driven; no resident pid) | | **fleet daemon** | `fleet-daemon` | heartbeat file + pid-identity cross-check | Rows are always emitted in this exact order (bridge, notifyd, ATC, fleet daemon), even when every daemon is stopped — so "everything stopped" is a legible four-row table, never an empty one. ## Run ```bash ainb fleet daemons # fixed-width text table (default) ainb --format json fleet daemons # typed rows for scripting ``` `--format` is a **global** flag — it goes bef...