🐛 Bug: Cron Scheduler Not Loading Jobs from jobs.json

Issue Description

The OpenClaw cron scheduler is completely broken. All 47 cron jobs exist in ~/.qclaw/cron/jobs.json but the Gateway doesn't recognize any of them.

Environment

• OS: macOS (Darwin 25.4.0, arm64)
• Node: v22.21.1
• OpenClaw version: latest
• Gateway running (PID visible) but cron timer not functioning

Steps to Reproduce

1. Create cron jobs via CLI: openclaw cron add ...
2. Jobs appear correctly in ~/.qclaw/cron/jobs.json (47 jobs confirmed)
3. Run openclaw cron list - shows all jobs correctly
4. Run openclaw cron run <id> - returns Error: unknown cron job id: 1
5. openclaw cron status - hangs indefinitely
6. Jobs never execute automatically despite being overdue

Technical Details

• jobs.json: 47 jobs present, valid JSON structure
• jobs.json.bak: Only 2 jobs (old backup, different format)
• Gateway process running but cron subsystem not loading jobs from file
• CLI cron run <id> fails with "unknown cron job id" for ALL job IDs
• cron status command hangs with no response
• cron runs shows 0 execution records for days

Expected vs Actual Behavior

• Expected: Jobs in jobs.json should be loaded into Gateway memory and executed on schedule
• Actual: Gateway runs but cron subsystem has 0 jobs loaded in memory, manual trigger also fails

Impact

• All daily digest tasks (AI news, weather, etc.) not running
• All reminder tasks (birthdays, travel reminders) not running
• User has to manually trigger everything via message

Workaround

None available - this completely blocks automated task scheduling functionality.

Labels: bug, cron, scheduler, high-priority