Simplify Differentials compare-queue hero card

[BigSimmo]

Summary

• Removed the small uppercase "Compare queue" eyebrow label and the helper sentence ("Review your shortlist, then open a side-by-side workspace to distinguish the diagnoses.") from the top hero card on /differentials/compare, since that copy duplicated messaging already shown in the "Your shortlist is ready" section lower on the page.
• Replaced the pill-shaped "Search: <query>" chip with a compact inline row (icon + query text) directly under the "N diagnoses selected" heading, dropping the "Search:" label prefix and background pill styling.
• Changed the icon/heading layout from a stacked, top-aligned block to a single vertically-centered row so the now-shorter text sits alongside the icon instead of below it.

Only src/components/differentials/differential-compare-queue-page.tsx was touched, and only the hero section of the non-empty compare-queue state — the "Selected diagnoses" list and the "Your shortlist is ready" / action-buttons section are unchanged.

Verification

• npm run test:focused -- --files src/components/differentials/differential-compare-queue-page.tsx — 1 file, 3 tests passed.
• UI verification not run via npm run verify:ui: this is a narrow, page-owned presentational change (not a shared UI foundation like MasterSearchHeader/GlobalSearchShell), so per docs/process-hardening.md it doesn't require the full Chromium journey gate. Instead verified manually with Playwright against the local dev server (npm run ensure) at:
  • phone viewport (393×852) with 2 diagnoses + a search query
  • phone viewport with 2 diagnoses and no search query (no dangling gap)
  • phone viewport with 1 diagnosis (singular "1 diagnosis selected" copy)
  • desktop viewport (1280×800) with 2 diagnoses + a search query
    All four render correctly with no leftover small text.
• npm run verify:release — not run; not a release/handoff request.

Risk and rollout

Not applicable — pure presentational/copy change to one page-local component, no clinical, data, API, auth/privacy, workflow, dependency, build, or deployment behavior touched.

Notes

• Requested by the user from phone screenshots of the Compare Queue page, scoped explicitly to "this top part."

---

Generated by Claude Code

[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

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 99 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

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: cfcaaec5-4aea-4407-90ca-018a15ed24e6

📥 Commits

Reviewing files that changed from the base of the PR and between 9904fbd and e9d8d26.

📒 Files selected for processing (2)

• docs/branch-review-records/fd90b933e6bf2bd4a3be809c74e1aec9dd9be5fe870e28f21aba6f624f621ca2.record.md
• src/components/differentials/differential-compare-queue-page.tsx

---

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

[github-actions]

CI triage

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

• Lighthouse budget — 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 #11840 (cancelled).

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