Fix CI: resolve RSC bundle and server bundle build errors

Two issues:
1. RSC bundle (127 errors): Remove server-bundle-generated.js import from
   rsc-bundle.js. It includes RouterApp.server.jsx (traditional SSR component)
   that uses react-redux/react-router with client-only React APIs incompatible
   with the react-server condition. Client references are handled automatically
   by the RSC loader/plugin.

2. Server bundle (3 errors): Add Node.js builtin fallbacks (path, fs, stream)
   to server webpack config. react-on-rails-pro now includes RSC modules that
   import these builtins, but they aren't used in the traditional SSR path.

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

Author: justin808

client/app/packs/rsc-bundle.js

@@ -3,11 +3,14 @@
 // It imports the same client component registrations as server-bundle.js,
 // plus the server component registrations.
 
-// Import existing client component registrations
+// Import stores registration (has 'use client' — RSC loader replaces with client reference)
 import './stores-registration';
-import './../generated/server-bundle-generated.js';
 
 // React Server Components registration (server-side)
+// Note: server-bundle-generated.js is NOT imported here because it contains
+// traditional SSR components (e.g., RouterApp.server.jsx) that use client-only
+// React APIs (useState, Component, etc.) incompatible with the react-server condition.
+// Client component references are handled automatically by the RSC loader/plugin.
 import registerServerComponent from 'react-on-rails-pro/registerServerComponent/server';
 import ServerComponentsPage from '../bundles/server-components/ServerComponentsPage';
 

config/webpack/serverWebpackConfig.js

@@ -171,6 +171,17 @@ const configureServer = () => {
     'react-dom/server.browser.js$': 'react-dom/server.node.js',
   };
 
+  // react-on-rails-pro includes RSC-related modules that import Node.js builtins
+  // (path, fs, stream). These code paths aren't used in the traditional SSR bundle,
+  // so provide empty fallbacks to avoid resolution errors.
+  serverWebpackConfig.resolve.fallback = {
+    ...serverWebpackConfig.resolve.fallback,
+    path: false,
+    fs: false,
+    'fs/promises': false,
+    stream: false,
+  };
+
   return serverWebpackConfig;
 };