Bug

The web dashboard at http://127.0.0.1:18789/cron shows "Run history = no runs yet" even though runs exist.

Evidence

Run history IS being written to disk:

• File: ~/.clawdbot/cron/runs/<job-id>.jsonl
• Contains entries with timestamps, status, errors

The cron.runs API also returns the data correctly when queried programmatically.

Expected

The /cron page should display the run history from the runs/ directory.

Environment

• Clawdbot: 2026.1.11-4
• macOS (Darwin 24.6.0 arm64)
• Chrome browser

Steps to Reproduce

1. Create a cron job
2. Wait for it to run (or trigger manually)
3. Visit http://127.0.0.1:18789/cron
4. Observe "Run history = no runs yet" despite runs existing in ~/.clawdbot/cron/runs/