The icons and the site catch up with teal - #4
Merged
Conversation
e918536 moved the accent from amber to teal in `web/src/lib/theme.ts`, but stopped there. Two things still wore the old colour. The PWA icon set is generated from that very token and committed, so a clean checkout builds without running the generator — which is exactly why nobody noticed the outputs had gone stale. `pnpm icons` regenerates them; the diff is the accent and nothing else, geometry byte for byte. flue.sh is hand-authored with no build step, so it cannot import the token at all and states it as a literal. That literal was amber in four places: the favicon, `--accent`, the architecture diagram, and the OG generator. All four are on the near-black field, so the swap is direct. Two cleanups while in there. `.cursor` had the hex inline rather than `var(--accent)`, which is how the site grew a fifth copy of a colour it already had a token for. And the focus-visible note named the colour instead of its role, so it read as wrong the moment the colour moved. Both OG cards stay byte-identical, which is the guarantee the two generators exist to keep: a link to the app and a link to the site wear one face. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
e9185366 design(web): the accent calms down from amber to tealmoved the accent inweb/src/lib/theme.tsand stopped there. The favicon, the whole PWA icon set, both OG cards and every colour on flue.sh were still amber.Why they were missed
Two different reasons, worth separating.
The app icons are generated from
chrome.accent— the token that already changed — but the outputs are committed so a clean checkout builds without running the generator. That is the right call for build hygiene and exactly why the staleness was invisible: nothing fails, the file just keeps its old bytes.pnpm iconsregenerates them. The diff is the accent and nothing else; the geometry is byte for byte what it was.The site is hand-authored with no build step, so
site/cannot import the token at all (site/→web/imports are forbidden, andgenerate-og.mjssays so in a comment). It states the colour as a literal, and that literal was amber in four places:favicon.svg,--accentinstyle.css,architecture.svg, andACCENTingenerate-og.mjs. Every one of them sits on the near-black#09090bfield, so the swap to teal-500#00bba7is direct — no contrast question to answer.Two cleanups on the way past
.cursorinstyle.csscarried the hex inline instead ofvar(--accent), three lines below a rule that used the token properly. That is how the site ended up with a fifth copy of a colour it already had one name for. Now points at the token.:focus-visiblecomment read "amber stays inside the terminal figure" — it named the colour rather than its role, so it went stale the instant the colour moved. Now says "the accent".Verification
make test— Go allok, web 601/601 across 40 files, relay 90/90. The web run includesstyles.build.test.ts, the real vite build.pnpm lint(tsc --noEmit) clean.web/public/og.pngandsite/public/og.pngare byte-identical (8e7f1ed3…), which is the guarantee the two generators exist to keep: a link to the app and a link to the site wear one face.icon-512.pngand both OG cards inspected visually.grep -rn fe9a00acrosssite/andweb/returns nothing.🤖 Generated with Claude Code