hermit-routines

# Routines Register and manage scheduled routines. Where the Monitor tool is available, all enabled routines except `heartbeat-restart` run from ONE persistent Monitor subprocess that decides eligibility outside the session — a skipped fire costs zero model tokens. `heartbeat-restart` stays a CronCreate **re-arm anchor**: its daily fire re-invokes `load` (re-arming the monitor) and its skill re-arms the heartbeat monitor. Where Monitor is unavailable (Bedrock/Google Cloud Agent Platform/Foundry, `DISABLE_TELEMETRY`/`CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`), `load` falls back to per-routine CronCreates. ## Usage ``` /claude-code-hermit:hermit-routines load register/reconcile: monitor mode if available, else CronCreate diff-register /claude-code-hermit:hermit-routines load --reset unconditional reset: tear down + recreate everything /claude-code-hermit:hermit-routines run <ids> [internal] ROUTINE_DUE handler — invoked by the monitor's notification /claude-code-hermit:hermit-routines list list configured routines from config.json /claude-code-hermit:hermit-routines status show monitor/anchor state (or CronCreate registrations in fallback mode) /claude-code-hermit:hermit-routines stop [id] stop the monitor (or a specific fallback-mode CronCreate) /claude-code-hermit:hermit-routines stop --all stop everything ``` ## Plan ### load Called automatically by `hermit-start.ts` on always-on launches. Can als...