iterm-statuslisted

# iTerm hook stack status Print a one-shot health snapshot for the whole iterm-config stack. ## What to do when invoked Run the report script and let its output stand on its own. The script is read-only — no side effects. ```bash ~/.claude/hooks/iterm-status-report.sh ``` After printing, **don't summarize or explain the output line-by-line** unless the user asks. The format is designed to be self-explanatory (green check = good, yellow `!` = warning, red `✗` = broken). If the user explicitly asks a follow-up like "what does the waiting marker mean," then explain. ## What the sections mean - **Daemon** — Tier 1's persistent process. `alive` + fresh heartbeat = healthy. A stale heartbeat with `DEAD` status means the daemon detected its own websocket failure and is about to exit (next hook event respawns it). - **Watchdog** — the `claude-code.iterm-watchdog` LaunchAgent. Runs every 30s, respawns the daemon if dead. - **Sessions** — live `*.state` files modified in the last hour, with the current color and any in-flight tool count. Useful for "which tab is in which state right now." - **Recent PostToolUse suppressions** — count of stray end-of-turn events the marker logic correctly squashed today (vs yesterday). Non-zero here is normal; zero means either no recent turns or the suppression heuristic isn't catching any strays. - **This session** — token totals from the latest Claude Code session JSONL for `$PWD`. Driven by `iterm-session-cost.py`. ## When something looks wr