- Ya
- 19 Agosti 2026, 18:18 UTC
- Mwandishi
- kamo
- Ahadi ya
- ae83077
The rebuild took its chrome from --accent-knowledge, which globals.css declares as #8b5cf6. That variable does not move with an organization's brand, so every customer on the platform got a violet knowledge base whatever their palette was — selection borders, focus rings, the primary button, the pinned shelf, the drop target, the AI mark, the search focus ring, all of it. 73 usages now resolve to var(--color-primary), and the frame's second light to var(--color-secondary). globals.css already said so where it declares the family: accent is scoped to "an icon chip + one hairline" while brand owns "every hover ring, focus outline and divider". Reaching past that scope was the mistake. The tone is renamed accent -> brand, so the next person building on this kit does not reach for the --accent-* family by association. What did NOT change is the semantic set: --commerce-success still means published, warning still means waiting, error still means overdue. Those are meanings shared across the whole product; only chrome belongs to the organization. Two tests hold the line: toneVar('brand') is var(--color-primary), and no tone resolves to anything matching --accent-.