[MyUltiDev]

The trigger matrix here is actually the most interesting part. Schedule plus API plus GitHub event on the same routine unlocks some nice patterns, and the /fire endpoint returning a session URL means you can wire this into alerting tools or a CD pipeline from almost anywhere. The part that is not really covered in the docs is what state a routine is supposed to recover from if a previous run died halfway through a repository change. The protection around claude/-prefixed branches helps you not clobber main, but it does not tell the next run what the previous run actually finished. I run scheduled jobs against multi step pipelines on my own infra and the failure mode that bites is not the crash, it is the run that returned success while a downstream side effect quietly broke. The /fire response returns a session URL and a session ID, which tells you the routine started, but how is a routine expected to notice when the downstream thing it kicked off (a CD pipeline, an alert follow-up, a library port PR like the one in the examples quietly fell over five minutes after the session ended?