Remote Trigger /run returns HTTP 500 — trigger auto-disables after failed cron execution

Description

Remote triggers fail with HTTP 500 on both manual /run and scheduled cron execution. After a failed cron run, the trigger auto-disables itself ("enabled": false).

Reproduction

1. Create a scheduled trigger with a git repository source (private GitHub repo)
2. Attempt manual run via API: POST /v1/code/triggers/{trigger_id}/run
3. Returns HTTP 500: {"error":{"message":"An internal server error occurred","type":"api_error"}}
4. Same result via CLI: claude trigger run <trigger_id>
5. When cron fires automatically, same failure occurs and trigger disables itself

Details

• Trigger IDs: trig_015XiEr3DKGPaiM8esD23xRg, trig_015UvyZiN4zvPGkyuAmyZQKU
• Environment: env_01MSGjrHZu5ZcraDpY5jyEKy
• Request ID (manual run): req_011CZeyMdErx3M43NtuM8hTL
• Model: claude-sonnet-4-6
• Source: Private GitHub repo (.git URL)
• MCP connections: Gmail, Canva
• Trigger updates work fine (HTTP 200) — only /run fails

Expected behavior

Trigger should execute the configured session successfully, or return a descriptive error message instead of a generic 500.

Environment

• Claude Code CLI (macOS)
• API and CLI both produce the same 500 error