fix(copy): honest pre-query trust badge (PT-06)

[BigSimmo]

Summary

Audit PT-06: the Answer and Documents mode homes asserted "Source backed" before any question was asked, overstating a corpus whose per-document validation status varies (unverified / review-due documents exist and are labelled on results). The pre-query badges now describe the mechanism — "Searches indexed clinical sources" — instead of asserting verification.

Per-answer "Source-backed" labels that reflect an actual grounding verdict are unchanged. The audit's PT-04 composer-warning size tweak was superseded by #576's deliberate single compact site-wide notice and is intentionally not re-applied.

Verification

Focused vitest (privacy-ui), check:type-scale, full typecheck, lint, prettier green. No test pins referenced the old badge copy.

🤖 Generated with Claude Code

[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

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

Next review available in: 9 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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 16d83969-219a-43c6-8df8-8dd13e048544

📥 Commits

Reviewing files that changed from the base of the PR and between e4ff21c and 46574ca.

📒 Files selected for processing (2)

• src/components/clinical-dashboard/answer-status.tsx
• src/components/clinical-dashboard/document-search-results.tsx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/pt-audit-pr4-trust-copy

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/pt-audit-pr4-trust-copy

---

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