heartbeat

# Heartbeat Run the agent's periodic checks. Triggered every 30 minutes by a local cron, or manually. ## How it works 1. **Cron health (ALWAYS — even outside active hours).** This is infrastructure, not a user-facing check; it is what heals orphaned reminders in long-running sessions (see issue #32). This step manages its own state: it reads AND writes the `cronAudit` field of `memory/heartbeat-state.json` itself, here, regardless of whether the later steps run. Every heartbeat: - Load the tools once per session if needed: `ToolSearch(query="select:CronList,CronCreate")`. - Retire fired one-shots FIRST so the repair below cannot resurrect them: `bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" prune-expired` - Call `CronList` and pipe its FULL output to: `bash "$CLAUDE_PLUGIN_ROOT/skills/crons/writeback.sh" audit` (mechanical diff: refreshes `lastSeenAlive`, relinks survivors, prints `orphan key=…` / `blocked key=…` lines and an `audit: alive=K/N …` summary; exit 4 = format drift — stop, surface it, do not create anything). - If `orphaned=0` and `blocked=0`: clear `cronAudit.pending` in `memory/heartbeat-state.json` if set — done, say nothing. - If `orphaned>0`: repair `orphan key=` lines ONLY (NEVER `blocked key=` lines — those have ambiguous live duplicates; recreating them would add a third copy). `touch "$CLAUDE_PROJECT_DIR/memory/.reconciling"` (the registry's crons are replayed verbatim, so the cron-from.sh stamp gate must be bypasse...