Remote trigger runs return config JSON but don't execute

Description

Remote triggers (scheduled cron jobs) are not executing. Both scheduled runs and manual runs via the API return the trigger configuration JSON but produce no actual agent execution or output.

Reproduction

1. Create a remote trigger with a cron schedule (e.g., 0 1 * * 1-5)
2. Wait for a scheduled run, OR manually trigger via POST /v1/code/triggers/{trigger_id}/run
3. The API returns HTTP 200 with the trigger config object
4. No agent session is created, no tools are called, no output is produced

Details

• Trigger ID: trig_01U3a2zNiajDZyrrXJzk6WNF
• Failing since: 2026-04-08 (two consecutive days of missed scheduled runs + multiple failed manual runs)
• Cron expression: 0 1 * * 1-5 (9am SGT weekdays)
• Model: claude-opus-4-6
• Allowed tools: Bash, Read, Write
• Environment ID: env_016Z5MuAqYdA8F6R5Y9RFV9F

What we tested

• Simplified the prompt to a trivial heartbeat ("echo hello") — same behavior
• Created brand new triggers — same behavior
• The prompt and Supabase RPCs all work correctly when run locally in a normal Claude Code session
• This appears to be a server-side execution platform issue, not a prompt or configuration issue

Expected behavior

POST /v1/code/triggers/{trigger_id}/run should spin up an agent session that executes the trigger prompt and returns execution output.

Actual behavior

Returns the trigger config JSON with no evidence of execution.