watch

# Watch Run background event watchers using the CC Monitor tool. Each stdout line from the subprocess becomes a conversation notification. Silence costs zero tokens. Two classes: - **Stream:** Source pushes events (`tail -f`, WebSocket, fswatch). Truly event-driven. - **Poll:** Script checks on interval, emits only on change. Same polling model, less noise. ## Usage ``` /claude-code-hermit:watch <instruction> — start ad-hoc (poll, default 5m interval) /claude-code-hermit:watch <stream-command> — start ad-hoc stream /claude-code-hermit:watch start — register all enabled config watches /claude-code-hermit:watch stop [id] — stop by id (or auto if 1 active) /claude-code-hermit:watch stop --all — stop all watches /claude-code-hermit:watch status — list active watches from registry ``` ## Runtime Registry All active watches are tracked in `.claude-code-hermit/state/monitors.runtime.json`. This is the **sole source of truth** — not SHELL.md. ```json { "monitors": [ { "id": "deploy-errors", "task_id": "bmg9y1le3", "description": "errors in deploy.log", "started_at": "2026-04-12T15:00:00Z", "source": "config", "class": "stream" } ], "last_cleared": "2026-04-12T15:00:00Z" } ``` SHELL.md `## Monitoring` entries are a **journal only** — no code path reads them for decisions. Start/stop decisions read from the runtime registry. ## Plan ### Starti...