Title: Isolated cron jobs don't schedule (nextWakeAtMs stays null)
Version: 2026.2.3-1
Description:
Cron jobs with sessionTarget: "isolated" are created successfully but:
state.nextRunAtMs is never populated
nextWakeAtMs in cron status stays null
Jobs never auto-fire (must use --force)
Main session jobs (sessionTarget: "main") work correctly.
Additional: CLI rejects --session isolated with unexpected property 'delivery' error, even without --announce.
Workaround: Use main session jobs with systemEvent.