Visual baselines are large binary test artifacts; keep them out of the repo.
They stay on disk locally (regenerate with `pnpm test:visual:update`); the
infra fixes that make rendering deterministic remain committed. Also folds in
the state_hub_task_id writeback from `make fix-consistency`.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Regenerate the four whynot-control visual baselines against the T06 token
regen, and make the harness render deterministically:
- serve.json (cleanUrls:false): serve was 301-redirecting /…/index.html and
stripping the trailing slash, shifting the document base so every relative
asset 404'd (also broke `pnpm showcase` in a browser).
- examples/whynot-control/index.html: token stylesheet pointed at a
non-existent root path; repoint to ../../src/styles/colors_and_type.css so
the page actually loads the T06 tokens.
- examples/vendor/lit.js: vendor a self-contained esbuild lit bundle and point
the showcase importmap at it, removing the multi-hop live esm.sh dependency.
- tests/visual/ui-kit.spec.mjs: abort the unused Google-Fonts CDN (fonts are
system-ui post-IBM-Plex); a hung font request blocked module execution.
The showcase "every component" test is marked test.fixme: that page wedges the
renderer main thread (a demo composition loops) and has never produced a
baseline. Tracked as WHYNOT-WP-0002-T11. Components + vendored lit render fine
in isolation; the four control baselines pass deterministically.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
