M-clarity-1 — Meridian veteran-facing clarity QA

Branch: feature/m-clarity-1
Do not merge until founder confirms a veteran now understands Meridian.
Next: M-act-1 (A) on feature/m-act-1-a (see M_ACT_1A_MERIDIAN_QA.md).

Does a veteran understand Meridian?

1. Enable / opted-in explainer
2. [ ] What Meridian is (providers matched to VA record)
3. [ ] What rank / “best fit” means (not severity, not provider rating)

4. [ ] Nothing shared until you approve

5. List cards

6. [ ] Provider name first (not “Rank 1” as hero)
7. [ ] Fit label: Best fit / Also a strong fit
8. [ ] Plain need tags + why line
9. [ ] Clear next: “See why this matches”

10. [ ] No “Technical rationale (preview)”

11. Detail

12. [ ] Why this matches you (plain; no med-001 / score= / signal jargon)
13. [ ] Based on your record: human labels only (Medication (sertraline), PHQ-9, PTSD…)
14. [ ] Raw elementId only under “Show record details”
15. [ ] What they would ask for (plain template)
16. [ ] Your control: nothing shared until you say so
17. [ ] Primary CTA named Start coordination (disabled until M-act-1)

18. [ ] One SYNTHETIC PREVIEW banner (not doubled)

19. Still gated

20. [ ] No live share / no real-record matching claim

21. [ ] m1_eligible / Mic gate unchanged

22. Adjacent (same build check)

23. [ ] Splash tagline is coordination copy (not “Own your record…”)
24. [ ] Organization invite card only when a real invite (deep link / plist), not hardcoded WIN