Post plugin verb invocation result
Called by the daemon after executing a polled plugin verb invocation. Ordinary local-bridge results keep the existing resume behavior. `rensei.verify.run` is a strict runtime-JWT-only branch (maximum 2 MiB) requiring `X-Rensei-Claim-Acknowledgement-Receipt-Sha256`; it settles canonical result bytes and returns Donmai acknowledgement authority but never resumes the workflow. Positive continuation occurs only at acknowledgement confirmation. Duplicate settlements are replay-safe and conflict on changed stable bytes.
Rensei API key presented as Authorization: Bearer rsk_live_. Required API-key scopes are recorded per operation in x-rensei-required-scopes.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/daemon/plugin-verbs/result" \ -H "Content-Type: application/json" \ -d '{ "invocationId": "string" }'{
"ok": true,
"invocationId": "string",
"resumed": 0
}{
"error": "Session not found"
}{
"error": "Session not found"
}{
"error": "Session not found"
}Poll for a pending plugin verb invocation
The daemon polls this endpoint to pick up plugin verb invocations queued by workflow engine steps. Returns the oldest pending invocation for the daemon's org/project scope, atomically marking it as in-flight. Returns `{ invocationId: null }` when the queue is empty or the daemon lost a race. Auth: `Bearer rsk_*` via `getCliOrSessionAuth` OR runtime JWT (`authenticateDaemon`).
Confirm Donmai terminal lease acknowledgement and authorize continuation
Runtime-JWT-only confirmation for a settled `rensei.verify.run` result. Requires `X-Rensei-Confirmation-Attempt: 1|2`, exact retained settlement/result-response digests, and a canonical Donmai acknowledgement outcome. Applied outcomes may retain `release-pending` with provider release incomplete or observe `released`; permitted rejection outcomes authorize only the action-failure edge. This is the sole positive continuation authority; the result endpoint itself always reports `resumed: 0` for first settlement.