Three fixes found by driving a real page, not by reading the code.
Its autoloader works out where to fetch components from by finding the
<script> whose src *ends with* "webawesome.loader.js". The cache-busting
`?v=` defeated that match, so it fell back to the site root and every
component 404'd - a page that merely looks unstyled, with nothing in the
browser console and only 404s in the server log to say why. Web Awesome now
lives at /chrome/wa-<version>/, which removes the query string and, because
component filenames are stable across releases, also busts caches properly
on an upgrade. There are regression tests for both halves.
The brand ramp pointed at yellow but buttons came out brown: Web Awesome
picks step 50 for a loud fill because that is the darkest point that still
carries white text, and yellow-50 is #b45f04. The services have always used
bright yellow with dark text, so the fill/on pair is now set explicitly
rather than taken from the ramp.
TemplateResponse's old (name, context) signature is gone in Starlette 1.7,
and the error handler was returning its 404 page with an HTTP 200.
Also adds the import map for Preact/hooks/htm to the shell. hooks.module.js
carries a bare "preact" specifier internally, so the map is required rather
than a convenience, and it belongs here once instead of in every service.
strings_json() hands an island its translations with `<` escaped.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>