Library

Report confirmed local writes (sync receipt)

Posted by skillrepo update AFTER it confirms skills were written to disk. Records a delivery event + stamps subscriber sync state from the (owner, name, version) pairs actually written. A confirmed disk write — not a fetch response — is the single source of truth for sync status (#1832).

Entries that don't resolve to a skill the caller can access, or to a known version label, are silently dropped (stale local copy or bogus payload); the recorded count reflects only what was stored. An empty skills array is accepted and records nothing.

Per-repo attestation: an optional repo block reports which skillset the syncing repo declares and the exact (skill, version) set it is serving, with skipped-extras and counts-only violation drift signals. Recorded only for accounts with skillsets enabled; silently ignored otherwise. Additive — older CLIs omit it and get byte-identical behavior.

Rate-limit bucket: cli-crud.

post/api/v1/library/sync-receipts

Request

  • Base URL: https://skillrepo.dev
  • URL: https://skillrepo.dev/api/v1/library/sync-receipts
  • Auth: HTTP bearer

Request body

syncedAtstring date-time required

Client timestamp of the sync that produced these writes. Used as the delivery event time and the per-UTC-day dedup key. Rejected (400) if more than 5 minutes in the future: a receipt records a write that already happened, and an unbounded future timestamp could otherwise game the fleet-view freshness buckets or burn a future dedup slot. The CLI sends the server's own response syncedAt, so a legitimate receipt is always at/near now.

Response

Receipt processed.

recordedinteger required

How many (skill, version) pairs resolved to an accessible skill and a real version label and were recorded. Entries that don't resolve are silently dropped and excluded from this count.

Changes

No recorded changes to this operation across all 1 revision of this API.