fix(web): enable Sentry tracing and restore client-side Sentry

Renames sentry.client.config.ts to instrumentation-client.ts, which
Next.js loads itself. The old file was only wired in by @sentry/nextjs'
webpack plugin, which never runs: next build defaults to Turbopack in
Next 16, and next.config.mjs defines a turbopack block, so Next's
"webpack config with no turbopack config" guard passes silently. Client
errors, replays and spans were therefore never reported in production.

Exports onRouterTransitionStart so App Router client-side navigations
are instrumented as spans; Next only reads that export from
instrumentation-client.ts.

Sets tracesSampleRate on client, server and edge. Tracing is off unless
this option is present at all, since hasSpansEnabled() checks for
non-nullish. Sampling every trace for now to get a read on span volume
before tuning the rate down.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: brendan-kellam

packages/web/src/sentry.client.config.ts …ckages/web/src/instrumentation-client.tspackages/web/src/sentry.client.config.ts renamed to packages/web/src/instrumentation-client.ts packages/web/src/sentry.client.config.ts renamed to packages/web/src/instrumentation-client.ts

@@ -1,6 +1,10 @@
 // This file configures the initialization of Sentry on the client.
 // The config you add here will be used whenever a users loads a page in their browser.
 // https://docs.sentry.io/platforms/javascript/guides/nextjs/
+//
+// Must be named `instrumentation-client.ts`. Next.js loads this file itself, whereas
+// `sentry.client.config.ts` is only picked up by @sentry/nextjs' webpack plugin,
+// which never runs since `next build` defaults to Turbopack.
 
 import * as Sentry from "@sentry/nextjs";
 
@@ -9,9 +13,15 @@ if (!!process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN && !!process.env.NEXT_PUBLIC_SEN
         dsn: process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN,
         environment: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT,
 
+        tracesSampleRate: 1.0,
+
         // Setting this option to true will print useful information to the console while you're setting up Sentry.
         debug: false,
     });
 } else {
     console.debug("[client] Sentry was not initialized");
 }
+
+// Instruments App Router client-side navigations as spans. Next.js only reads this
+// export from `instrumentation-client.ts`. A no-op when Sentry is uninitialized.
+export const onRouterTransitionStart = Sentry.captureRouterTransitionStart;

packages/web/src/sentry.edge.config.ts

@@ -10,6 +10,8 @@ if (!!process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN && !!process.env.NEXT_PUBLIC_SEN
         dsn: process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN,
         environment: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT,
 
+        tracesSampleRate: 1.0,
+
         // Setting this option to true will print useful information to the console while you're setting up Sentry.
         debug: false,
     });

packages/web/src/sentry.server.config.ts

@@ -12,6 +12,8 @@ if (!!process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN && !!process.env.NEXT_PUBLIC_SEN
         dsn: process.env.NEXT_PUBLIC_SENTRY_WEBAPP_DSN,
         environment: process.env.NEXT_PUBLIC_SENTRY_ENVIRONMENT,
 
+        tracesSampleRate: 1.0,
+
         // Setting this option to true will print useful information to the console while you're setting up Sentry.
         debug: false,
     });