fix(theme): dark mode goes back to the stock neutral ground and text - #240
Conversation
The brand re-theme (#235) carried the site's cream/olive palette into the dark variant as well as the light one. Cream reads as a deliberate warm surface on white; on a dark ground it reads as a colour cast, and next to the surrounding VS Code chrome the app looked like it belonged to a different product. Dark backgrounds, text, icons and borders return to the values they had before the re-theme (oc-2's neutral ramp) — greys 50-1200, the text and icon steps that ride on them, the legacy surface/text/border overrides, and palette.neutral/ink, which seed everything the overrides do not pin. The pre-paint literal and the terminal's default dark colours follow, so the first frame and the terminal surface match the app again. The brand is untouched: yellow accent (#FFE614) in every accent role, the semantic green/red/warning ramps, the status dots, the yellow selection fill, and the whole light variant stay exactly as merged. Verified by resolving both variants — every neutral background/text/border/icon token is now byte-identical to oc-2, and every remaining difference is an accent- or status-derived token.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 10 included reviews per hour; 8 remain after this review. 📝 WalkthroughWalkthroughThe pull request updates dark-mode colors in the Harmoniqs theme, application preload, and terminal fallback. Light-mode colors remain unchanged. ChangesDark theme palette
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change restores dark-mode backgrounds, text, borders, icons, preload color, and terminal defaults to the stock neutral values while leaving light mode and accents unchanged. No actionable merge-blocking risk remains after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Follow-up to #235.
The brand re-theme carried the site's cream/olive palette into the dark variant as well as the light one. Cream reads as a deliberate warm surface on white; on a dark ground it reads as a colour cast, and next to the surrounding VS Code chrome the app looked like it belonged to a different product. Reported in review as jarring and out of place.
Dark backgrounds, text, icons and borders return to the values they had before the re-theme.
What moved
packages/ui/src/theme/themes/harmoniqs.json(darkonly)surface-*/text-*/border-*/icon-*overrides, andpalette.neutral+palette.inkpackages/app/public/oc-theme-preload.js#0F0F0D→#080808, so the first frame isn't warm eitherpackages/app/src/components/terminal.tsx#191515/#d4d4d4palette.neutralandpalette.inkare the load-bearing pair — they seedgenerateNeutralScale, so they tint every neutral the explicit overrides don't pin. Reverting only the override list would have left the derived tokens warm.Borders and icons came along with "background and text": the borders were cream alphas at 22%, and once the ramp goes neutral they'd have been the last warm thing on screen. Two text colours that the re-theme had neutralised into cream also revert —
syntax-constant, andpalette.info, which drives markdown link text in chat.What is deliberately untouched
#FFE614in every accent rolesurface-interactive-weak)--fg-on-darkindesign-polish.css— that's content on fixed dark scrims (poster art, media overlays) in both schemes, not dark-mode chromeVerification
Both variants resolved through
resolve.tsand diffed againstoc-2:oc-2border-*-selected,surface-brand-*,icon-agent-*) and were confirmed unchanged by this commitcheck:designpasses · ui tests 453 pass / 0 fail · theme-preload tests 4 pass / 0 fail ·packages/uiandpackages/apptypecheck clean.npm run lintreports 1 error inpackages/app/e2e/performance/timeline/session-timeline-benchmark.fixture.ts— pre-existing onlocal/amicode, unrelated to this change.Summary by CodeRabbit