fix(sync): guarantee prompt fingerprint convergence

[ctawiah]

Context

Prompt sync uses fingerprints to decide whether local and LaunchDarkly variations still represent the same state. Equivalent API defaults could produce different fingerprints, and an omitted custom model version previously could not converge with the concrete version stored by LaunchDarkly.

What changes

• Normalize only equivalent API defaults: absent versus empty parameters and custom maps.
• Treat an omitted custom model version as “follow latest” at sync time; explicit versions remain pinned.
• Fetch the exact model config by key, which returns its latest version without listing the project catalog.
• Resolve that authored intent before planning, while leaving the local file unchanged.
• Revalidate the complete plan once after confirmation instead of rereading every resource before its write.
• Preserve the existing verification read for uncertain writes whose response may have been lost.

For example, this authored intent remains unchanged:

modelConfigKey: claude-prod

If the current version is 4, sync plans and applies the effective variation with modelConfigVersion: 4. A later model-config release is picked up by the next sync.

Verification

• go test ./internal/sync/...
• go test ./...
• go vet ./internal/sync/... ./cmd/sync
• Create and update convergence acceptance tests
• git diff --check

Related changes

Review the stack in this order:

1. Confirm destructive watch actions
2. Guarantee prompt fingerprint convergence
3. Add searchable attachment API foundations
4. Reconcile variation attachments
5. Attach tools and skills to variations
6. Render attachment-aware review output
7. Safely clean unreferenced attachments
8. Persist sync manifests in LaunchDarkly

---

Note

Overview
Fixes prompt sync so equivalent LaunchDarkly API shapes and “follow latest” model configs stop causing endless drift.

Fingerprinting now strips only API-noise defaults—empty parameters and custom maps—while still treating other empty model fields (e.g. metadata) as meaningful.

Model config intent: omitted modelConfigVersion means follow latest. Planning calls the new ModelConfig GET-by-key, resolves version and merged model in memory, and pushes the resolved version on create/update to the server. Local files keep version 0 on pull when follow-latest is intended; LocalFollowsLatestModelConfig drives that behavior and local verification fingerprints.

Concurrency: per-write verifyResourceUnchanged is removed; the runner still re-plans once after confirmation via samePlanState. Uncertain server writes still verify with a read.

Watch mode: non-destructive plans auto-apply without --yes; archives/deletes still prompt (or need --yes). Confirmation respects cancel via context; watch no longer forces Yes: true on each tick.

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

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b72f419. Configure here.}