fix(factsheets): restore composer suggestions and fix phone centering

[BigSimmo]

Summary

Follow-up to #2091 (merged). After that PR landed, the user reported the Factsheets composer still didn't match other mode homes' behaviour. Investigating with a live local build (not just a screenshot) turned up two real, separate gaps neither PR #2091 nor its original scope touched:

• Missing composer suggestions.factsheets was never added to the per-mode searchCommandSurfaceByMode table in src/lib/search-command-surface.ts. UniversalSearchCommandSurface (rendered inside MasterSearchHeader's composer chrome for every mode) early-returns to a bare input with no "✨ TRY THIS" suggestion ticker, no autocomplete suggestions, and no cross-mode chips whenever that lookup resolves to null — every other hero-placement mode (DSM, Services, Forms, Specifiers, Formulation, Tools, Calculators, …) already has an entry; Factsheets silently didn't. Added a factsheets entry (calculators' shape/pattern: local search, remoteSearchEnabled: false) with examples/suggestions drawn from real, currently-indexed factsheets (sertraline, lithium monitoring, CBT) so "Tap to search" resolves real results.
• Broken vertical centering on phone.ModeHomeMain's contentAlign="center" (Factsheets' default, since it has no action/pill content to populate start/startOnPhone layouts with) is meant to vertically centre short, empty-ish mode homes in the visible canvas. On phone this silently never worked: its immediate DOM parent in GlobalSearchShell (mobile-composer-reserve-pad) is a plain block element, not a flex container, so its flex-1/min-h-0 classes have no effect there — the box collapsed to its own content height (measured 393px against an 844px viewport) instead of stretching to fill available space, so justify-center had nothing to centre within and content just pinned to the top. The existing sm:min-h-[calc(100dvh-var(--shell-header-h))] rule already solves the identical problem at sm+ using the same calc; mirrored it for phone, scoped only to the center alignment variant in MODE_HOME_MAIN_ALIGN_CLASS (not start/startOnPhone, which don't rely on container height to look correct, and are what every other mode home already uses).

Both fixes verified live against a local dev server, side-by-side with /dsm (composer stack now structurally identical — ticker, input, privacy notice) and /differentials (the only other page using contentAlign="center"; confirmed unaffected — its richer content already fills the viewport, and no scroll/overflow regression was introduced: scrollHeight === clientHeight before and after on both /factsheets and /differentials).

Verification

• npm run verify:pr-local — not yet re-run against this exact combined diff at PR-open time; will run before merge if requested. Already independently verified: npm run test:focused -- --files src/lib/search-command-surface.ts src/components/mode-home-template.tsx (283 tests passed across 32 files), npm run typecheck (clean), eslint on both changed files (clean), prettier --check on both changed files (clean).
• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed — not run as the full Chromium gate; instead verified directly with live Playwright checks at 390×844 against the local dev server (npm run ensure): confirmed the "TRY THIS" ticker renders and is tappable (fills the search input with "sertraline") on /factsheets, matches /dsm's composer stack pixel-for-pixel structurally, and the phone-centering fix produces a genuinely centered short home with no overflow/scroll regression on /factsheets or /differentials (its own contentAlign="center" no-results state), and no change at all to /dsm (uses startOnPhone, untouched by this diff).
• npm run verify:release before release or handoff confidence claims — not run; this is a PR handoff, not a release.

This PR does not touch retrieval, ranking, selection, chunking, source/citation rendering, or answer-contract behaviour, so eval:retrieval:quality / eval:rag / eval:quality are not applicable.

Risk and rollout

• Risk: Low-moderate. src/lib/search-command-surface.ts is a pure per-mode data-table addition (isolated, additive). src/components/mode-home-template.tsx is a shared layout primitive used by 8+ standalone mode homes, but the change is scoped to the center alignment variant only, which today is used by exactly two pages (factsheets, and differentials' no-results state) — both were checked live for regressions.
• Rollback: Revert this commit; no data, schema, or config changes are involved.
• Provider or production effects: None.

Clinical Governance Preflight

src/lib/search-command-surface.ts matches this repo's clinical-risk path pattern (any src/lib/** file with "search" in it), which is deliberately broad — but the actual change is a per-mode composer-suggestions data-table entry (search terms shown in a "try this" ticker) plus a layout centering fix; neither touches retrieval, ranking, answer generation, ingestion, or source rendering logic.

• Source-backed claims still require linked source verification before clinical use
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
• Service-role keys and private document access remain server-only
• Demo/synthetic content remains clearly separated from real clinical sources
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

• This does not touch src/lib/rag/**, clinical-search, retrieval-selection, ranking-config, answer-ranking, the eval harness, or the golden fixture, so no RAG impact: declaration applies.

---

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.

[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:28 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 101 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: 65b3af36-6739-4b7b-95f8-b9cebce759a9

📥 Commits

Reviewing files that changed from the base of the PR and between b491f0f and 28aa0f2.

📒 Files selected for processing (5)

• docs/branch-review-records/81997d38c381bb8080a941b3ba8e54540b842a4341cf4b38c4b6f6a3b91ce316.record.md
• docs/branch-review-records/c7d5291702bbc1acdbe61d91c20665e02df1aa60d3560900cd46e5c272b72d0a.record.md
• src/components/mode-home-template.tsx
• src/lib/search-command-surface.ts
• tests/mode-home-main-align.test.ts

---

_{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 ↗︎.