Move client build to Docker build phase to avoid runtime memory limits

- Pre-build both server and client during Docker build (more memory available)
- Remove runtime client build that was causing JavaScript heap out of memory
- Server runs immediately with pre-built assets
- Should resolve 404 errors from missing client/dist/ directory

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

Author: ZRTMRH

.devcontainer/Dockerfile

@@ -52,9 +52,11 @@ COPY --chown=node:node . .
 # Build the project (only this step runs if game files change)
 RUN echo "Building Lean project..." && lake build
 
-# Pre-build lean4game server to avoid runtime delays (client builds at runtime)
-RUN echo "Pre-building lean4game server..." && \
-    cd /home/node/lean4game && npm run build_server
+# Pre-build lean4game server and client to avoid runtime memory issues
+RUN echo "Pre-building lean4game server and client..." && \
+    cd /home/node/lean4game && \
+    npm run build_server && \
+    npm run build_client
 
 # Apply port binding fix to relay server
 COPY relay-patch.mjs /home/node/lean4game/relay/index.mjs

start-server.sh

@@ -59,8 +59,7 @@ echo "ASSIGNED_PORT=$ASSIGNED_PORT"
 echo "PORT (from Render)=${PORT:-'not set'}"
 
 echo "Starting server in production mode for memory efficiency..."
-echo "Building client for production..."
-cd /home/node/lean4game && npm run build_client
+echo "Client should be pre-built during Docker build phase..."
 echo "Verifying lean4game relay server exists..."
 if [ -f "/home/node/lean4game/relay/index.mjs" ]; then
     echo "✅ Relay server found!"