feat: add multi-skill cron editing and docs

website/docs/developer-guide/cron-internals.md

@@ -1,7 +1,7 @@
 ---
 sidebar_position: 11
 title: "Cron Internals"
-description: "How Hermes stores, schedules, locks, and delivers cron jobs"
+description: "How Hermes stores, schedules, edits, pauses, skill-loads, and delivers cron jobs"
 ---
 
 # Cron Internals
@@ -10,7 +10,9 @@ Hermes cron support is implemented primarily in:
 
 - `cron/jobs.py`
 - `cron/scheduler.py`
+- `tools/cronjob_tools.py`
 - `gateway/run.py`
+- `hermes_cli/cron.py`
 
 ## Scheduling model
 
@@ -21,9 +23,30 @@ Hermes supports:
 - cron expressions
 - explicit timestamps
 
+The model-facing surface is a single `cronjob` tool with action-style operations:
+
+- `create`
+- `list`
+- `update`
+- `pause`
+- `resume`
+- `run`
+- `remove`
+
 ## Job storage
 
-Cron jobs are stored in Hermes-managed local state with atomic save/update semantics.
+Cron jobs are stored in Hermes-managed local state (`~/.hermes/cron/jobs.json`) with atomic write semantics.
+
+Each job can carry:
+
+- prompt
+- schedule metadata
+- repeat counters
+- delivery target
+- lifecycle state (`scheduled`, `paused`, `completed`, etc.)
+- zero, one, or multiple attached skills
+
+Backward compatibility is preserved for older jobs that only stored a legacy single `skill` field or none of the newer lifecycle fields.
 
 ## Runtime behavior
 
@@ -32,11 +55,22 @@ The scheduler:
 - loads jobs
 - computes due work
 - executes jobs in fresh agent sessions
+- optionally injects one or more skills before the prompt
 - handles repeat counters
-- updates next-run metadata
+- updates next-run metadata and state
 
 In gateway mode, cron ticking is integrated into the long-running gateway loop.
 
+## Skill-backed jobs
+
+A cron job may attach multiple skills. At runtime, Hermes loads those skills in order and then appends the job prompt as the task instruction.
+
+This gives scheduled jobs reusable guidance without requiring the user to paste full skill bodies into the cron prompt.
+
+## Recursion guard
+
+Cron-run sessions disable the `cronjob` toolset. This prevents a scheduled job from recursively creating or mutating more cron jobs and accidentally exploding token usage or scheduler load.
+
 ## Delivery model
 
 Cron jobs can deliver to:
@@ -48,7 +82,7 @@ Cron jobs can deliver to:
 
 ## Locking
 
-Hermes uses lock-based protections so concurrent cron ticks or overlapping scheduler processes do not corrupt job state.
+Hermes uses lock-based protections so overlapping scheduler ticks do not execute the same due-job batch twice.
 
 ## Related docs