Refine Services filters and referral progress

[BigSimmo]

Summary

• remove the separate service-group browse strip and query-replacing suggestion row on phone and desktop
• move the four overlapping service categories into the shared Filter panel as an OR-within, URL-backed multi-select facet
• replace the minimal referral dots with a compact four-stage pathway directly below the results heading
• preserve the active search when filters are cleared and add responsive regression coverage

Verification

• npm run verify:pr-local

Partial: runtime, installed-lock parity, formatting, docs, ledger guards, lint, and typecheck passed. The full unit phase reported 6,618 passing and 27 skipped tests before stopping on seven failures across three files. The in-scope design-system manifest failure was repaired and now passes; the remaining Windows-only Playwright executable-bit and Claude session-hook failures are in files identical to current origin/main.

• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed

UI verification not run: the full broad UI gate was omitted in favor of focused final-scope coverage. The repository Playwright wrapper passed all four selected Chromium scenarios at phone and desktop widths.

• npm run verify:release before release or handoff confidence claims

Verification not run: this PR is not a release or deployment handoff.

• npm run format
• npm run typecheck
• npm run test -- tests/design-system-adoption.test.ts tests/services-catalog.test.ts — 69/69 passed
• npm run test:e2e -- tests/ui-tools.spec.ts tests/ui-smoke.spec.ts --project=chromium --grep "phone bottom-dock search keeps the command results sheet hidden|services mode shows source-backed records in search results|services results keep category filtering and compact referral progress without suggestion rows|services shortlist exposes comparison only when requested" — 4/4 passed
• npm run build — production build and client bundle secret-surface check passed
• npm run check:rag:fixtures — 36 golden cases / 23 suites passed
• npm run check:medication-interactions
• npm run check:medication-lexicon-report

Risk and rollout

• Risk: Low-to-moderate Services UI behavior change. Existing category predicates and the legacy group URL key are retained; multi-selection now reflects the categories' real overlap.
• Rollback: Revert commit 8d3536b3f.
• Provider or production effects: None.

Clinical Governance Preflight

Not applicable: this is a local Services presentation/filter-state change. It does not alter ingestion, source rendering, clinical claims, document access, privacy, provider configuration, or deployment behavior.

Notes

• Clearing Service category or other facets preserves the active q search parameter.
• Current origin/main is one unrelated mobile safe-area commit ahead; a read-only merge simulation completed without conflicts.

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

Limit details: You’ve used all 1 included review currently available under your plan. You completed 98 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: 3bdd4846-cd19-4130-8f99-c4b305114912

📥 Commits

Reviewing files that changed from the base of the PR and between f80aff0 and a7ead86.

📒 Files selected for processing (9)

• docs/design-system/COMPONENTS.md
• docs/design-system/adoption-manifest.json
• docs/filter-contract.md
• src/components/services/service-group-nav.tsx
• src/components/services/services-navigator-page.tsx
• src/lib/service-core-groups.ts
• tests/services-catalog.test.ts
• tests/ui-smoke.spec.ts
• tests/ui-tools.spec.ts

---

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