chore: merge design-audit remediation to main

[BigSimmo]

Summary

• Finalizes the 2026-07-17 repository-wide design and accessibility remediation pass against current main, keeping completed interactions, keyboard behavior, and verification controls in place.
• No new clinical data-path writes were introduced; changes are UI/regression fixes with conservative behavior on source fallbacks and unknown content.

Verification

• Verification not run: local npm run verify:ui and broader runtime checks were not executed in this branch handoff context.
• UI verification not run: provider/browser harness not launched in this environment.

Clinical Governance Preflight

• 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

Risk and rollout

• Risk: medium; UI and clinical-UI surfaces changed and could affect user interaction and source visibility behavior, requiring QA focus.
• Rollback: Revert this PR immediately and restore the previous main commit if any user-facing regression or source display regression is reported.

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy due to reaching the limit of concurrent preview branches.
Go to Project Integrations Settings ↗︎ if you wish to update this limit.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 15 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: dd7e9fe4-ab2e-49a4-9d29-0ab473660293

📥 Commits

Reviewing files that changed from the base of the PR and between af5c025 and d350d58.

📒 Files selected for processing (24)

• docs/codebase-index.md
• docs/site-map.md
• playwright.config.ts
• scripts/check-github-action-pins.mjs
• scripts/generate-site-map.ts
• src/app/layout.tsx
• src/app/page.tsx
• src/components/clinical-dashboard/master-search-header.tsx
• src/components/forms/forms-home-page.tsx
• src/components/services/services-navigator-page.tsx
• src/lib/rag-candidate-sources.ts
• src/lib/rag.ts
• supabase/drift-manifest.json
• supabase/migrations/20260714180000_patch_rag_and_corrector_scalability.sql
• supabase/migrations/20260714190000_document_table_facts_trgm_idx.sql
• supabase/migrations/20260717010000_harden_rag_scalability_patch.sql
• supabase/schema.sql
• tests/audit-content-services-regressions.test.ts
• tests/audit-navigation-auth-regressions.test.ts
• tests/site-map.test.ts
• tests/supabase-schema.test.ts
• tests/ui-accessibility.spec.ts
• tests/ui-smoke.spec.ts
• tests/ui-tools.spec.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/design-audit-to-main-lockfix-2

---

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

[github-actions]

CI triage

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

• Production UI — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• Advisory UI — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• Build — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• Static PR checks — needs investigation: inspect the failing step and uploaded diagnostics; rerun only after classifying the cause.
• Unit coverage — 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 #2998 (cancelled).

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