[ctawiah]

Context

A push of a linked variation ends with a patch of the remote sync manifest, and LaunchDarkly rejected it with /properties/upserts/items/additionalProperties additional properties 'fingerprintSchema', 'referenceDigest', 'adapterBehavior' not allowed. The variation was written, the baseline was not, so the next plan saw the push again. The remote manifest records the fingerprint and the version of each entry, and nothing else.

What changes

• SyncManifestResource and SyncManifestUpsert carry the kind, the lookup key, the fingerprint, and the version only.
• The store sends an upsert when the fingerprint of an entry changed. A change to the descriptor metadata of a linked resource alone sends nothing.
• The sync.lock file keeps the descriptor metadata, as before. The lock travels with the repository, so every working copy reads it from there.

Design notes

• The remote manifest gives each entry a version for optimistic concurrency and a fingerprint for the stale check between working copies. Neither needs the descriptor metadata, which the planner reads from the lock.

Review focus

• Is any other place expecting the descriptor metadata in the remote manifest?

Verification

• go test ./...
• golangci-lint run ./...
• TestStoreUpdatesWithRemoteVersions asserts the upsert without the metadata, and TestStoreSendsNothingForADescriptorMetadataChange covers a metadata-only change.
• Against staging: the push of a linked variation returned the schema error above.

Related changes

• fix(sync): accept an empty remote manifest without a format version #1025 and fix(sync): drop formatVersion from the sync manifest API #1026 removed the remote format version. This pull request completes the match with the API shape.

🤖 Generated with Claude Code

---

Note

Overview
Stops sending descriptor metadata (fingerprintSchema, referenceDigest, adapterBehavior) in remote sync manifest API payloads, which LaunchDarkly rejects as additional properties and was blocking baseline updates after linked variation pushes.

SyncManifestResource and SyncManifestUpsert now only expose kind, lookup key, fingerprint, and version. The manifest store loads and patches with that same subset, and sameManifestContent compares fingerprints only, so updates that change lock-only descriptor metadata without a fingerprint change do not emit a patch. Descriptor metadata remains on local manifest/sync.lock resources as before.

^{Reviewed by Cursor Bugbot for commit a7dcd10. Bugbot is set up for automated code reviews on this repo. Configure here.}