feat(css): Blue Harbor semantic-token retune (LC-554 phase 1a) #522
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/LC-554-blue-harbor-tokens"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
LC-UI-01 phase 1a: Blue Harbor semantic-token retune (CSS only)
First slice of the Blue Harbor redesign (epic LC-553 / ticket LC-554). Pure
assets/main.csstoken-value changes - no template edits, no Rust, no Tailwind rebuild.What changed
:root: neutral ramp goes blue-tinted instead of cool slate ---surface#f8fafc -> #f7fbff,--surface-sunken#f1f5f9 -> #edf6ff,--content#0f172a -> #071426,--content-muted#64748b -> #52657a,--content-subtle#94a3b8 -> #8193a8,--border#e2e8f0 -> #d8e6f5,--border-strong#cbd5e1 -> #b9cde3. Accent is unchanged (--accentstill tracks--brand-primary= #2563eb), so operator brand override is preserved.[data-theme=dark]: rebased from slate-900 to Blue Harbor navy - surfaces #071a2f / #0b2542 / #041326, text ramp #eaf4ff / #9fb6d0 / #6f89a5, borders #17395c / #24517c, and--accent-surface#1e3a8a -> #123e73 (keeping the LC-222var(--content)foreground).hc-light/hc-dark: intentionally NOT retinted, with a documented rationale. High contrast is contrast-first and brand-hue-neutral (pure black/white surfaces + borders) and is already blue-accented AAA; tinting it would only reduce contrast.Why it is safe
main.cssis served via its own<link>aftertailwind-built.css, and Tailwind utilities map tovar(--token), so changing token values needs no CSS rebuild.just check/just testoutcomes are identical tomain(which is green).Scope / follow-ups (tracked separately)
--sidebar-*tokens (phase 1b) plus template wiring (LC-560 / LC-UI-07), because the sidebar currently consumes the shared surface tokens..alert*classes = LC-555;.lc-page-*width utilities = LC-562.🤖 Generated with Claude Code
https://claude.ai/code/session_011jXpZXXwpB36MvTr6JrGXN