Chromium's crash reports reach the server, which logs each and files it in Sentry as a warning, and the page's own errors name the room and seat and leave extensions' failures out

A tab that crashes takes the page's error reporting down with it, so the
page never says so. Every page now names a default Reporting API endpoint,
/api/reports, where Chromium sends a crash report after the fact; the
server logs the room, the reason when one is given, and the browser, and
files a warning that rings no bell. Other report types are ignored, and an
address may send ten an hour.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0141G6xqLeNRYEtviLWSB5Up

packages/web/src/main.ts

@@ -10,7 +10,8 @@ if (import.meta.env.VITE_SENTRY_DSN) {
     environment: "production",
     // Facebook's in-app browser injects its own scripts (iabjs://) and
     // reports their failures as ours when the page unloads.
-    denyUrls: [/^iabjs:\/\//],
+    // Extensions run their own scripts in the page, and their failures are not ours.
+    denyUrls: [/^iabjs:\/\//, /^(chrome|moz|safari(-web)?)-extension:\/\//],
     ignoreErrors: ["Java object is gone"],
   });
 }