Skip to content

fix(theme): salvage dark-mode audit from PR #1190 without clinical regressions#1214

Merged
BigSimmo merged 10 commits into
mainfrom
cursor/pr1190-dark-mode-salvage-f453
Jul 25, 2026
Merged

fix(theme): salvage dark-mode audit from PR #1190 without clinical regressions#1214
BigSimmo merged 10 commits into
mainfrom
cursor/pr1190-dark-mode-salvage-f453

Conversation

@BigSimmo

@BigSimmo BigSimmo commented Jul 25, 2026

Copy link
Copy Markdown
Owner

Summary

PR #1190 (remediate-dark-mode-audit @ 00eca49b) is not merge-safe: conflict resolution dropped the trustGatedAnswerForClinicalNotes fail-closed gate, broke @/lib/rag imports on the answer API, and remains CONFLICTING vs main.

This PR salvages only the intentional dark-mode audit commit (363672602) onto current main:

  • Theme transition / CSS dark-mode tokens + no-hardcoded-hex ESLint rule
  • Theme-aware sidebar/provider/settings colour usage
  • Remove static PWA manifest theme_color / background_color (theme-color stays on viewport/meta)
  • Keep trustGatedAnswerForClinicalNotes intact
  • Drop unused APP_THEME_COLORS / DEFAULT_THEME imports from manifest.ts
  • Update tests/pwa-manifest.test.ts to assert theme colours are not locked in the static manifest

After this lands: close PR #1190 without merging.

Verification

  • tsc --noEmit clean on salvage tip
  • tests/visual-evidence-tabs.dom.test.tsx + tests/ui-overlay-css-contract.test.ts (13/13)
  • tests/pwa-manifest.test.ts (8/8) after contract update
  • eslint on changed files (--max-warnings 0)
  • npm run check:branch-review-ledger
  • Synced with origin/main before merge
  • Verification not run: full verify:pr-local deferred to hosted CI on this tip
  • UI verification not run: no local browser matrix; Production UI covered by hosted CI

Risk and rollout

  • Risk: Low — theme/CSS/lint + mockup colour token cleanup; no answer/retrieval behaviour change
  • Rollback: revert this PR
  • Provider or production effects: None

Clinical Governance Preflight

Not required for this salvage (no ingestion/answer/search/source/privacy/production-env behaviour change). Explicitly preserves the clinical-notes trust gate that #1190 deleted.

Notes

Open in Web Open in Cursor 

BigSimmo added 3 commits July 25, 2026 22:53
Cherry-pick the intentional dark-mode commit from PR #1190 onto current main,
keep trustGatedAnswerForClinicalNotes, drop unused manifest theme imports, and
normalize the no-hardcoded-hex ESLint rule export.
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 56 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: cd5286d1-71ed-4770-80e5-6c83ee950c12

📥 Commits

Reviewing files that changed from the base of the PR and between b2d794c and e194422.

📒 Files selected for processing (12)
  • docs/branch-review-ledger.md
  • eslint-rules/no-hardcoded-hex.mjs
  • eslint.config.mjs
  • playwright.config.ts
  • src/app/globals.css
  • src/app/manifest.ts
  • src/components/clinical-dashboard/ClinicalSidebar.tsx
  • src/components/clinical-dashboard/provider-brand-icons.tsx
  • src/components/clinical-dashboard/settings-dialog.tsx
  • src/components/clinical-dashboard/use-theme.ts
  • src/components/favourites-page-mockups/favourites-library-redesign-page.tsx
  • tests/pwa-manifest.test.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cursor/pr1190-dark-mode-salvage-f453

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

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

@supabase

supabase Bot commented Jul 25, 2026

Copy link
Copy Markdown

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 ↗︎.

@BigSimmo
BigSimmo marked this pull request as ready for review July 25, 2026 15:11
@chatgpt-codex-connector

Copy link
Copy Markdown

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, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

Matches the dark-mode salvage that removed locked theme_color/background_color
from the PWA manifest so light/dark can update at runtime.
@github-actions

Copy link
Copy Markdown
Contributor

CI triage

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

  • Unit coverageneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
  • PR requiredneeds investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.

Compared with main CI run #5459 (success).

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

@BigSimmo
BigSimmo enabled auto-merge (squash) July 25, 2026 15:36
@BigSimmo BigSimmo added the skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR label Jul 25, 2026
@BigSimmo
BigSimmo merged commit bb6b394 into main Jul 25, 2026
19 checks passed
@BigSimmo
BigSimmo deleted the cursor/pr1190-dark-mode-salvage-f453 branch July 25, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-branch-sync Opt out of hosted pr-branch-sync / update-branch on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant