Start a workflow on a ticket

POST /tickets/runs accepts a workflow_id instead of an agent_id, so the workflow outputs publish the result.


POST /tickets/runs now takes either agent_id or workflow_id, with an optional entry. With a workflow, the ticket is resolved as before, the workflow starts from its manual entry with the ticket as input, and the same one-run-per-ticket lock applies. The workflow outputs, such as a GitHub comment, publish the result, which a bare agent run never did. Starting with an agent_id is unchanged.

A workflow with a github_comment output cannot start on a FerrTrack ticket, which has no GitHub issue to comment on: use a ferrtrack_ticket output. See the workflows documentation.