Kit+ replaced the warm brand in brand.html weeks before it replaced anything
else. That gap is where the interesting failure lived.
A spec is not a system
brand.html declared the Kit+ tokens locally and overrode css/styles.css,
which still held Midnight Ink and the warm off-white. So the brand page looked
right and every other page looked wrong, and both were technically correct.
The fix was not to restyle pages. It was to move the tokens into
css/styles.css :root and delete the local override, so there is exactly one
definition again.
The generated files were the real work
js/logo.js is the single source for the mark, and every committed SVG and PNG
is built from it. That is a good rule right up to the moment the source
constants are wrong, at which point it faithfully propagates the wrong colour
into 33 files.
INKandOFFmoved to#0A0A0Band#FFFFFFAMBER_DEEPwas deleted outright, because amber never carries text in Kit+npm run logo,npm run iconsandnpm run socialrebuilt everything
npm run logo:check then passes, which is the only reason we know the SVGs
match the source rather than merely having been regenerated at some point.
One file was lying the whole time
assets/og-image.svg was hand-drawn and never generated. It still showed the
pre-Aperture letterform D sitting in an amber tile, set in Syne, on the share
card every page pointed at. It is deleted. The share card is now a copy of the
generated social card, so there is nothing left to drift.