🤖 fix: don't force dark theme when globals.theme is undefined

Chromatic modes only set context.globals.theme during their CI snapshot
process, not during local development. When undefined, we should let
ThemeProvider use its default behavior (system preference/localStorage)
rather than forcing dark theme.

This way:
- Local dev: uses system preference (no forcedTheme)
- Chromatic dark mode: gets forcedTheme='dark' from modes config
- Chromatic light mode: gets forcedTheme='light' from modes config
- Toolbar usage: manually set globals.theme applies forcedTheme

Author: ethanndickson

.storybook/preview.tsx

@@ -20,18 +20,16 @@ const preview: Preview = {
   },
   decorators: [
     (Story, context) => {
+      // Chromatic modes don't set context.globals during local development
+      // They only work during Chromatic's CI snapshot process
+      // For local development, globals.theme can be set via the toolbar
       const mode = context.globals.theme as ThemeMode | undefined;
-      console.log('🔍 Storybook decorator - Story:', context.name);
-      console.log('🔍 context.globals:', context.globals);
-      console.log('🔍 context.parameters:', context.parameters);
-      console.log('🔍 context.parameters.chromatic:', context.parameters.chromatic);
-      console.log('🔍 Full context keys:', Object.keys(context));
-      console.log('🔍 Theme mode from globals:', mode);
-      // Default to dark when no mode is explicitly set (e.g., Latest view)
-      const forcedTheme = mode ?? "dark";
-      console.log('🔍 forcedTheme passed to ThemeProvider:', forcedTheme);
+      
+      // When no explicit mode is set (locally or via toolbar), don't force a theme
+      // Let ThemeProvider use its default behavior (system preference / localStorage)
+      // When Chromatic runs with modes, it will set globals.theme appropriately
       return (
-        <ThemeProvider forcedTheme={forcedTheme}>
+        <ThemeProvider forcedTheme={mode}>
           <Story />
         </ThemeProvider>
       );