Approve a run's diff
Approve a held diff, or resume a failed apply, after reviewing it.
v2 compatibility notes
POST /api/v2/knowledge/synchronized-sources/approveDiff requires knowledge:manage. The body is {sourceId, runId, expectedRevision, reviewId, mode}: expectedRevision and reviewId from a ready review page this same person read; mode is approve (the default) for a held diff, or resume for an apply that failed. The changes then apply as the approver: each write re-checks that person’s access. The answer is {sourceId, outcome, revision, progressVersion}; a repeat of the same decision answers the same result. A diff or review that changed since it was read answers 409 conflict: review it again.
Only a Personal key is admitted, acting as its owner: the owner must hold the permission where the source lives, and is recorded as the decider, with the key named in the audit. An External App or platform key answers 403 forbidden, recorded: a person reviews and decides a source’s held changes.
Send an Idempotency-Key to retry safely. A completed 200 response remains stored for 24 hours and is replayed only while the caller still holds knowledge:read and the source is still in its writable namespaces. Lost access, a missing source or a stored non-200 response yields 409 idempotency_result_unavailable; the request never runs twice.Authorizations
Headers
1–255 printable ASCII characters. A repeat with the same key and request never runs the write again, a 5xx included. It returns the first response (Idempotency-Replayed: true) only when the route's current authorization policy permits disclosure; otherwise 409 idempotency_result_unavailable. Honoured for External App JWTs and platform and MCP keys; an External App's static companion key is not protected.
1 - 255Path Parameters
Body
reviewId and expectedRevision from the ready review page, read by this same person. mode: approve (the default) a held diff, or resume an apply that failed.

