archilyzer

commit 0f46d7aac65f84d1a3127190285fefd673fa4665
parent ae7d11a0d586311cfacf225656cd4f45863bb39f
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date:   Fri, 25 Sep 2026 22:19:50 -0400

common: accentHex's comment — the published hex is the icon's lit line for a named accent only (brand S1 review)

A custom hex is published as stored, but its icon is lit with the dark-fitted
resolveAccent().dark.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Diffstat:
M
common/lib/accent.ts
 | 
8
+++++---

1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/common/lib/accent.ts b/common/lib/accent.ts
@@ -99,9 +99,11 @@ export function resolveAccent(input: unknown): ResolvedAccent {
 }
 
 // The PUBLISHED accent: always a hex. An id becomes its on-dark value (the
-// family's hub and homepage are dark, and the value is also the lit line of the
-// site's icon); a custom hex is published as stored. Absent or malformed →
-// undefined, so a publisher omits the key exactly as before.
+// family's hub and homepage are dark, and for a NAMED accent that value is also
+// the lit line of the site's icon); a custom hex is published as stored — its
+// icon is lit with the dark-fitted resolveAccent().dark instead, which can
+// differ. Absent or malformed → undefined, so a publisher omits the key exactly
+// as before.
 export function accentHex(input: unknown): string | undefined {
   const setting = parseAccentSetting(input);
   if (!setting) return undefined;