Bug Description

On OpenClaw v2026.4.26, cron jobs with payload.kind: "systemEvent" and sessionTarget: "main" still silently fail when manually triggered via cron run (both CLI and Control UI "Run" button). The run completes in ~12-31ms with deliveryStatus: "not-requested" and no actual execution.

This appears to be a regression or incomplete fix for previously closed issues #60262 and #62296.

Steps to Reproduce

1. Create a cron job with systemEvent payload targeting main session:

{
  "name": "Test systemEvent",
  "sessionTarget": "main",
  "payload": {
    "kind": "systemEvent",
    "text": "Please check something and report back"
  }
}

2. Trigger it via CLI: openclaw cron run --id <job-id> or click "Run" in Control UI

3. Check run result: openclaw cron runs --id <job-id>

Expected Behavior

The system event should be delivered to the main session, causing the agent to wake up and execute the task.

Actual Behavior

{
  "action": "finished",
  "status": "ok",
  "durationMs": 12,
  "deliveryStatus": "not-requested"
}

No agent turn is created. The task is not executed.

Environment

• OpenClaw: v2026.4.26
• Node: v22.22.2
• OS: Linux 6.6.87.2-microsoft-standard-WSL2

Related Issues

• [Bug]: Cron jobs fire but don't wake agent sessions #60262 — [Bug]: Cron jobs fire but don't wake agent sessions (mentioned fix commit 435018a)
• [Bug] memory-core dreaming cron system-event does not trigger before_agent_reply hook (deliveryStatus: not-requested) #62296 — memory-core dreaming cron system-event does not trigger before_agent_reply hook
• Bug: Cron job system events are ignored during heartbeat execution #7065 — Cron job system events are ignored during heartbeat execution
• [Bug]: wake() in cron/service/timer.ts calls enqueueSystemEvent without sessionKey — system events silently dropped #19438 — wake() in cron/service/timer.ts calls enqueueSystemEvent (fixed in 98feb9f)

Additional Context

The same job works correctly when triggered naturally via scheduled heartbeat poll. The issue is specifically with manual cron run trigger (both CLI cron run and Control UI "Run" button).