fix(imagegen): share one chromium across test renders to avoid spawn deadlocks

[nibzard]

Summary

The imagegen CI flake was not slow runners: with the timeout raised to 240s (#110), the failing test died at 180s, which is Playwright's own browser launch timeout, with chrome-headless-shell stuck at launching. Repeated chromium.launch() calls in the same Bun test process intermittently deadlock on spawn; cli.test.ts already documents this pattern for subprocess spawns. The first launch always succeeds, so the fix is to launch once and reuse.

• renderCard accepts an optional already-launched browser; the caller owns its lifecycle, and pages are now closed per render either way. Without the option, behavior is unchanged (launch and close per call), so the production CLI path is untouched.
• run() gains a render seam in RunDependencies, mirroring the existing generate seam.
• New tests/imagegen/helpers/browser.ts shares one lazily-launched Chromium across all imagegen test files; Playwright reaps it at process exit.
• Both integration test files render through the shared browser; timeout comments updated.

Side effect: the full test suite drops from about 195s to about 28s, since Chromium launches once instead of per render.

Test plan

• bun test tests/imagegen: 79 pass, 0 fail
• bun test (full): 316 pass, 0 fail
• bun run typecheck and bun run check: clean

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Jul 31, 2026 1:37pm