Skip to main content
Status checked 2026-10-22 against main revision 37c75867e53dbcb92e1360cfa3a8bbb0fb9c67ae. The current routes and parsed OpenAPI expose no Studio conductor rule or trigger operations, dry-run endpoints, or conductor setup reads. Existing AgentConfigurations::Commands is internal implementation and does not establish an HTTP publish, check, trigger, or history API. The agent configuration route show/rollback operations are version/route surfaces owned by ENG-5852 and are not conductor CRUD.

Shared lifecycle and version behavior

conductor.publish and agents.publish reference the same missing publish HTTP surface, canonically owned by ENG-5888, through the shared version/rollback concept documented by the Agent configuration versions page. They do not represent separate implementations. conductor.pauseAgent and conductor.resumeAgent reference the single ENG-5890 agent lifecycle family; they are not extra operations. Dry runs currently have no callable API. Zero-live-effect behavior and trigger idempotency plus actor audit are future requirements owned by ENG-5892. Nothing in current routes or internal command services proves those guarantees. No HTTP paths, request/response schemas, scopes, event names, or final operation IDs are assigned here.