chore: Run pnpm format:fix.

docs/automation/cron-jobs.md

@@ -5,6 +5,7 @@ read_when:
   - Wiring automation that should run with or alongside heartbeats
   - Deciding between heartbeat and cron for scheduled tasks
 ---
+
 # Cron jobs (Gateway scheduler)
 
 > **Cron vs Heartbeat?** See [Cron vs Heartbeat](/automation/cron-vs-heartbeat) for guidance on when to use each.
@@ -12,10 +13,11 @@ read_when:
 Cron is the Gateway’s built-in scheduler. It persists jobs, wakes the agent at
 the right time, and can optionally deliver output back to a chat.
 
-If you want *“run this every morning”* or *“poke the agent in 20 minutes”*,
+If you want _“run this every morning”_ or _“poke the agent in 20 minutes”_,
 cron is the mechanism.
 
 ## TL;DR
+
 - Cron runs **inside the Gateway** (not inside the model).
 - Jobs persist under `~/.openclaw/cron/` so restarts don’t lose schedules.
 - Two execution styles:
@@ -24,18 +26,19 @@ cron is the mechanism.
 - Wakeups are first-class: a job can request “wake now” vs “next heartbeat”.
 
 ## Beginner-friendly overview
+
 Think of a cron job as: **when** to run + **what** to do.
 
-1) **Choose a schedule**
+1. **Choose a schedule**
    - One-shot reminder → `schedule.kind = "at"` (CLI: `--at`)
    - Repeating job → `schedule.kind = "every"` or `schedule.kind = "cron"`
    - If your ISO timestamp omits a timezone, it is treated as **UTC**.
 
-2) **Choose where it runs**
+2. **Choose where it runs**
    - `sessionTarget: "main"` → run during the next heartbeat with main context.
    - `sessionTarget: "isolated"` → run a dedicated agent turn in `cron:<jobId>`.
 
-3) **Choose the payload**
+3. **Choose the payload**
    - Main session → `payload.kind = "systemEvent"`
    - Isolated session → `payload.kind = "agentTurn"`
 
@@ -44,7 +47,9 @@ Optional: `deleteAfterRun: true` removes successful one-shot jobs from the store
 ## Concepts
 
 ### Jobs
+
 A cron job is a stored record with:
+
 - a **schedule** (when it should run),
 - a **payload** (what it should do),
 - optional **delivery** (where output should be sent).
@@ -56,7 +61,9 @@ In agent tool calls, `jobId` is canonical; legacy `id` is accepted for compatibi
 Jobs can optionally auto-delete after a successful one-shot run via `deleteAfterRun: true`.
 
 ### Schedules
+
 Cron supports three schedule kinds:
+
 - `at`: one-shot timestamp (ms since epoch). Gateway accepts ISO 8601 and coerces to UTC.
 - `every`: fixed interval (ms).
 - `cron`: 5-field cron expression with optional IANA timezone.
@@ -67,6 +74,7 @@ local timezone is used.
 ### Main vs isolated execution
 
 #### Main session jobs (system events)
+
 Main jobs enqueue a system event and optionally wake the heartbeat runner.
 They must use `payload.kind = "systemEvent"`.
 
@@ -77,9 +85,11 @@ This is the best fit when you want the normal heartbeat prompt + main-session co
 See [Heartbeat](/gateway/heartbeat).
 
 #### Isolated jobs (dedicated cron sessions)
+
 Isolated jobs run a dedicated agent turn in session `cron:<jobId>`.
 
 Key behaviors:
+
 - Prompt is prefixed with `[cron:<jobId> <job name>]` for traceability.
 - Each run starts a **fresh session id** (no prior conversation carry-over).
 - A summary is posted to the main session (prefix `Cron`, configurable).
@@ -90,11 +100,14 @@ Use isolated jobs for noisy, frequent, or "background chores" that shouldn't spa
 your main chat history.
 
 ### Payload shapes (what runs)
+
 Two payload kinds are supported:
+
 - `systemEvent`: main-session only, routed through the heartbeat prompt.
 - `agentTurn`: isolated-session only, runs a dedicated agent turn.
 
 Common `agentTurn` fields:
+
 - `message`: required text prompt.
 - `model` / `thinking`: optional overrides (see below).
 - `timeoutSeconds`: optional timeout override.
@@ -104,12 +117,15 @@ Common `agentTurn` fields:
 - `bestEffortDeliver`: avoid failing the job if delivery fails.
 
 Isolation options (only for `session=isolated`):
+
 - `postToMainPrefix` (CLI: `--post-prefix`): prefix for the system event in main.
 - `postToMainMode`: `summary` (default) or `full`.
 - `postToMainMaxChars`: max chars when `postToMainMode=full` (default 8000).
 
 ### Model and thinking overrides
+
 Isolated jobs (`agentTurn`) can override the model and thinking level:
+
 - `model`: Provider/model string (e.g., `anthropic/claude-sonnet-4-20250514`) or alias (e.g., `opus`)
 - `thinking`: Thinking level (`off`, `minimal`, `low`, `medium`, `high`, `xhigh`; GPT-5.2 + Codex models only)
 
@@ -118,12 +134,15 @@ session model. We recommend model overrides only for isolated jobs to avoid
 unexpected context shifts.
 
 Resolution priority:
+
 1. Job payload override (highest)
 2. Hook-specific defaults (e.g., `hooks.gmail.model`)
 3. Agent config default
 
 ### Delivery (channel + target)
+
 Isolated jobs can deliver output to a channel. The job payload can specify:
+
 - `channel`: `whatsapp` / `telegram` / `discord` / `slack` / `mattermost` (plugin) / `signal` / `imessage` / `last`
 - `to`: channel-specific recipient target
 
@@ -131,15 +150,18 @@ If `channel` or `to` is omitted, cron can fall back to the main session’s “l
 (the last place the agent replied).
 
 Delivery notes:
+
 - If `to` is set, cron auto-delivers the agent’s final output even if `deliver` is omitted.
 - Use `deliver: true` when you want last-route delivery without an explicit `to`.
 - Use `deliver: false` to keep output internal even if a `to` is present.
 
 Target format reminders:
+
 - Slack/Discord/Mattermost (plugin) targets should use explicit prefixes (e.g. `channel:<id>`, `user:<id>`) to avoid ambiguity.
 - Telegram topics should use the `:topic:` form (see below).
 
 #### Telegram delivery targets (topics / forum threads)
+
 Telegram supports forum topics via `message_thread_id`. For cron delivery, you can encode
 the topic/thread into the `to` field:
 
@@ -148,9 +170,11 @@ the topic/thread into the `to` field:
 - `-1001234567890:123` (shorthand: numeric suffix)
 
 Prefixed targets like `telegram:...` / `telegram:group:...` are also accepted:
+
 - `telegram:group:-1001234567890:topic:123`
 
 ## Storage & history
+
 - Job store: `~/.openclaw/cron/jobs.json` (Gateway-managed JSON).
 - Run history: `~/.openclaw/cron/runs/<jobId>.jsonl` (JSONL, auto-pruned).
 - Override store path: `cron.store` in config.
@@ -162,18 +186,20 @@ Prefixed targets like `telegram:...` / `telegram:group:...` are also accepted:
   cron: {
     enabled: true, // default true
     store: "~/.openclaw/cron/jobs.json",
-    maxConcurrentRuns: 1 // default 1
-  }
+    maxConcurrentRuns: 1, // default 1
+  },
 }
 ```
 
 Disable cron entirely:
+
 - `cron.enabled: false` (config)
 - `OPENCLAW_SKIP_CRON=1` (env)
 
 ## CLI quickstart
 
 One-shot reminder (UTC ISO, auto-delete after success):
+
 ```bash
 openclaw cron add \
   --name "Send reminder" \
@@ -185,6 +211,7 @@ openclaw cron add \
 ```
 
 One-shot reminder (main session, wake immediately):
+
 ```bash
 openclaw cron add \
   --name "Calendar check" \
@@ -195,6 +222,7 @@ openclaw cron add \
 ```
 
 Recurring isolated job (deliver to WhatsApp):
+
 ```bash
 openclaw cron add \
   --name "Morning status" \
@@ -208,6 +236,7 @@ openclaw cron add \
 ```
 
 Recurring isolated job (deliver to a Telegram topic):
+
 ```bash
 openclaw cron add \
   --name "Nightly summary (topic)" \
@@ -221,7 +250,8 @@ openclaw cron add \
 ```
 
 Isolated job with model and thinking override:
-```bash
+
+````bash
 openclaw cron add \
   --name "Deep analysis" \
   --cron "0 6 * * 1" \
@@ -242,15 +272,17 @@ openclaw cron add --name "Ops sweep" --cron "0 6 * * *" --session isolated --mes
 # Switch or clear the agent on an existing job
 openclaw cron edit <jobId> --agent ops
 openclaw cron edit <jobId> --clear-agent
-```
-```
+````
+
+````
 
 Manual run (debug):
 ```bash
 openclaw cron run <jobId> --force
-```
+````
 
 Edit an existing job (patch fields):
+
 ```bash
 openclaw cron edit <jobId> \
   --message "Updated prompt" \
@@ -259,28 +291,33 @@ openclaw cron edit <jobId> \
 ```
 
 Run history:
+
 ```bash
 openclaw cron runs --id <jobId> --limit 50
 ```
 
 Immediate system event without creating a job:
+
 ```bash
 openclaw system event --mode now --text "Next heartbeat: check battery."
 ```
 
 ## Gateway API surface
+
 - `cron.list`, `cron.status`, `cron.add`, `cron.update`, `cron.remove`
 - `cron.run` (force or due), `cron.runs`
-For immediate system events without a job, use [`openclaw system event`](/cli/system).
+  For immediate system events without a job, use [`openclaw system event`](/cli/system).
 
 ## Troubleshooting
 
 ### “Nothing runs”
+
 - Check cron is enabled: `cron.enabled` and `OPENCLAW_SKIP_CRON`.
 - Check the Gateway is running continuously (cron runs inside the Gateway process).
 - For `cron` schedules: confirm timezone (`--tz`) vs the host timezone.
 
 ### Telegram delivers to the wrong place
+
 - For forum topics, use `-100…:topic:<id>` so it’s explicit and unambiguous.
 - If you see `telegram:...` prefixes in logs or stored “last route” targets, that’s normal;
   cron delivery accepts them and still parses topic IDs correctly.