test-rendered-landing: 12 s Chrome startup window flakes on CI #112

test/test-rendered-landing.js polls Chrome's debugging port 80 times, 150 ms apart (about 12 s), then fails with Chrome did not expose a debugging port within 12s.

During #109 this failed in 3 of about 40 jobs across 10 CI runs, all on GitHub-hosted ubuntu runners, in both the test job and the mutation job's baseline. Reruns passed. When the mutation job's baseline hits it, the whole mutation run aborts.

Options: a longer window (for example 30 s), one relaunch on a fresh port before failing, or reading the DevTools listening on ws://… line from Chrome's stderr instead of polling. The port choice, 9400 + pid % 500, could also collide on a shared runner.

🤖 Generated with Claude Code