Reduce render-blocking CSS without delaying LCP fonts

[BigSimmo]

Summary

• Exclude design-scratch mockup sources from the production Tailwind sheet and load their utility vocabulary only under /mockups.
• Keep Geist Sans preloaded after two hosted Lighthouse runs proved that disabling it delayed text LCP by roughly 2.8–3.7 seconds on root, Forms, and Therapy.
• Preserve live inline themes after client-side navigation from mockups by avoiding persistent !important utilities.
• Supersedes Reduce render-blocking production CSS and font preload #1922 with the valid review and Lighthouse corrections included.

Verification

• npm run verify:pr-local — not run locally; GitHub CI is the requested broad handoff gate.
• npm run verify:ui — not rerun broadly; the focused mockup suite passed 16/16 before the font-only correction, and Reduce render-blocking production CSS and font preload #1922's hosted critical/advisory UI jobs passed.
• npm run test -- tests/css-delivery-contract.test.ts — 2/2 passed on the corrected head.
• npm run format — completed with no additional changes.
• git diff --check — passed.
• Hosted Reduce render-blocking production CSS and font preload #1922 evidence: Build/bundle budget, Static PR checks, Unit coverage, critical UI, advisory/mockup UI, all production UI shards, Semgrep, Gitleaks, and GitGuardian passed. Lighthouse failed twice only with Sans preload disabled; that change is removed here.

Risk and rollout

• Risk: Tailwind utilities used only by mockups are emitted in a route-scoped stylesheet; the contract and client-navigation regression test protect production styling and theme precedence.
• Rollback: Revert this PR to restore the single global Tailwind sheet.
• Provider or production effects: Railway production deployment is authorized after merge; no clinical, data, retrieval, privacy, or Supabase behavior changes.

Clinical Governance Preflight

Not applicable: this changes CSS and font delivery only; clinical/RAG behavior is unchanged.

Notes

• Local production build evidence measured the production stylesheet at 302,113 raw / 46,203 gzip bytes versus the live 367,050 raw / 55,140 gzip bytes.
• Field INP remains unverified because lab Lighthouse does not measure INP.

[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

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:31 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

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

Run ID: d1582958-c611-4343-9cc2-ee9b1e4afa38

📥 Commits

Reviewing files that changed from the base of the PR and between 2d27039 and 0752092.

📒 Files selected for processing (10)

• docs/branch-review-records/2c6a919bc949df279d074bdf810c92f2cb5a090b3bd4b521a833f0baa002e0e3.record.md
• docs/branch-review-records/e9ef965f3b9bffc0aef79a3be4d3c206f04207ac0e1b2d8696bb3f657b7df90a.record.md
• docs/outstanding-issues-inbox/66f364c0-5612-449b-9046-94b4dab0b152.json
• docs/outstanding-issues-inbox/f4b9c833-03f4-40bd-9537-90501c1287c4.json
• src/app/globals.css
• src/app/layout.tsx
• src/app/mockups/layout.tsx
• src/app/mockups/mockups.css
• tests/css-delivery-contract.test.ts
• tests/ui-tools-search-mode-mockup.spec.ts

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:4fe764de43

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[github-actions]

CI triage

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

• Production UI (3) — 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 #10571 (failure).

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