ainb-fleetneedslisted

# ainb fleet:needs — center control panel Single place to see every claude session that wants your attention. Four signal kinds classified per session, priority ASK > ERR > IDLE > WAIT. ## `needs` vs `fleet-needs` — which skill? > **This skill (`needs`) is the plain, always-available control panel.** It is > prompt-driven: render the HUD, fire AskUserQuestion, route answers back. It > needs no workflow gate and works everywhere. > > **[`/ainb-fleet:fleet-needs`](../fleet-needs/SKILL.md) is the workflow-backed > "Jarvis" cockpit** — same purpose, but it runs the deterministic `hangar` > workflow (verb=needs) for discover→enrich→prioritize, batches enrichment in a > single agent, and adds **key-route ASK answering** (presses the target's > picker keys via tmux for an open AskUserQuestion). It requires > `CLAUDE_CODE_WORKFLOWS=1`; with the gate off it falls back to **this** skill. > > Rule of thumb: reach for `fleet-needs` when the workflow gate is on and you > want the batched/cockpit path; otherwise use `needs`. Both read the same > underlying `ainb fleet needs` data, so the panel content is identical. ## Source of truth — materialized `current_state` (hooks), tmux fallback `ainb fleet needs` reads the **event-sourced** read model first. Claude Code hooks append lifecycle events to `events.jsonl`; notifyd ingests them into a SQLite `current_state` table that materializes the latest stage per session (ASK / ERR / WAIT / IDLE / RUNNING / DONE). For each session (keyed by `c