feat(brand): phase 2 — the branding pipeline

PLAN.md §7: swapping a logo or recolouring the site is a file copy and a
container restart, never a rebuild. Phase 2 builds the mechanism and the
checks that keep it true.

GET /brand/* resolves every file against the mount first and the baked-in
defaults second, per file, at stable unhashed URLs with an ETag and a five
minute TTL. Nothing goes through Vite, which would fingerprint the names out
of the mount's reach. An X-Brand-Source header says which step answered.

Three decisions were taken with the org lead (recorded as D14-D16 in §7):

D14 — one raster in, every size out. brand-default holds a single logo.png;
the header mark at three pixel ratios, both install icons, the apple-touch
icon, the favicons and a real multi-resolution favicon.ico are derived on
request from whichever logo.png is in force, cached, and limited to an
allowlist of sizes. Shipping fifteen precomputed files would have meant an
operator producing fifteen to change a mark — and getting a new header with
the old favicon.

D15 — brand text is applied at boot. Pages are prerendered, so §7's promise
about the site name, tagline and links could not hold at render time.
npm start now runs scripts/applyBrand.mjs first, rewriting the built HTML
from what it last applied to what the mount says. It rewrites from a record
in dist/.brand-applied.json rather than from the defaults, because the naive
version works exactly once and then silently ignores every later edit. An
empty mount is a no-op; removing a mount restores the stock build byte for
byte. Verified both ways, plus a second rename.

D16 — the header shows the real emblem, replacing phase 1's placeholder
glyph, so the site, the product and the Android launcher icon are one mark.
It is raster art, so theme.css cannot recolour it; replacing logo.png is how
the mark changes.

Two defects found and fixed while proving it:

The mounted theme.css did not win. Astro emits its own stylesheet after the
head markup, so linking the operator's last was not enough and every override
was silently a no-op. tokens.css now lives in @layer tokens and the mounted
file is unlayered, which takes order out of the mechanism entirely.

The documentation was a different site. Starlight builds its own head, so the
docs linked a Starlight default /favicon.svg that does not exist here, carried
no manifest or OG card, and never loaded the brand stylesheet — a mounted
theme recoloured the marketing pages and left the docs stock. A Head override
fixes it; half a rebrand looks like a product bug rather than a missed step.

brand-default/wordmark.svg and og-image.png are generated by
scripts/buildBrandAssets.mjs from the emblem and Cinzel's outlines and are
committed, so CI needs neither the artwork nor a font. Type is converted to
paths, because an SVG in an <img> can see neither the page's @font-face rules
nor fontconfig — the same isolation that broke currentColor in phase 1. Its
glyphs are drawn at the origin and translated: opentype.js emits NaN
coordinates at a non-zero origin for some glyphs, and a path parser stops at
the first malformed command, so the first lockup read "Runic Gate" and looked
like a typo rather than a bug.

scripts/checkBrand.mjs is the mechanism for the two failures that are
otherwise silent: it puts every literal /brand/... URL in the source through
the route's own classifier, so a size that is not on the allowlist fails the
build instead of 404ing in a browser, and it rejects a brand string short
enough that a blind replacement at boot could corrupt a page. Negative-tested
three ways before being trusted. It runs in CI ahead of the type check.

Co-Authored-By: Claude <noreply@anthropic.com>

src/lib/brand.mjs

@@ -2,32 +2,31 @@ import brandDefault from '../../brand-default/brand.json' with { type: 'json' };
 
 /**
  * The single accessor for brand text (§7). Every template reads brand through here and
- * never imports `brand.json` directly, so phase 2 can change WHERE the values come from
- * without touching a single call site.
+ * never imports `brand.json` directly.
  *
  * ---------------------------------------------------------------------------
- * A tension phase 2 has to resolve, recorded here so it is not discovered late
+ * WHAT THIS RETURNS, AND HOW THE MOUNT STILL WINS
  * ---------------------------------------------------------------------------
- * §7 promises that changing the site name, the Discord invite or the contact address is a
- * file edit on the bind mount plus a restart — the same class of change as swapping a
- * logo. But §6 prerenders the pages at build time, and a value read at build time is baked
- * into the HTML, where no mounted file can reach it.
+ * These are the STOCK values, read from `brand-default/brand.json` at build time, and they
+ * are what gets baked into the prerendered HTML. That is correct and complete for a stock
+ * deployment, which is the common case.
  *
- * Assets are fine: they are served by `GET /brand/*` at runtime, which reads the mount per
- * request. Text is not, and phase 2 owns the fix. The options, in the order they are worth
- * trying:
+ * The mount reaches the text afterwards, from outside this module. Phase 1 recorded the
+ * conflict here — §7 promises that renaming the product or changing the Discord invite is
+ * a file edit plus a restart, while §6 prerenders every page, so a build-time value is
+ * baked where no mounted file can reach it. The org lead settled it on 2026-08-20:
+ * `scripts/applyBrand.mjs` rewrites the built HTML at boot, before the server opens a
+ * socket, replacing what was baked with what the mount says. Every page stays prerendered,
+ * the docs are covered by the same pass, and Pagefind still has static HTML to index.
  *
- *   1. A response-time rewrite in the Node adapter's middleware, substituting a small set
- *      of placeholder tokens in the prerendered HTML. Keeps every page static and the
- *      mount authoritative. Costs one pass over the response body.
- *   2. Mark the handful of pages that show brand text as `prerender = false`. Simple, but
- *      it spreads: the footer is on every page, so "the handful" is all of them.
- *   3. Accept that text is build-time and only assets are mounted. Cheapest, and it
- *      contradicts the sentence in §7 that says otherwise — so it needs the org lead's
- *      agreement, not a quiet decision here.
+ * Two consequences for anyone adding a field here:
  *
- * Until then this returns the stock values, which is the correct behaviour for an empty
- * mount either way.
+ *   - A new brand string is not automatically rewritable. Add it to `TEXT_FIELDS` in
+ *     `applyBrand.mjs`, or it is build-time only and §7 quietly stops being true for it.
+ *   - The rewrite is a plain string replacement, so a default that is short or that occurs
+ *     in ordinary markup is unsafe. `scripts/checkBrand.mjs` fails the build for one.
+ *
+ * Assets never had this problem: `GET /brand/*` reads the mount per request.
  */
 export const brand = Object.freeze({ ...brandDefault });