Increase Cronicle trigger timeout to 5 min to allow LLM agent to complete

The shell script's Node.js socket timeout was 10s, too short for agent
runs with use_agent=true. Bump to 300s (5min) and set Cronicle job
timeout to 360s to match.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

utils/cronicle.py

@@ -49,7 +49,7 @@ function post(host) {{
          headers: {{'X-Cron-Secret': '{cron_secret}'}} }},
       res => {{ res.resume(); resolve(res.statusCode); }}
     );
-    req.setTimeout(10000, () => {{ req.destroy(); reject(new Error('timeout')); }});
+    req.setTimeout(300000, () => {{ req.destroy(); reject(new Error('timeout')); }});
     req.on('error', reject);
     req.end();
   }});
@@ -119,6 +119,7 @@ async def create_message_event(
                     "category": category_id,
                     "timing": timing,
                     "timezone": "UTC",
+                    "timeout": 360,
                     "params": {"script": script},
                     "notes": f"Auto-created for scheduled message {msg_id} (recurrence={recurrence})",
                 },