The site rebuild
Was a draft while it was unshipped. Published 2026-08-17, the day it went live, which is the condition the draft note set for itself. The state moved because the world did, not because the entry was rewritten.
What was wrong before this release: the site carried a set of defects that were individually small, mostly invisible in a screenshot, and collectively the difference between a page that works and a page that looks like it works.
This entry is grouped by what changed rather than by commit, because a changelog assembled from commit messages is noise wearing a structure. Every line below was drawn from the defect ledger the repository already keeps, where each item was recorded at the time with its cause.
It is marked draft on purpose. The build is verified locally and it is not deployed. Deploying is an operator act, and the entry moves to published on the day the version is actually live.
Added
- A dedicated text-safe accent for the two system colours that failed the 4.5:1 contrast floor on the page background, threaded through every surface that renders small coloured text.
- A boundary line on every system, stating what is built and proven against what is still ahead. It renders on the brochure page and the subdomain page, and it is not removable to make a system look finished.
Changed
- The commit figure is published as a floor rather than a point count, after three honest counts of the same repositories diverged as the trees moved.
- The system data module was split by audience. It had been shipping whole to every route at 50,663 minified bytes, of which about 91 per cent never rendered; the slim module is 4,888 bytes and the homepage document fell from roughly 129 KB to 81,962 bytes.
- Eleven tap targets under 24 pixels — footer links, back links, the nav brand — were raised to the floor.
Removed
- Every backdrop-filter declaration and every frosted utility class in the application. Frosting never sits over a live canvas; the last dormant utility was deleted so the rule holds by construction rather than by nobody using it.
- Two names were removed from a system's version ladder. The reason first recorded for removing them — that they appeared nowhere outside the one tree that named them — is itself wrong: they do appear, in a different product's documentation, as explicitly retired rungs. The removal was correct, for the better reason, and the record is corrected here rather than left standing on a premise that does not hold.
Fixed
- The status ticker blackout — see the superseded entry on this page for the full account and for what the later measurement did to it.
- Six one-column cards on mobile were thrashing a single-slot offscreen canvas cache at 1.967 allocations per frame. A size-keyed cache capped at twelve with eviction brought it to zero.
- An icosahedron that drew none of its thirty edges. See the post-mortem on this page.
- A four-second liveness probe aimed at a file that does not exist. See the post-mortem on this page.
- The hero sweep beam travelled a fixed viewport height inside heroes taller than the viewport, leaving 51 per cent of a tall mobile hero unswept. It is now container-sized and covers any height.
- Animation loops started before their visibility observers had reported, and re-armed at the display refresh rate while drawing at 30 frames per second. The loop now starts inside the first observer callback and every callback draws.
- Six form fields on the intake page had labels that neither wrapped their input nor referenced it.
Security
- The development-only script allowance was scoped to development. A production build emits no eval and ships the strict directive unchanged.