Problem

The cron run action is documented as "Trigger job immediately (requires jobId)" but it respects the schedule and returns ran: false, reason: "not-due" when the job isn't due yet.

Expected Behavior

cron run should force immediate execution regardless of schedule — that's the whole point of a manual trigger.

Actual Behavior

{
  "ok": true,
  "ran": false,
  "reason": "not-due"
}

Use Case

User wants to manually trigger a PM agent (Scout) that normally runs every 6 hours. The workaround is sessions_spawn with the same task payload, but that defeats the purpose of having a named cron job.

Suggested Fix

Add a force: true parameter or change the default behavior of run to always execute immediately (since that's what "run" implies).