Webapp screenshot setup does not recognize current Playwright Chromium layout

Reported (UTC): 2026-07-16 13:52

What was being attempted: install the headless Chromium required by the webapp-screenshots skill while preparing a GitProjectHealth WUI pull-request screenshot.

What went wrong: setup-chromium.bash failed with 'ERROR: playwright-core install chromium-headless-shell did not produce a headless_shell binary under ~/.cache/ms-playwright'. Playwright had successfully installed build 1228 at ~/.cache/ms-playwright/chromium_headless_shell-1228/chrome-headless-shell-linux64/chrome-headless-shell, but both setup-chromium.bash and screenshot.mjs only search the older chrome-linux/headless_shell path.

Impact: the documented screenshot workflow falsely reports that browser installation failed and blocks required PR screenshots even though a valid browser is present.

Workaround used: create chrome-linux under the installed build and symlink headless_shell to ../chrome-headless-shell-linux64/chrome-headless-shell, then rerun setup-chromium.bash.

Suggested durable fix: update both webapp-screenshots scripts to discover the old chrome-linux/headless_shell path and the current chrome-headless-shell-linux64/chrome-headless-shell path, preferring the newest numeric Playwright build.

Production verification — 2026-07-17

Status: STILL EXISTS. The current ARM64 agent image still has no Chromium/Chrome executable, reports Node 18.20.8, and had to fetch Playwright dynamically via npx, so the browser bootstrap gap remains.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.