mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-11-09 13:35:12 +09:00
check-frontend-boundaries failed on dev: _ai-assistant.scss carried 11 colour literals against a legacy baseline of 10. The extra one came in with the attachment composer as `var(--warning, <amber literal>)`. `--warning` is not a defined token anywhere in the tree, so that declaration always fell through to the literal -- a hardcoded amber that runtime skins could never recolour, which is precisely what the boundary check exists to catch. (_doctor.scss reaches for the same undefined token with a *different* fallback, so the two rendered slightly different ambers.) $warning resolves to var(--amber, …), the real token. The adjacent line already uses $warning-raw, so the variables are in scope; $warning itself must not be fed to fade() since it expands to a var() rather than a compile-time colour. File back to 10 literals, matching the baseline without moving it. Verified: boundary check, theme-token check, npm run lint and npm run build all pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>