fix(design): /digest speaks the house palette; design-audit finds every page that doesn't #5531
ccantynzAI Reviewcommented 8d ago
AI Triage
(no summary)
Priority: medium Risk area: mixed
Suggested labels: (no label suggestions) Suggested reviewers: (no reviewer suggestions)
Suggestions only — nothing has been applied. The PR author stays in control.
gluecron[bot]🤖 botAI Reviewcommented 8d ago
AI review unavailable
The platform's AI balance is exhausted, so AI generation is temporarily unavailable. Nothing was lost. You can queue this as a repair for the internal agent from the repository's Health page, or try again once the balance is restored. The PR is otherwise unchanged.
Cross-repo impact
See what breaks downstream if this PR merges.
⮌ Merged
This pull request was merged into main.
c comment · e edit title · m merge · a approve · r request changes · ? shortcuts
The /digest fix and the "how do we find all of these" answer
The page: hardcoded indigo/violet insight card (
#f0f4ff→#fdf4ff,#c7d2fe,#3730a3— the banned purple family, dark-mode-blind), an off-palette orange/yellow hero gradient, light-only literal priority colors, and Vercel-blue accent fallbacks. All replaced with the house vocabulary: evergreen--accent/--accent-2,color-mixtints of--red/--amber, token text colors — correct in both themes.The detector:
scripts/design-audit.mjs— every literal color insrc/routes+src/viewsis either the token file, an email template (mail clients can't read CSS variables — exempt), or a violation; hue analysis makes purple/indigo/violet a hard failure (exit 1). Derived coverage applied to design: a page can't quietly speak the wrong language again.First run's map: 185 files with literal colors, 49 banned purple-family literals across ~15 pages — orgs, admin, vs-github, docs, help, inbox, playground, oauth, developer-apps, standups, ai-explain, web.tsx. The proposed follow-up: an agent-run purple sweep to zero, then the audit joins CI as a hard gate so zero stays zero.
Typecheck clean.
🤖 Generated with Claude Code