Human-confirmation step: executes a staged coordinator pending action
POST/api/coordinator/pending-actions/:id/execute
Human-confirmation step: executes a staged coordinator pending action. A pending action is created when a user stages one of the coordinator brain’s suggested writes (via the prepare route) — artifact promotion (create_task, link_to_existing, and draft_spec — staged as the pending-action kind draft_spec_pr), a ticket-management mutation (update_priority, transition_status, assign, update_due_date, edit_description), or a cycle assignment (assign_task_to_cycle). This route is the ONLY write path — there is no direct-mutation bypass. The optional mutationPolicyOverride in the request body may tighten (never loosen) the code-declared confirm-required ceiling.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 410
- 501
Successful response
mutation_policy_escalation — mutationPolicyOverride attempts to widen beyond the code-declared ceiling, or unknown override value / missing path param; or an invalid staged-action argument (e.g. a malformed cycleId, a rejected cycle membership, an out-of-range priority or unknown status).
Caller is not authenticated.
Coordinator is in read-only mode for this initiative.
Pending action not found (or not visible to the caller via RLS).
Pending action is already in a terminal status (executed / cancelled / failed).
Pending action TTL has elapsed (expires_at is in the past).
draft_spec_pr action kind — outbound GitHub PR creation is not yet implemented (follow-up: PLT-391).