Problem
ToolsView.svelte uses a different token vocabulary than the rest of the app:
- ToolsView:
--color-border, --color-text-muted, with hardcoded fallbacks (#333, #888)
- Rest of app:
--border, --text-muted (defined in app.css)
ToolsView is currently hidden from the sidebar (PR #244 — route kept for future return), so this is latent: the moment it's re-enabled it will look subtly off (wrong border/text colors on non-dark themes where the fallbacks kick in).
Fix
When re-enabling or touching ToolsView:
- Rename
--color-* → app tokens (--border, --text-muted, --bg-*, etc.)
- Remove numeric fallbacks (
#333, #888, #ddd) — tokens always exist; fallbacks mask drift
Could also be done now as a mechanical sweep — file is not user-visible so regression risk is zero.
Source
Full-app UI audit (token vocabulary split).
Problem
ToolsView.svelteuses a different token vocabulary than the rest of the app:--color-border,--color-text-muted, with hardcoded fallbacks (#333,#888)--border,--text-muted(defined inapp.css)ToolsView is currently hidden from the sidebar (PR #244 — route kept for future return), so this is latent: the moment it's re-enabled it will look subtly off (wrong border/text colors on non-dark themes where the fallbacks kick in).
Fix
When re-enabling or touching ToolsView:
--color-*→ app tokens (--border,--text-muted,--bg-*, etc.)#333,#888,#ddd) — tokens always exist; fallbacks mask driftCould also be done now as a mechanical sweep — file is not user-visible so regression risk is zero.
Source
Full-app UI audit (token vocabulary split).