fix: remove outputFileTracingRoot — conflicts with turbopack.root in Next.js 16

Next.js 16 requires outputFileTracingRoot and turbopack.root to have the same
value. Setting outputFileTracingRoot to web/ overrode turbopack.root (desktop/)
and broke pnpm symlink resolution during the production build.

The nested standalone layout (web/server.js) is already handled by the updated
prepare-web.js and electron/main.js, so outputFileTracingRoot is not needed.

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

Author: mehdiraized

overlay/next.config.ts

@@ -9,11 +9,6 @@ const nextConfig: NextConfig = {
   // Safe: this only applies in development; has no effect in production builds.
   allowedDevOrigins: ["127.0.0.1"],
   serverExternalPackages: ["just-bash", "bash-tool", "node-liblzma", "@mongodb-js/zstd", "@secure-exec/node", "@secure-exec/core", "isolated-vm", "esbuild"],
-  // Set the standalone output file tracing root to web/ itself.
-  // Without this, Next.js uses the pnpm workspace root (desktop/) as the tracing root,
-  // which causes server.js to be nested at web/server.js inside the standalone output
-  // instead of at the root — breaking the Electron production launcher.
-  outputFileTracingRoot: path.resolve(__dirname),
   // Set the Turbopack workspace root to desktop/ (one level above web/).
   // With pnpm workspaces, all node_modules live in desktop/node_modules/ and
   // web/node_modules/ contains symlinks pointing up to desktop/node_modules/.pnpm/.