ainb-fleetatc

# ainb fleet:atc — Air Traffic Control ATC is the orchestrating brain that ties the fleet verbs together on a schedule with a policy. It is a real `ainb run` Claude session reading a generated `CLAUDE.md`, woken every N minutes by an OS timer. On each heartbeat it pulls the **LLM-free** `ainb fleet needs --format json` read, auto-clears the safe cases itself, and pages you (via the phone bridge) only for the calls that genuinely need a human. ``` hooks ─▶ events.jsonl ─▶ notifyd ─▶ current_state (ASK/ERR/WAIT/IDLE/RUNNING/DONE) │ (materialized per session) OS timer ──[HEARTBEAT]──▶ ATC session ──reads──▶ ainb fleet needs --format json │ (hooks-primary, tmux fallback) ├─ auto-clear ─▶ ainb fleet broadcast (answer / continue) └─ escalate ───▶ phone bridge ─▶ your phone ``` ## How ATC learns a session is blocked — HOOKS-PRIMARY The `fleet needs` read ATC runs each heartbeat is **event-sourced**, not pane- scraped. 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). ATC reads that materialized state as the PRIMARY source — so it learns ASK/WAIT/IDLE/ERR from hooks, the instant they fire, **without scraping panes**. The tmux pane scan is only the **fallback** for sessions the hook...