fix(e2e): add smoke fail-fast project to abort on broken-infra runs

[mborgeson]

Summary

Adds a one-shot smoke Playwright project that runs before every other project. When it fails, Playwright skips dependents and the suite exits in <2 minutes instead of running ~40 minutes of redundant red across 400+ tests.

What it does

The smoke test (e2e/smoke.spec.ts) validates the most fundamental contract in a single navigation:

1. page.goto('/') redirects an unauthenticated user to /login — proves dev server is reachable, Vite served the bundle, router booted, and the auth gate ran.
2. getByLabel(/email/i) is visible on /login — proves React actually rendered (no white-screen hydration crash).

Wire-up in playwright.config.ts:

• New smoke project: testMatch: /smoke\.spec\.ts/, retries: 0.
• chromium and ci gain dependencies: ['smoke'] and testIgnore: /smoke\.spec\.ts/ so the smoke spec runs exactly once, before everything else.

Why standalone (no auth dependency)

The smoke test deliberately does NOT depend on auth, storageState, or any backend behavior beyond the login page being reachable. This is the right scope for a fail-fast check:

• A broken auth fixture should NOT mask a healthy app and abort the suite.
• A broken app should NOT be obscured by an auth setup race.
• The check has to run before auth even has a chance to matter.

Composition with PR #12 (auth fixture setup)

PR #12 introduces a setup project that authenticates and persists storageState to e2e/.auth/admin.json. Both can coexist cleanly: when PR #12 lands, chromium and ci simply list dependencies: ['smoke', 'setup']. The smoke project gates everything; the setup project warms credentials only for tests that need them. Order between them is unimportant because smoke does not consume storageState.

This PR is branched from origin/main, so the conflict surface with PR #12 is just the dependencies array on chromium and ci. Trivial to resolve in whichever PR lands second.

Expected impact

Scenario	Before	After
Dev server down, build broken, router wedged	~40 min of red across all 400+ tests	<2 min, suite aborts after smoke
Healthy infrastructure	smoke + 404 tests	smoke + 404 tests (negligible overhead)

Test plan

• npx tsc --noEmit playwright.config.ts e2e/smoke.spec.ts — clean
• npx playwright test --list --project=smoke — 1 test
• npx playwright test --list --project=chromium — 404 tests (smoke excluded; was 405 before testIgnore)
• CI run: confirm smoke runs first, chromium/ci wait on it
• Negative validation: temporarily break baseURL, confirm chromium/ci are skipped (do NOT merge with this in place)

🤖 Generated with Claude Code