fix(theme): salvage dark-mode audit from PR #1190 without clinical regressions#1214
Conversation
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.
|
Warning Review limit reached
Next review available in: 56 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (12)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Matches the dark-mode salvage that removed locked theme_color/background_color from the PWA manifest so light/dark can update at runtime.
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
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. |
Bot-authored main sync left required CI on action_required; this agent commit re-triggers human-authored checks for PR #1214.
Summary
PR #1190 (
remediate-dark-mode-audit@00eca49b) is not merge-safe: conflict resolution dropped thetrustGatedAnswerForClinicalNotesfail-closed gate, broke@/lib/ragimports on the answer API, and remains CONFLICTING vsmain.This PR salvages only the intentional dark-mode audit commit (
363672602) onto currentmain:no-hardcoded-hexESLint ruletheme_color/background_color(theme-color stays on viewport/meta)trustGatedAnswerForClinicalNotesintactAPP_THEME_COLORS/DEFAULT_THEMEimports frommanifest.tstests/pwa-manifest.test.tsto assert theme colours are not locked in the static manifestAfter this lands: close PR #1190 without merging.
Verification
tsc --noEmitclean on salvage tiptests/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--max-warnings 0)npm run check:branch-review-ledgerorigin/mainbefore mergeverify:pr-localdeferred to hosted CI on this tipRisk and rollout
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
docs/branch-review-ledger.md