bridge-healthlisted

Quick health check on the bridge daemon (CEO machine + any exec mirrors). Surfaces heartbeat staleness, version drift, active sessions, and the Phase 1 -> Phase 2 adoption gate metrics. Use when the dashboard feels stale, the sync-pill is red, the daemon may have crashed, or before a /push-updates that changes daemon config. NEVER auto-trigger - invoke explicitly via /bridge-health.
mishahanin/heading-os · ★ 11 · AI & Automation · score 78

Install: claude install-skill mishahanin/heading-os

# Bridge daemon health check Wraps two CLI scripts into a single CEO ops command: - `scripts/daemon-fleet-health.py` -- fleet status grid (heartbeat freshness, version drift, active session count per workspace) - `scripts/bridge-daemon.py --health` -- live `/health` endpoint probe on the local daemon Optionally surfaces the adoption-gate metrics (Phase 1 -> Phase 2 gate from the bridge spec, section 4) when called with `--gate`. ## When to use - Sync-pill on the dashboard is amber or red - /push-updates pushed a daemon config change and the CEO wants to verify the fleet picked it up - The dashboard feels stale and you don't know if the daemon is dead or just slow - Before deciding whether to scale from Phase 1 (CEO only) to Phase 2 (full CEO coverage) or Phase 3 (exec pilot) — `--gate` shows the gate verdict ## When NOT to use - Single-script debugging: prefer `python scripts/bridge-daemon.py --health` directly when the question is "is this daemon process alive on this machine right now". /bridge-health is for the rollup. - One-line grep summary: prefer `python scripts/bridge-daemon.py --status` for a single grep-friendly line (port + pid + uptime + version + config_v + sessions + errors + last_hb). Designed for cron + shell pipelines. - Triggering refresh: use the dashboard's sync-pill (top right) instead. - Tweaking config: edit `corporate/daemon/config.yaml`, commit, run /push-updates. /bridge-health is read-only. ## Arguments | flag | default