docs(sandbox): add neutral theme contrast audit

[rubyycheung]

Summary

• Render the exact light/dark palette stored on the built neutralTheme.
• Label whether the page shows the built theme or pending preview overrides.
• Present palette values as explicit family + mode + tone labels instead of unexplained T50 shorthand.
• Group component previews and contrast results by component family.
• Document WCAG requirements and decorative exceptions.

Source of truth

The page no longer generates a parallel palette. It reads neutralTheme.palettes, so the tonal strips, audit mappings, and shipped theme metadata use the same approved values.

The provenance label says Built neutral theme · no pending overrides when no experiment is applied. Otherwise it reports the pending override count. Hover labels spell out entries such as “Blue, light-mode tone 45” while retaining the numeric API key shown by the palette.

Scope

This PR is sandbox-only beyond inherited stack changes. Palette mappings are in #5628; component-specific contrast treatments are in #5690; ProgressBar structure is in #5645; status-role mappings are in #5667.

Stack

#5627 → #5668 → #5628 → #5690 → this PR → #5667

Verification

Sandbox TypeScript, focused ESLint, formatting, repository checks, and inherited palette/contrast tests pass.

@rubyycheung

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
astryx	Ready	Preview	Aug 30, 2026 9:07am