The afterAll hook of tests/console-fill.test.ts timed out (30 s) in 2 of 3
runs with 10 CPU hogs. Cause: Google Chrome (the fallback when playwright's
Chromium is not downloaded) hangs in its own shutdown after loading http
pages until its 10 s teardown watchdog fires; under load that passed 30 s.
- tests/helpers/browser.ts: one shared launch per file as a browser server
with a 60 s launch timeout, killed at the end (throwaway profile, nothing
to flush); a launch timeout fails instead of silently skipping; contexts
and engine runs tracked per test and closed in afterEach (capped);
event-driven waits for engine log lines
- console-fill: explicit test timeouts, slow tests marked, waits expected
to succeed get a long cap (they return at once), sign-in / watching
navTimeoutMs 1.5 s -> 5 s, persistent-profile Chromium closed in finally,
temp account dirs removed
- site-overflow, console-session: same plumbing (site-overflow's afterAll
had bun's 5 s default)
- console session: launchTimeoutMs option (tests only)
