Candidate identity and request boundaries

These two operations consume existing structured Skill Creator candidates; they do not generate candidates first. Confirmation does not additionally require the task to be terminal, and completed execution does not mean the candidate was saved. A verifiable existing candidate is required.

Information

Usage

task_id

Original runtime task ID. The service checks workspace, task ID, and whether the current principal is the original task.UserID.

call_id

Original native gateway audit event’s tool-call ID. Do not generate a new one to bypass an unknown result.

source_digest

Server-generated sha256 digest of canonical candidate display serialization. Copy the complete returned value rather than recalculating it from UI text.

agent_id / agent_workspace_id

Candidate target from the original task and manifest. The confirmation body cannot change the target.

can_bind_current

Candidate eligibility within the same workspace and from a non-system source; does not prove the current principal has update privileges.

display

name/description/instruction/change_reason and optional files for review only. Confirmation does not resubmit editable content.

The permission boundary requires regular workspace access. The service also validates task/manifest/owner and the original source event. An API Key or Workspace Owner status alone does not allow confirming another user’s candidate. Only records matching task/workspace/call/tool and the candidate digest in the original native gateway audit are accepted. Regular model display events and arbitrary chat text are not savable drafts.

POST allows only call_id, source_digest, and bind_current in the body, all required and non-null. Nonobjects, unknown keys, and trailing JSON within the parse window are rejected. Reading is bounded to 8 MiB; this is not a general413 upload contract and does not guarantee rejection of duplicate JSON keys. This operation does not upload ZIPs or submit arbitrary skill content.

GET uses the first query call_id/source_digest; the service rejects missing/empty values. The path workspace must match the header. Both operations require original candidate identity. Frontend cards show at most20000 characters per preview and may truncate. Check the full structured candidate before confirmation; a preview is not complete file content. This describes source-level UI behavior, without live page acceptance testing.

Last updated on