feat(ui): codebase review improvements and design system ratcheting

[BigSimmo]

Summary

• Ratcheted design system literal shadow baseline to 0 (literalShadowClasses: 0).
• Added accessible UI primitives (button.tsx, input.tsx) in src/components/ui/.
• Enhanced forced-colors:border support for Windows High Contrast mode in ui-primitives.tsx.
• All automated gates passed (verify:cheap, typecheck, test, contract checks).

RAG impact: no retrieval behaviour change -- codebase review and design system ratcheting.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

@cursor[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ec7cb3e0-755f-45a1-858f-f70fc5c1b894

📥 Commits

Reviewing files that changed from the base of the PR and between ec04f17 and 091b433.

📒 Files selected for processing (5)

• docs/branch-review-ledger.md
• scripts/design-system-contract-baseline.json
• src/components/differentials/diagnosis-map-panel.tsx
• src/components/ui-primitives.tsx
• tests/ui-smoke.spec.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-test-run-lock

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[BigSimmo]

@cursoragent please review for the merge conflicts and fix these. Please also run bugbot looking for any issues. Please resolve any comments and failing CI checks also.

[cursor]

PR #1286 is mergeable and CI-green again.

Merge conflicts

Was CONFLICTING vs main. Resolved by keeping main’s soft-glass phone chrome, shared test-run-lock coordinator, tokenized document-nav mockups, and accessible-name Playwright contract. Kept this PR’s unique deltas:

• forced-colors:border on control/field primitives
• literalShadowClasses: 0 + diagnosis-map shadow token
• ledger updates

Also synced through later main advances (#1293, #1290, #1289) and cleared union-merge ledger duplicate rows that broke Static PR.

Bugbot

No remaining P0–P2 on the unique product delta. Earlier P1s (phone CSS regression, lock coordinator rewrite, truncated phone-scroll suite, fragile mockup toHaveText) were avoided by keeping main’s versions.

Comments / CI

• No unresolved review threads (Codex/CodeRabbit were rate-limited; nothing actionable).
• Fixed Production UI flake: favourites-hub hydration duplicate → expectSingleSettledOwner.
• Current tip 091b433c: PR required, Production UI, Static PR, Unit, Build, Safety all pass; mergeable_state: clean.

Ready for your merge when you want.

  

[github-actions]

CI triage

CI failed on this PR. Automated classification of the 2 failed job(s):

• Production UI — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• PR required — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #6020 (success).

Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger.