Bug

Isolated agentTurn cron jobs that don't set lightContext: true and don't restrict toolsAllow spend their entire timeout budget on session bootstrap (loading full agent context, memory, workspace files) and timeout before executing any actual work.

Steps to reproduce

1. Create a cron job with sessionTarget: isolated, payload.kind: agentTurn, no lightContext, no toolsAllow, and timeoutSeconds: 60
2. Task only needs one or two tools (e.g. web_fetch + message)
3. Observe: job times out at exactly 60 s every run, never executes its task

Current behavior

Job run history shows 4/4 consecutive timeouts at exactly 60 s. The job never reaches its first tool call. No error other than "cron: job execution timed out".

Expected behavior

Either:

1. The gateway should warn at job creation/update time when a job likely needs lightContext or toolsAllow based on its timeout and task scope, or
2. The default timeout for isolated agentTurn jobs should account for cold-start overhead (cold start can take 30–45 s on a loaded system), or
3. Docs should prominently call out that isolated jobs doing simple tasks must set lightContext: true and restrict toolsAllow to avoid spending the budget on bootstrap

Workaround

Set lightContext: true and toolsAllow: [<only needed tools>] on the job. Also set timeoutSeconds to at least 2–3× the expected task duration.

Impact

Silent failure — the job shows as "error" but the error message gives no indication that cold-start overhead is the cause. Easy to miss if you don't check run history.