fix(web): serve Nitro assets reliably

Co-authored-by: multica-agent <github@multica.ai>

Dockerfile

@@ -61,11 +61,6 @@ COPY --from=build /app/apps/worker apps/worker
 COPY --from=build /app/packages/shared packages/shared
 COPY --from=build /app/packages/game-engine packages/game-engine
 
-# Nitro 2.10 resolves file-backed public assets from the directory containing
-# its split runtime chunk. Keep the generated output in its standard location
-# and expose it at that runtime path without storing a second copy.
-RUN ln -s ../../public apps/web/.output/server/chunks/public
-
 EXPOSE 3000
 
 # Coolify (and other hosts) override PORT at runtime; probe that port, not a

apps/web/nuxt.config.ts

@@ -3,6 +3,13 @@ export default defineNuxtConfig({
   devtools: { enabled: false },
   css: ['~/assets/css/main.css'],
   modules: [],
+  nitro: {
+    // Nitro 2.10 resolves file-backed assets relative to its split runtime
+    // chunk, which makes every /_nuxt request fail outside the Docker-only
+    // symlink workaround. Embedding them keeps every production launcher
+    // (preview, Docker, and managed hosts) on the same reliable code path.
+    serveStatic: 'inline',
+  },
   runtimeConfig: {
     aiProvider: process.env.AI_PROVIDER ?? 'openrouter',
     openrouterApiKey: process.env.OPENROUTER_API_KEY,