Route accessible text colors through @policyengine/design-system

[MaxGhenis]

Summary

Drops the inconsistency between policybench's locally-defined accessible text colors and the upstream @policyengine/design-system tokens.

The recent a11y pass had to declare --color-danger-text and --color-success-text locally because the design system only exposed --pe-color-text-warning (no error or success companions). policyengine-app-v2#1024 adds those upstream as --pe-color-text-error and --pe-color-text-success.

This PR switches our theme.css to:

--color-warning-text: var(--pe-color-text-warning, #d9480f);
--color-danger-text:  var(--pe-color-text-error,   #b91c1c);
--color-success-text: var(--pe-color-text-success, #285e61);

So:

• Today: identical render — the fallback hex matches the local value.
• Once design-system v0.5+ is installed: the upstream value takes over automatically and the local hexes drop out. No second PR needed here.

Verification

• bun run lint clean.
• bun run build clean.
• Computed accessible text colors stay at their AA-passing values for badges, intervals, pending notes, etc.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
policybench-site	Error		May 9, 2026 4:21am

[policyengine]

Looks good! This is a clean backward-compatible migration that prepares for the upstream design-system tokens.

Verified:

• All three fallback hex values match their current computed values:
  • --color-warning-text: #d9480f matches --pe-color-text-warning (already exists upstream)
  • --color-danger-text: #b91c1c matches the previous hardcoded value
  • --color-success-text: #285e61 matches --pe-color-primary-700 (uppercase/lowercase hex equivalence)
• The var() syntax with fallbacks is correct and will pick up the upstream tokens once design-system v0.5+ is installed
• No other files reference these color variables directly, so the change is isolated to theme.css
• Comment clearly explains the migration strategy

The approach is sound: renders identically today, and will automatically pick up the upstream values when the design-system package is upgraded. No follow-up PR needed in this repo.