Files
zeekayandHanzo Dev afe1eb5c1b Dark is the default here, and the palette is the design system's
TWO SURFACES BUILT FROM THESE PACKAGES CAME OUT BRIGHT WHITE BY ACCIDENT.

theme.css put the LIGHT palette on :root with dark behind `.dark`, so an app
that imported it and did not put class="dark" on <html> rendered oklch(1 0 0) —
pure white. That is also the inverse of @hanzo/design, whose :root is dark with
`.light` to opt out, so an app pulling in both had its theme decided by which
file happened to win. One convention now, the design system's: :root is dark,
.light opts out. `.dark` is kept so an app already stating it is unaffected, and
.light is ordered after so it can still override.

And the token values had drifted to stock shadcn oklch neutrals: `background`
was oklch(0.145), a washed near-#252525 where the system says true black, and
`card` was lighter still — the grey-box-on-grey look. An app on @hanzo/ui did
not resemble an app on @hanzo/design. The CSS in @hanzo/design is the source of
truth and this module is its TS mirror; a second set of numbers is not a second
opinion, it is drift.

destructiveForeground was independently broken: oklch(0.58 0.22 27) is the same
saturated red as `destructive`, so error text sat unreadable on its own fill.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-04 09:35:46 -07:00
..