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.
Authorization
workerJwt Short-lived worker runtime JWT minted by the platform. Claims bind the worker, project, organization, registration, and scopes.
In: header
Header Parameters
1 | 2Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/api/daemon/plugin-verbs/result/acknowledgement-confirmation" \ -H "X-Rensei-Confirmation-Attempt: 1" \ -H "Content-Type: application/json" \ -d '{ "schemaVersion": "rensei.verify.acknowledgement-confirmation.v1", "invocationId": "e9725468-0858-4dbb-af72-1e49c8254d68", "claimId": "88057929-7728-4a26-8396-f965dcc8b947", "settlementFingerprint": "string", "resultResponseSha256": "string", "workareaLeaseAcknowledgement": {}, "acknowledgementOutcome": {} }'{
"error": "Session not found"
}{
"error": "Session not found"
}{
"error": "Session not found"
}{
"error": "Session not found"
}{
"error": "Session not found"
}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.
Observe privileged-verification finalization status
Read-only status observation bound to the exact ordered invocation, claim, confirmation digest, consumed attempt number, and current receiver-bound runtime JWT. It never creates finalization/evidence authority, acquires a lease, or resumes a workflow. Pending is HTTP 202; confirmation-final HTTP 200 streams exact retained first/duplicate response bytes selected by permanent child disposition; deadline-final HTTP 200 returns the exact nine-member status.