Paul BakausandClaude Opus 4.6 a6a58f712c Fix CI: relative img path in /visual-mode + sandbox flags for Puppeteer ...

Two unrelated breakages were stacking on the v2.0 PR:

1. The static site build crashed because the generated /visual-mode page
   referenced images via root-absolute paths (/antipattern-images/*.png).
   Bun's HTML loader resolves <img src> at build time relative to the
   source HTML file and treats a leading slash as filesystem-absolute, so
   it could not find the images. Use a relative path so Bun bundles and
   hashes them the same way the homepage already does.

2. The Puppeteer-backed fixture tests crashed in GitHub Actions because
   the Ubuntu runners block unprivileged user namespaces, so Chrome's
   sandbox cannot initialize. Pass --no-sandbox / --disable-setuid-sandbox
   only when process.env.CI is set, so local users keep the hardened
   default launch.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-08 13:57:41 -07:00

..

detect-antipatterns-browser.js

Detect side-tab borders built with CSS variables

2026-04-08 11:50:23 -07:00

detect-antipatterns.mjs

Fix CI: relative img path in /visual-mode + sandbox flags for Puppeteer

2026-04-08 13:57:41 -07:00