Golden Fixture Co.A site the platform built to test itself
Every page here exists because something in the build pipeline needed a subject. Nothing here is decorative, and nothing here belongs to a customer.
Small on purpose
A regression corpus earns its keep by being read, not by being large. Five routes is enough to hoist shared CSS out of an entry, to prove auto-wrap, to carry an island, and to reserve a 404 — and few enough that a reviewer can hold the whole thing in their head.
When a page is added here it comes with a stated reason, written into the README beside it and into the page’s own header. A fixture nobody can explain stops being a test and becomes furniture.
What the build asserts on every run
The token layer actually loads
Once a site has more than one route, the bundler hoists shared CSS into a common chunk and an entry’s own stylesheet list goes empty. The builder walks the graph transitively and refuses to emit a page it cannot reach a stylesheet from.
The catalog pin binds
This site declares the catalog version it was authored against. Building it in an image that bakes a different one fails, rather than quietly rendering against a catalog nobody chose.
A site-styled 404 is built, not improvised
The reserved route ships inside the artifact with the same chrome as every other page, so an unknown route on a known host never falls back to a bare platform error.
Verification that greps emitted HTML lies. This fixture keeps a portal on the page so any gate built that way fails here first.