Skip to content

/* transparent-at-rest depends on JS toggling data-nav-scrolled (nav-ui.ts); without scripts the frosted readability state must be permanent, or body text scrolls beneath a fully transparent fixed nav. Not on `bare` (the home hero): shared.css keeps the nav transparent at rest specifically because painting it opaque "clipped the stars into a hard-edged black band across the top", and that page is a single immersive screen with nothing scrolling under the nav to be unreadable. So the one page where this override costs the most is the one page it buys nothing on. */ nav[data-type="hero-nav"] { background-color: var(--color-bg-blur); -webkit-backdrop-filter: blur(12px); backdrop-filter: blur(12px); }

learnings

Things I found worth understanding properly, written up with the simulation running in the page. Read the story, then poke at the thing itself.

Aug 20, 2026
One agent wrote the article, the code and the test. All three were wrong the same way.
A green gate said the implementation matched its test. Both matched the prose. All three had inherited the same misremembered fraction, and the tool taught the wrong number to anyone who used it.