Fix opaque phone header compositing follow-up

[BigSimmo]

Summary

• Follow up PR Phone chrome: opaque header/footer, hide backdrops, and add paint/scroll tests #1246 by disabling inherited backdrop blur on opaque phone headers.
• Add static and computed-style regression guards.
• Record the confirmed late review finding and fix in the review ledger.

Verification

• Focused Vitest: tests/mobile-chrome-paint-contract.test.ts and tests/mobile-composer-reserve.test.ts (11/11)
• Focused production Chromium: phone chrome paint/scroll test (1/1)
• Prettier, ESLint, git diff --check, and branch-review ledger guard
• Verification not run: full npm run verify:pr-local; the focused production build/browser check covers this narrow CSS/test follow-up and required hosted CI is the merge gate.

Risk and rollout

• Risk: Low; phone-only paint-layer override with explicit regression coverage.
• Rollback: Revert the two follow-up commits.
• Provider or production effects: None until protected-main merge; merge was explicitly requested.

Clinical Governance Preflight

Not applicable: no ingestion, answer generation, retrieval/ranking, source rendering, document access, privacy, environment, or clinical output behavior changes.

Notes

• PR Phone chrome: opaque header/footer, hide backdrops, and add paint/scroll tests #1246 merged before its late unresolved review thread was verified. This PR carries only that confirmed fix and its ledger record.

[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

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

Next review available in: 6 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: d7d122cc-f37e-49b2-b9a1-e6b8d23b4dd7

📥 Commits

Reviewing files that changed from the base of the PR and between 2a96c1e and 0074b6d.

📒 Files selected for processing (4)

• docs/branch-review-ledger.md
• src/app/globals.css
• tests/mobile-chrome-paint-contract.test.ts
• tests/ui-phone-scroll.spec.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/pr1246-header-blur-followup

---

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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f05dd2ecef

ℹ️ 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".