Skip to main content
Reconcile one persisted artifact with configured object storage
Audience: developers repairing or checking the storage state of one persisted artifact.

Coverage and source scope

Checks the saved record against configured R2 storage. Without R2 configuration it reports local_only; with R2 it can report an existing object as synced, repair a missing stored object as recovered, or upload a local record as uploaded. Send no request fields.

Canonical metadata

  • artifactId
  • status
  • storageMode
  • objectKey
  • requestId

Example request

Example response

Storage outcomes

Send no fields: omit the body or send {}. If R2 is not configured, the result is local_only. With R2 configured, synced means the recorded object exists, recovered means a missing recorded object was uploaded again, and uploaded means a local record was uploaded. The result reports storage state; it does not re-derive, validate, or refresh the filing content.

Errors

Unknown body fields return 400 validation_error. A missing, inaccessible, or failed reconciliation returns 404 artifact_reconcile_failed.

Give this prompt to your agent

Failure posture

  • do not represent storage reconciliation as source-data validation
  • preserve requestId and objectKey with a reconciliation report
  • re-fetch the manifest or download only after recording the returned storage state