Module starts 

Start nodes as the triggers (RFC 0027 §4, plan §3.6.6): beyond once and manual, the long-lived start kinds fire runs while the instance lives — loop (re-run on completion, interval/until/max_iterations/ backoff), schedule (cron / every, catch_up), subscribe (an MCP resource update, notify-then-read, debounce/coalesce/filter, claim/shard for exactly-one-owner in a cluster), signal (a named signal), event (an internal lifecycle event), and a2a (a principal’s message routed here — P5). Start-node state (last fired, iteration, missed, next deadline, debounce) is durable in the manifest.

Functions

run_event

Whether a status is a success for event on: workflow.finished|failed.