Merge pull request #90 from sidclawhq/fix/browser-ci-production-servers

fix(browser-tests): production Next builds in CI, dev servers locally

Author: VladUZH

playwright.config.ts

@@ -15,6 +15,11 @@ export default defineConfig({
     trace: 'on-first-retry',
     viewport: { width: 1440, height: 900 },
   },
+  // In CI the Next.js apps run PRODUCTION builds: dev servers compile each
+  // page on first hit, and on a 2-core runner those compiles blow the 30s
+  // selector timeouts (validation run 30460483491: 35 timeout failures that
+  // never reproduce locally). The API keeps its dev server everywhere — tsx
+  // has no per-page compile step.
   webServer: [
     {
       command: 'cd apps/api && npm run dev',
@@ -23,19 +28,21 @@ export default defineConfig({
       timeout: 30000,
     },
     {
-      command: 'cd apps/dashboard && npm run dev',
+      command: process.env.CI
+        ? 'cd apps/dashboard && npm run build && npm run start'
+        : 'cd apps/dashboard && npm run dev',
       port: 3000,
       reuseExistingServer: true,
-      timeout: 30000,
+      timeout: process.env.CI ? 420000 : 30000,
     },
     {
       // The landing-page specs (01-*) target the landing app directly.
-      // Locally an absent server made them skip; in CI they hard-failed
-      // with ERR_CONNECTION_REFUSED on the suite's first scheduled run.
-      command: 'cd apps/landing && npm run dev',
+      command: process.env.CI
+        ? 'cd apps/landing && npm run build && npm run start'
+        : 'cd apps/landing && npm run dev',
       port: 3002,
       reuseExistingServer: true,
-      timeout: 60000,
+      timeout: process.env.CI ? 420000 : 60000,
     },
   ],
   projects: [