fix(browser): Remove development-only wrapper from Spotlight auto-enablement

The Spotlight auto-enablement code was wrapped in rollup-include-development-only,
which stripped it from production builds. But users install production builds of
the SDK from npm and still expect auto-enablement to work during their app's
development (when they set NEXT_PUBLIC_SENTRY_SPOTLIGHT=true, etc.).

The env vars won't be set in production deployments anyway, and users can
explicitly disable Spotlight with `spotlight: false` if needed.

Author: BYK

packages/browser/src/sdk.ts

@@ -96,8 +96,12 @@ export function init(options: BrowserOptions = {}): Client | undefined {
   let defaultIntegrations =
     options.defaultIntegrations == null ? getDefaultIntegrations(options) : options.defaultIntegrations;
 
-  /* rollup-include-development-only */
-  // Resolve Spotlight configuration with proper precedence
+  // Resolve Spotlight configuration with proper precedence.
+  // This code is intentionally NOT wrapped in rollup-include-development-only because:
+  // - Users install production builds of the SDK from npm
+  // - They expect auto-enablement to work during their app's development
+  // - The env var (NEXT_PUBLIC_SENTRY_SPOTLIGHT, etc.) won't be set in production deployments
+  // - Users can explicitly disable with `spotlight: false` if needed
   const envSpotlight = getSpotlightConfig();
   // resolveSpotlightOptions is the single source of truth that ensures empty strings are never used
   const spotlightValue = resolveSpotlightOptions(options.spotlight, envSpotlight);
@@ -109,7 +113,6 @@ export function init(options: BrowserOptions = {}): Client | undefined {
     const args = typeof spotlightValue === 'string' ? { sidecarUrl: spotlightValue } : undefined;
     defaultIntegrations.push(spotlightBrowserIntegration(args));
   }
-  /* rollup-include-development-only-end */
 
   const clientOptions: BrowserClientOptions = {
     ...options,