Skip to content

a11y | Bump design-system for D12 dark stroke tokens - #83

Merged
BrianGenisio merged 1 commit into
mainfrom
fix/a11y-bump-ds-d12
Aug 13, 2026
Merged

a11y | Bump design-system for D12 dark stroke tokens#83
BrianGenisio merged 1 commit into
mainfrom
fix/a11y-bump-ds-d12

Conversation

@BrianGenisio

Copy link
Copy Markdown
Contributor

Summary

Bumps design-system to learn_bespoke-design-system main at 6ab762a so ChatCPT picks up D12 (dark-adapted --Colors-Stroke-* tokens and the tertiary button border).

Changes

Submodule c8bc4906ab762a (DS #27).

Dropped the app.css override of --Colors-Buttons-Tertiary-Default. The DS dark block now sets Neutral-1100.

The sidebar rest pill still needs a stronger rest color than Stroke-Light (hairline at 0.5 opacity). It now uses Stroke-Stronger in dark, which is the same Neutral-900 as the old hardcoded value.

wave-4-plan.md: D12 → DS PR #27.

Test plan

  • npm test (235 passed)
  • Dark mode: tertiary buttons (Cancel, etc.) have a dark border, not a near-white one
  • Dark mode: sidebar, markdown rules, inputs, and tables use dark hairlines
  • Dark mode: resizer grip is still visible at rest (same as before)
  • Light mode: borders and the rest pill unchanged

Pick up D12 stroke remaps. Drop the tertiary border override; the rest
pill uses Stroke-Stronger in dark so the grip stays visible.

Co-authored-by: Cursor <cursoragent@cursor.com>
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7c2ecbc7-24e5-40fb-9da3-0754a7ca06e0

📥 Commits

Reviewing files that changed from the base of the PR and between 17095e8 and 3a835c5.

📒 Files selected for processing (3)
  • a11y-audits/8-5-26/wave-4-plan.md
  • design-system
  • public/app.css

Comment @coderabbitai help to get the list of available commands.

@BrianGenisio
BrianGenisio merged commit 5fe104d into main Aug 13, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant