fleetlisted

# Fleet — Snapshot of live fleet state One-line status summary for aesop fleet operations, showing active agents, daemon health, tracker backlog, and orchestrator phase. ## Procedure Run the fleet snapshot tool and parse the JSON output: ```bash aesop fleet ``` ### Output format JSON object with: - **timestamp**: ISO 8601 when snapshot was taken - **aesop_root**: Fleet root directory (from AESOP_ROOT env or process.cwd()) - **heartbeats**: Object with watchdog and monitor pulse status - **watchdog**: age_seconds, status (OK/STALE/MISSING), threshold_seconds - **monitor**: age_seconds, status (OK/STALE/MISSING), threshold_seconds - **agents**: Array of active agents OR unavailable message - Each agent: id, project, status, age_s, hint, startedAt, lastActivity, runtimeSeconds, tokensUsed, taskLabel, promptFull - **tracker**: Tracker backlog counts by lane OR unavailable message - total_items: sum of all items - by_lane: object mapping lane names to counts - **orchestrator**: Current orchestrator status OR unavailable message - activity, phase, timestamp (from state/orchestrator-status.json) ### Graceful degradation All missing state files produce explicit `unavailable: "<reason>"` entries rather than crashing: - watchdog heartbeat missing → `unavailable: "MISSING"` - monitor heartbeat missing → `unavailable: "MISSING"` - dash-extra.mjs not found → `agents: { unavailable: "dash-extra.mjs not found" }` - tracker.json missing/malformed → `tracker: { unavailab