diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 5e2f3491..3d362178 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -72,49 +72,8 @@ jobs:
       - name: Test
         run: bun test
 
-  e2e:
-    name: E2E
-    runs-on: ubuntu-latest
-    timeout-minutes: 20
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Set up Bun
-        uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: 1.3.11
-
-      - name: Install dependencies
-        run: bun install --frozen-lockfile
-
-      # Playwright pins a browser build per version; cache it keyed on the
-      # installed @playwright/test version so we only re-download on upgrades.
-      - name: Resolve Playwright version
-        id: pw
-        shell: bash
-        run: echo "version=$(bun pm ls 2>/dev/null | grep -oE '@playwright/test@[^ ]+' | head -n1 | cut -d@ -f3)" >> "$GITHUB_OUTPUT"
-
-      - name: Cache Playwright browsers
-        id: pw-cache
-        uses: actions/cache@v4
-        with:
-          path: ~/.cache/ms-playwright
-          key: playwright-${{ runner.os }}-${{ steps.pw.outputs.version }}
-
-      - name: Install Playwright browser
-        run: bunx playwright install --with-deps chromium
-
-      # The Playwright config starts its own stack via `bun run e2e:dev`
-      # (Vite + Bun CMS on a disposable SQLite DB), so no services are needed.
-      - name: Run E2E tests
-        run: bun run test:e2e
-
-      - name: Upload Playwright report
-        if: ${{ !cancelled() }}
-        uses: actions/upload-artifact@v4
-        with:
-          name: playwright-report
-          path: .tmp/playwright-report
-          retention-days: 7
-          if-no-files-found: ignore
+# NOTE: The Playwright E2E suite is intentionally NOT run in CI yet. As
+# configured (`workers: 1`, fully serial, 156 tests) it takes ~45-60 min and is
+# timeout-fragile against the un-optimized dev server, so it cannot gate PRs
+# reliably today. Run it locally with `bun run test:e2e`. It will be reintroduced
+# as its own workflow once the suite is sharded/parallelized and stabilized.