Till JS 52af8c0cec refactor(theming): migrate who semantic colours to theme tokens ... PlayView used Tailwind palette classes for game-status feedback: bg-emerald-500/10 + text-emerald-300 (won) → bg-success/10 + text-success bg-amber-500/10 + text-amber-300 (lost) → bg-warning/10 + text-warning border-red-500/20 + bg-red-500/10 + text-red-300 (error) → border-error/20 + bg-error/10 + text-error placeholder-white/30 focus:border-purple-400/50 → placeholder:text-muted-foreground/60 focus:border-primary/50 Semantic status now tracks the theme (errors are red in dark, darker red in light, etc.) instead of being fixed hex ramps. The `bg-purple-500` / `bg-purple-500/30` / `hover:bg-purple-600` classes on the user's chat bubble and submit buttons STAY — purple is the who module's primary identity colour (historical-deck accent `#a855f7` is semantically the same hue). Documented in brand-literals.md §who. Also harden two validators against mid-rename states where git ls-files returns paths that aren't on disk yet — both now skip unreadable files instead of crashing the pre-commit hook (caught while migrating who). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-22 17:19:53 +02:00
..
src	refactor(theming): re-apply theme validator suite after parallel rebase	2026-04-22 17:07:48 +02:00
brand-literals.md	refactor(theming): migrate who semantic colours to theme tokens	2026-04-22 17:19:53 +02:00
package.json	fix(shared-tailwind): export CSS under 'style' condition for Vite build	2026-04-16 13:39:01 +02:00