v0.2 Phase 8: full release gate — all checks green

cargo fmt --check                                         ✓
  cargo clippy --workspace --all-targets -- -D warnings     ✓
  cargo test --workspace                                    ✓
  cargo nextest run --workspace                             ✓ 435/435
  npm run check                                             ✓ 0/0/5704 files
  npm test                                                  ✓ 13/13 (2 files)
  npm run test:browser                                      ✓ 3/3 in Chromium
  npm run test:e2e                                          ✓ 16/16 × 2 viewports
  npm run analyze                                           ✓ reports/bundle-stats.html (1.7 MB)
  scripts/dogfood-rebrand-drill.sh                          ✓ 8/8 (sandbox)
  npm run guard:no-skeleton                                 ✓ clean

Two small Phase 8 corrections landed alongside the gate:

vite.config.js: the jsdom suite was picking up
`src/lib/ui/*.browser.test.ts`, which only works under the
@vitest/browser-playwright provider. Added the browser-suffix glob to
the jsdom suite's exclude list so the two runners stop double-running
the same files.

playwright.config.ts: bumped the global `expect.timeout` to 15 s. The
cold first-compile of the Vite SPA tree was exceeding Playwright's
default 5 s `toBeVisible` timeout on the 900x700 project on dogfood
runs. The 1440x900 project (which runs second after a warm cache)
never hit it.

Phase 8 closes Phase-7 page migrations. Branch is ready for the
finishing-a-development-branch handoff.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-15 09:07:10 +01:00
parent ba851680ce
commit f03f8a01b0
3 changed files with 17 additions and 3 deletions

View File

@@ -15,6 +15,11 @@ export default defineConfig({
retries: process.env.CI ? 2 : 0,
reporter: [["list"], ["html", { open: "never", outputFolder: "playwright-report" }]],
outputDir: "test-results",
// Vite's first compile of the SPA tree can blow past the default 5s
// expect timeout on cold runs (especially on the 900x700 project,
// which fires before any module cache is warm). Bumping the global
// expect timeout avoids per-test {timeout: …} sprinkles.
expect: { timeout: 15_000 },
use: {
baseURL: "http://localhost:1420",
trace: "on-first-retry",