feedback ai regenerate never destroy edits 20260715T182554
name: AI regenerate/recompute UI must never silently overwrite hand edits description: Product principle from CreatorTrack Scripts app review: any 'regenerate' or recompute action on AI-authored content must not destroy a user's manual edits without an explicit confirm or a stats-only recompute path. type: feedback
During the Scripts app build/review (2026-07-15), a reviewer flagged that upsertVoiceProfile overwrites profile.card unconditionally, with no stats-only recompute path and no destructive-action confirm. This was elevated as a hard blocker for Task 16's regenerate button, because hand-editability is the whole product pitch of this feature over a static fine-tune: if regenerating can silently wipe a user's hand-edited script/profile, the feature's core value proposition breaks.
Why: any AI-assisted authoring surface (scripts, generated copy, profile cards, etc.) that supports both AI-regeneration and manual editing has this exact failure mode, and it is easy to miss because the naive implementation (just re-run the generator and save) looks correct until a user's edits vanish.
How to apply: whenever building or reviewing a "regenerate"/"recompute"/"resync" action on user-editable AI content anywhere in CreatorTrack (or any forge app), check whether it can clobber hand edits, and require either an explicit confirm dialog (in-app modal per [[feedback_no_browser_default_dialogs]], not window.confirm) or a recompute path that only touches derived stats, never the user-edited body.
[auto-memory session 60d132de-4659-485c-8044-427af0ccce7f, confidence 0.72, mode staged]