Feedback no browser default dialogs

Justin (2026-07-13, reviewing the drag-to-trash confirm): "never use the default dialog box, we need a native UI pop up." Browser-default dialogs (window.confirm, alert, prompt) are banned in CreatorTrack and all forge web surfaces; confirmations use an in-app styled modal matching the product UI.

Why: Default dialogs look foreign to the product, cannot be styled or animated, and read as unpolished. Justin is building CreatorTrack to product quality.

How to apply: For any confirm/prompt need, reuse the shared in-app ConfirmDialog component (created for drag-to-trash, components/workspace) or the surface's existing modal primitives. Keyboard parity is required (Enter confirms, Escape cancels). Note: the CT codebase had ~13 legacy window.confirm call sites when this rule landed; convert them opportunistically when touching those files, or as a dedicated queue task.

URL: https://mkdocs.justinsforge.com/memory/general/feedback_no_browser_default_dialogs/

[Claude Code]