heartbeat

# Heartbeat Background health checker that periodically evaluates a checklist and surfaces anything that needs operator attention. ## Usage ``` /claude-code-hermit:heartbeat run — execute one tick immediately /claude-code-hermit:heartbeat start — start the recurring tick /claude-code-hermit:heartbeat stop — stop the recurring tick /claude-code-hermit:heartbeat status — show last result and schedule state /claude-code-hermit:heartbeat edit — modify the checklist ``` ## Step 0 — Channel reply If this skill was invoked from a channel-arrived message (the inbound prompt contains a `<channel source="...">` tag), reply via that channel's reply tool. Otherwise emit to conversation. The only interactive ask here is the `edit` subcommand's free-form "what to add, remove, or change" — on a channel-tagged turn deliver it via the reply tool as an ordinary over-channel exchange (it's open-ended, so no micro-proposal entry is queued). **Never call `AskUserQuestion` on a channel-tagged turn** — it renders in the terminal, invisible to a remote operator. ## Subcommands ### run This subcommand is the handler for `HEARTBEAT_EVALUATE` notifications emitted by the heartbeat Monitor. It's also runnable manually for ad-hoc ticks. The Monitor uses `precheck --peek` for polling; this handler re-runs precheck without `--peek` so the mutating tick (`total_ticks` increment, alert-state write) happens exactly once per noteworthy tick. 1. Run the precheck: ``` bun ${CLAUD...