Claude
ed84b29c6b
Sentry's global integrations natively capture window.onerror / unhandledrejection (renderer) and uncaughtException / unhandledRejection (main). When a DSN is configured we let Sentry own those paths to avoid double-capturing. When it isn't (dev, unconfigured prod), we attach minimal listeners that route through reportError so stray promise rejections and uncaught errors at least hit the console and the facade. This closes the one gap where a bare click-handler promise rejection (no try/catch, not a useMutation) would otherwise be invisible.