iterm-diagnoselisted

# iTerm hook stack diagnose Active end-to-end test. Flashes colors on the current tab, verifies each pushes through to iTerm2 via the daemon, and reports pass/fail per step. ## When to use - "Test the iterm tab hooks" - "Is the iterm stack actually working" - "Run iterm diagnose" - "/iterm-diagnose" - After installing/upgrading anything in the iterm-config stack — confirm the install actually works before declaring done ## Heads-up to the user before invoking Brief warning is enough: "Going to flash white → blue → orange on this tab over ~3s, then restore. OK?" Only ask if the user invoked you in a context where unexpected color changes might be confusing. For an explicit `/iterm-diagnose` invocation, just run it. ## What to do when invoked Run the diagnose script. Default mode (no `--restart`) is fast (~3s) and only flashes colors. Pass `--restart` ONLY if the user explicitly asked for "deep" / "full" / "include daemon respawn" — that one adds ~30s while the watchdog re-spawns the daemon. ```bash ~/.claude/hooks/iterm-diagnose.sh # color flash test only ~/.claude/hooks/iterm-diagnose.sh --restart # also test daemon respawn ``` Let the script's output speak for itself. It prints per-step pass/fail with the same green-check/red-cross convention as `/iterm-status`. Don't restate or interpret unless asked. ## What gets tested 1. **Prereqs** — venv python, daemon script, resync script exist; UUID resolved 2. **Daemon health** — PID alive, heartbeat status