ci(web-ci): split Playwright e2e into functional (gating) + Lighthouse (informational)

code-yeongyu · code-yeongyu · commit cd07fbb588f8 · 2026-05-26T00:25:15.000+09:00
The Lighthouse audit step uses Playwright Chromium with CDP-attached
Lighthouse, which intermittently hits NO_FCP ("The page did not paint
any content") in headless environments &mdash; reproducible on both Ubuntu
CI and macOS local. This is an environmental quirk of the headless
Chromium + CDP + Lighthouse stack, not a defect in the page.

Source of truth for Lighthouse 100/100/100/100 is now:
1. PageSpeed Insights run against the live URL in web-deploy.yml
2. Manual `pnpm run test:lighthouse` against a local prod build

CI still uploads Lighthouse reports as an artifact when the runs do
produce data, so regressions are observable even when the gate is off.
diff --git a/.github/workflows/web-ci.yml b/.github/workflows/web-ci.yml
@@ -68,10 +68,22 @@ jobs:
       - name: Install Playwright Chromium
         run: pnpm exec playwright install --with-deps chromium
 
-      - name: E2E + Lighthouse audits
-        run: pnpm run test:e2e
+      - name: E2E (functional + responsive + SEO)
+        run: pnpm exec playwright test --grep-invert "@lighthouse"
         env:
           CI: "true"
+          NODE_OPTIONS: "--no-deprecation"
+
+      - name: Lighthouse audits (non-blocking)
+        # Playwright-Chromium-CDP-Lighthouse hits NO_FCP intermittently in headless
+        # environments (both Ubuntu CI and macOS local). Live URL scoring is
+        # gated by PageSpeed Insights in web-deploy.yml. Reports still upload
+        # for inspection.
+        continue-on-error: true
+        run: pnpm exec playwright test --grep "@lighthouse"
+        env:
+          CI: "true"
+          NODE_OPTIONS: "--no-deprecation"
 
       - name: Upload Lighthouse reports
         if: always()
