fix(sync): confirm destructive watch actions

[ctawiah]

Context

Watch mode currently treats every filesystem-triggered sync as pre-approved. That is convenient for routine edits, but it also allows a local deletion to archive a LaunchDarkly variation, or a server deletion to remove a local file, without confirmation.

What changes

• Continue applying create and update actions automatically in watch mode.
• Ask for confirmation before archive or local-delete actions.
• Preserve --watch --yes as the explicit non-interactive opt-in.
• Reject unconfirmed destructive actions when no terminal is available.

For example:

Action: Archive the variation in LaunchDarkly

Sync these changes? [y/N]

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
Watch mode no longer auto-applies every sync. Routine creates/updates still apply without a prompt, but plans that archive in LaunchDarkly or delete local files require interactive confirmation (or explicit --yes).

Adds Plan.HasDestructiveActions() to drive that policy and refactors watch sync options via optionsForWatchSync, which clears one-shot flags (--add, --link, etc.) without forcing --yes on each watcher-triggered run.

Confirmation during watch uses context-aware confirmApplyWithContext so interrupt/cancel can unblock a pending [y/N] read instead of hanging the watcher loop.

^{Reviewed by Cursor Bugbot for commit 7046994. 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 1 potential issue.

^{❌ 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 4923245. Configure here.}