fix: SW-wait timeout + automatic dev-server warm-up (0.1.2)

[kevinccbsg]

Summary

Fixes cross-browser flakiness where Firefox/WebKit time out claiming the service worker in headless CI while Chromium passes — surfaced when running a larger suite (it reproduced reliably with ~120 SW-mocked tests). Two root causes, both fixed here.

1. config.timeout was ignored for the SW wait (af1f1b5)

page.waitForFunction(fn, { timeout }) passed the options object in Playwright's arg slot (signature is waitForFunction(pageFunction, arg, options)), so the timeout was silently dropped and the wait fell back to Playwright's 30s default. That cap is too low for Firefox/WebKit to claim the SW in headless CI, so the wait timed out and no tests ran. Moved the timeout into the options slot.

Proven with a standalone Playwright repro:

buggy   form  -> threw after 30006 ms   (ignored the requested 2000ms)
correct form  -> threw after  2003 ms

2. Cold dev server races SW registration (03d8b1a)

A cold Vite dev server compiles the module graph and runs optimizeDeps on first load, forcing a full-page reload that races SW registration. Chromium shrugs it off; Firefox/WebKit lose the race. In a sequential run the first engine accidentally warms the shared server for the rest — which is why serial passed but parallel/cold runs failed.

Now, when waitForServiceWorker is set, the runner does one throwaway Chromium page load first (same readiness gates) so every engine starts against a warm server. It's:

• Automatic — no new config key; tied entirely to waitForServiceWorker.
• Best-effort — a warm-up that can't complete logs a warning and the run continues.
• Resilient — falls back to a configured engine if Chromium isn't installed.

3. Docs (974e566, d95e401)

• Lead with single-job parallel (npx twd-runner run runs engines in parallel inside one runner) as the portable, CI-agnostic pattern; the GitHub matrix is noted only as an optional per-engine-isolation extra.
• Clarify that npm install does not fetch browser binaries (npx playwright install does), that all engines should be installed since the warm-up uses Chromium, and that the composite action installs browsers in CI.
• Bump version to 0.1.2.

Testing

• vitest: 42 passing (added warmUp coverage + corrected the timeout-signature assertion).
• End-to-end on a real Vue example (124 SW-mocked tests): Firefox + WebKit go from total failure → green across 4 consecutive CI runs, single job, both engines in parallel.

Changes

• src/runBrowser.js — waitForReady helper, timeout fix, warmUp()
• src/index.js — warm-up pass before the run when waitForServiceWorker is set
• src/config.js — unchanged (warm-up is internal, no new key)
• tests/ — warmUp + timeout-signature coverage
• README.md, package.json, package-lock.json — docs + 0.1.2

🤖 Generated with Claude Code