refactor(mode-home): short titles and single-line hero subtitles

[BigSimmo]

Summary

• Mode-home heroes now read consistently: the title is the mode name and the subtitle is one high-yield line instead of a sentence that wraps to two lines on a phone.
• Titles shortened to the mode noun: Therapy (was "What therapy are you looking for?"), Factsheets (was "Clear information for the next conversation."), Specifiers (was "Refine the diagnosis with the right specifier"), Formulation (was "How can I help with the formulation?"), Services (was "Find a service"), Medication (was "Medication prescribing").
• Titles already short (Tools, Forms, DSM-5 Diagnosis, Favourites, Differentials) keep their name; their subtitles are trimmed where still long.
• Subtitles rewritten to a single focused line, e.g. Factsheets → "Plain-language patient handouts to print and share.", Forms → "The complete WA MHA 2014 forms register.", Tools → "Assessment, prescribing, and clinical workflows.". Therapy keeps its dynamic record count but drops the trailing clause.
• Copy-only change to the title/subtitle props passed to ModeHomeHero/ModeHomeTemplate; no component structure or CSS change. UI/DOM specs that asserted the old copy are updated in lockstep.

Verification

• npm run verify:pr-local
• Ran instead: npm run typecheck ✅, npm run lint ✅, full vitest run ✅ (2971 passed; the single failure is tests/pdf-extraction-budget.test.ts, an unrelated Python-OCR child-process timing test that needs the OCR stack — untouched by this change).
• UI verification not run: verify:ui/Playwright could not launch in this environment — the sandbox has Chromium build 1194 installed but the pinned Playwright expects build 1228 (chrome-headless-shell-...-1228), and browser download is disabled. Every failure was browserType.launch: Executable doesn't exist, not an assertion. The affected specs (ui-accessibility, ui-route-coverage, ui-specifiers, ui-formulation, ui-tools) had their hero-heading assertions updated to the new titles and should be run in CI.

Risk and rollout

• Risk: Low — user-facing copy only; no logic, data, API, or provider surface touched.
• Rollback: Revert the commit; strings return to their previous values.
• Provider or production effects: None.

Clinical Governance Preflight

Not applicable — no ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical-output surface is touched. Change is presentational hero copy only.

Notes

• Defaults chosen without live confirmation (the interactive prompt was unavailable): applied to all mode homes for consistency, and targeted a concise single line (~40–55 chars). Happy to tighten to an ultra-short (~35-char) variant on request.

🤖 Generated with Claude Code

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 24 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: 83301c9d-74e0-4d8e-864a-be7eacf736dd

📥 Commits

Reviewing files that changed from the base of the PR and between 9d6e1f7 and f79a262.

📒 Files selected for processing (16)

• src/components/applications-launcher-page.tsx
• src/components/clinical-dashboard/favourites-hub.tsx
• src/components/clinical-dashboard/medication-prescribing-workspace.tsx
• src/components/dsm/dsm-home-page.tsx
• src/components/factsheets/factsheets-home-page.tsx
• src/components/forms/forms-home-page.tsx
• src/components/formulation/formulation-home-page.tsx
• src/components/services/services-home-page.tsx
• src/components/specifiers/specifiers-home-page.tsx
• src/components/therapy-compass/screens/home-screen.tsx
• tests/therapy-compass-data-recovery.dom.test.tsx
• tests/ui-accessibility.spec.ts
• tests/ui-formulation.spec.ts
• tests/ui-route-coverage.spec.ts
• tests/ui-specifiers.spec.ts
• tests/ui-tools.spec.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/factsheet-copy-polish-pkdxz8

---

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

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

[github-actions]

CI triage

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

• Production UI — 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 #3859 (success).

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

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