When users send atMs as a numeric string (e.g., '1234567890') via the
cron tool, the normalization was failing to parse it correctly because
parseAbsoluteTimeMs expects ISO date strings.

This caused schedule.at to be undefined, which made computeJobNextRunAtMs
return undefined, leaving jobs without state.nextRunAtMs set. Jobs would
never execute because the scheduler couldn't determine when they were due.

Changes:
- Add parseNumericStringToMs helper to convert numeric strings to timestamps
- Use it as fallback in coerceSchedule when parseAbsoluteTimeMs fails

Fixes openclaw#9668

When the timer fires slightly after the scheduled time (even 1ms late),
the previous order of operations caused jobs to be skipped:

1. ensureLoaded called recomputeNextRuns, which advanced nextRunAtMs to
the NEXT occurrence (e.g., 14:00 instead of 12:00)
2. runDueJobs then checked if jobs were due, but nextRunAtMs was already
in the future, so no jobs ran

The fix reorders operations in onTimer:
1. Load store WITHOUT recomputing (preserve stored nextRunAtMs)
2. Check and run due jobs using stored nextRunAtMs values
3. THEN recompute next runs for subsequent executions
4. Persist and arm timer

This ensures jobs are checked against their original scheduled times
before any recomputation happens.

Changes:
- store.ts: Add skipRecompute option to ensureLoaded
- timer.ts: Reorder operations, call recomputeNextRuns after runDueJobs

Fixes openclaw#9661

When agents create cron reminders, the results were not being delivered
to users because there was no way to specify the delivery channel.

Changes:
- Add deliver, channel, and to parameters to CronToolSchema
- In the 'add' action, build delivery config when these are provided
- Only apply delivery for isolated agentTurn jobs (as per constraints)

This allows agents to create reminders that deliver results back to the
originating channel by setting channel=<channel-id> and optionally to=<user>.

Fixes openclaw#9683

When a Signal message is edited, signal-cli provides an editMessage envelope
containing targetSentTimestamp (original message) and new dataMessage content.

Previously, edited messages were treated as entirely new messages, creating
duplicate context and potentially triggering duplicate responses.

Changes:
- Detect editMessage envelopes by checking for targetSentTimestamp
- Add [edited] marker to edited message text for visibility
- Use targetSentTimestamp as messageId to help with deduplication

This allows users to see when messages are edited and helps prevent
duplicate processing of the same logical message.

Fixes openclaw#9656

When opening Tool Output in the Chat view with large content (>10KB),
the browser would freeze for 10+ seconds and CPU usage spiked to 100%.

Root cause: marked.parse() is synchronous and can be very slow with large
inputs or certain patterns, even with the previous 40KB limit.

Changes:
- Lower MARKDOWN_PARSE_LIMIT from 40KB to 20KB
- Add MARKDOWN_PRE_WRAP_LIMIT at 10KB (new fast path)
- For content >10KB: skip markdown parsing entirely, render as pre-wrap
- Add white-space: pre-wrap and word-break for readable large outputs

This ensures tool outputs display immediately without blocking the UI,
while still supporting markdown formatting for smaller outputs.

Fixes openclaw#9700