CI green on a loaded shared machine: browser suites (now also glyph-ligatures and feature-fit, through the shared launch helper) in one dedicated shard started first at concurrency 2; timeouts scaled by load ÷ cores (tests/helpers/load.ts, max(1-, 5-min average), capped at 5x, logged) for browser tests, waits, launch/close, the other shards' default and the desktop boot check; one retry for a browser test that timed out while the factor was above 2, listed as 'retried under load' in the CI summary, never for an assertion failure; the six-type App Privacy walk no longer dumps every step (the --debug-dump check walks two types), wait timeouts print per-line times; play-edit-lock checks reads in flight instead of wall time; tests/load-retry.test.ts

tests/console-persist.test.ts

@@ -3,7 +3,7 @@
 // product uses for that profile (cli/shots/browser.ts, kind "visible"): real Google Chrome, else Playwright's full
 // Chromium, headless here so no window appears. Never the headless shell: it does not restore the last session, so the
 // cookie is always lost there. Skips (with the reason) only when neither is installed. Slow (two real Chrome launches
-// and graceful closes per store), so tools/ci-plan.ts lists it as HEAVY: a shard of its own.
+// and graceful closes per store), so tools/ci-plan.ts lists it as HEAVY (the dedicated browser shard).
 import { afterAll, beforeAll, describe, expect, test } from 'bun:test';
 import { mkdtempSync, rmSync } from 'node:fs';
 import { tmpdir } from 'node:os';