6 months ago
617bb51The settings navigation was leaning on muted text tokens for section labels and inactive rows, which leaves the left rail too faint against the light settings surface. This keeps the existing layout and interactions intact while switching the settings-only navigation copy to stronger foreground-derived tones. A small markup test now locks that contract down so future token churn does not quietly wash the settings rail out again. Constraint: Keep the fix scoped to settings navigation instead of globally changing muted text tokens across the desktop app Rejected: Retune the global muted token palette | higher blast radius and likely changes unrelated UI copy that already relies on muted contrast Confidence: high Scope-risk: narrow Reversibility: clean Directive: Treat settings nav contrast as a local contract; if desktop token values change again, recheck the left rail before broadening token edits Tested: bun test apps/desktop/test/settings-shell.test.ts; bun run typecheck:desktop; bun test Not-tested: live native desktop visual verification against the Electron window chrome in this headless session
Parent17928b8
