fix(services): centre the referral progress stepper on phone

[BigSimmo]

Summary

• The Search → Shortlist → Compare → Refer dot rail (ServiceReferralProgress on /services) defaulted to justify-start, so on narrow phone viewports it hugged the left edge with empty space trailing on the right — asymmetrical.
• Added justify-center on the row with sm:justify-start to restore the existing left-aligned layout from sm up, so desktop is unchanged and only the phone layout is affected.

Verification

• npm run verify:pr-local — completed in two passes because the first attempt hit BUILD_REFUSED_DEV_SERVER (a local dev server I'd left running for manual QA); stopped it and reran the remaining steps.
  • check:runtime, check:installed-lock-parity, format:changed, lint, typecheck — clean
  • test — 7091 passed, 4 skipped (663 files)
  • build — succeeded
  • check:rag:fixtures — 36 golden cases / 26 suites passed (unrelated to this change; included by the standard PR-local plan)
  • check:medication-interactions, check:medication-lexicon-report — up to date (unrelated to this change; included by the standard PR-local plan)
• npm run verify:ui — not run. This is a single Tailwind class change on one already-tested page (no shared UI foundation touched); manually confirmed at a 390px viewport against npm run ensure that the row now centers on phone and stays left-aligned from sm up.

Risk and rollout

• Risk: Very low — single Tailwind utility class change, cosmetic only, no logic/behavior change.
• Rollback: Revert this commit.
• Provider or production effects: None

Notes

• This branch's prior PR (fix(services): fold service-group browse nav into the filter sheet #2040, the services filter fold-in) merged via squash while this follow-up commit was in progress. Per this repo's merged-branch policy, the branch was restarted from the latest main and this one unmerged commit was replayed on top, then force-pushed (with explicit user confirmation) to replace the branch's stale, already-merged history.

---

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: 7 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: 171b093f-e86a-4981-a2ae-5314d9d7a4e1

📥 Commits

Reviewing files that changed from the base of the PR and between f19cf8f and 3c55da4.

📒 Files selected for processing (2)

• docs/branch-review-records/c9089c1be4eccbe787644d8ceb04bbb8fd0fbd7faf769b235b340a9a2e32befa.record.md
• src/components/services/services-navigator-page.tsx

---

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