Workflows can expose a button to another product
A surface entry and a reply output let FerrTrack start a workflow and read its typed answer.
A workflow entry can now be of kind surface: a labelled button, with an icon, that another product shows and that starts the workflow. The first placement is ferrtrack.new_issue. The new reply output checks the result of a step against the placement's reply schema and keeps it, with no connector and no network call. A product lists the surfaces with GET /surfaces, starts one with POST /surface-runs and polls GET /surface-runs/{id}, which answers only the status, the queue position and the reply. An organization has at most 5 surface runs active at once. Agents also take options.tools with allow and deny lists, merged into the tool lists of their runs.