feat(sync): render attachment-aware review output

[ctawiah]

Context

Tool and skill changes are reviewed as part of the variation that references them. This layer updates the terminal output so users can see that relationship clearly and understand exactly what will change before confirming a sync.

What changes

• Groups sync output by project, config, and variation.
• Shows every tool and skill as a separate child of its variation instead of combining several attachments into one diff.
• Labels stable keys consistently so names and identifiers are easy to distinguish.
• Uses indentation to make the resource hierarchy clear in the terminal.
• Renders attachment content in a readable form instead of showing raw API JSON.
• Keeps side-by-side diffs focused on the lines around a change.
• Separates variation content changes from tool and skill content changes.
• Avoids showing an empty-field difference when omitted maps are semantically the same as empty maps returned by LaunchDarkly.

Review focus

• Is it clear which config and variation own each attachment?
• Can a user distinguish several tools or skills attached to the same variation?
• Are the side-by-side diffs concise without hiding useful context?
• Do no-change variations avoid displaying misleading content differences?
• Does the output remain readable in both interactive and non-interactive terminals?

Verification

• go test ./internal/sync/prompt
• go test ./...
• 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
Reworks sync plan review output so project → config → variation hierarchy is obvious in the terminal, with bold headings and deeper indentation for actions and errors.

Tool and skill changes are no longer one blob of JSON or a collapsed “whole variation” diff. Each attachment is its own section (e.g. Tool "my-first-tool" (added)), with readable fields (description, schema, markdown) and (not attached) when missing; unchanged attachments are skipped. Tool/skill diffs drop @@ hunk lines, and unified diffs use 1 line of context instead of 3 for tighter side-by-side output.

Adds tests covering attachment rendering, per-skill sections, config grouping, and diff context.

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

[cursor]

Stale Bugbot comment from a previous run.

[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 1a2e390. Configure here.}

[cursor]

Markdown skill diffs break code fences

Medium Severity

Markdown review wraps skill diffs in a diff fence while skill bodies are emitted as raw markdown. An unchanged closing fence line from the skill becomes a CommonMark closer (three leading spaces plus backticks) and terminates the outer fence, so later diff lines render as broken markdown.

Additional Locations (1)

• internal/sync/prompt/diff.go#L504-L506

 

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

[cursor]

Nested schema objects dump as Go maps

Low Severity

writeDiffMap prints JSON Schema arrays with %v, so nested objects and nulls show up as Go values like map[type:string] and <nil>. Tool schemas that use anyOf, oneOf, or prefixItems are less readable than the JSON they replaced, and null defaults are easy to misread.

 

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