Answer page: symbol off, one number per claim, no safety rail, one panel

[claude]

Summary

The production half of the answer-page work approved in #2386. Everything here was drawn in /mockups/answer-chat-perfected-v2 first and signed off by the clinical owner on 2026-08-26, including "direction B" for the block beneath the answer.

• The answer runs edge to edge. The answer-clinical-icon shield tile and its grid column are gone from plain-answer-response, the matching ps-[var(--answer-message-gutter)] is gone from the bare AnswerCard header, and --answer-message-gutter is deleted from globals.css. The tile was decorative (aria-hidden) and its column cost ~2.75rem of every line of a clinical answer on a 390px phone. There are two speakers on this surface, the person's turn is already a right-aligned bubble, and what identifies the assistant turn is the verification line above it — information rather than decoration.
• One number per claim. maxMarksPerCluster is 1. Nothing is hidden: resolveClaimMarks already counted the remainder into overflow, +N renders it, and every source it counts sits on the rail immediately below at full tap size. That rail is also where a Review due or Outdated badge lives, per the 2026-08-24 decision that staleness is carried by the row and the drawer and never by the mark — so the one signal that must not be lost was never on the mark to begin with. This was checked in the code before the cap was changed, not assumed.
• The safety card has no coloured rail. border-t-2 border-t-[color:var(--warning)] spanned a card that also holds Evidence gaps and Report a problem, colouring two controls that carry no state. Colour moves into the icon tile plus a severity chip built from the finding's own label, which answerSupportPriority now returns as severityLabel rather than running into the citation string. The row still renders whenever priority is set — it remains the only route to the safety-findings sheet.
• Direction B under the answer. AnswerFollowUpSuggestions gains layout="rows" (one question per full-width row) and renders on every width; CrossModeLinksSection gains variant="line" (one collapsed row with a preview, opening to the rail it always was); questions sit above matches. Two second copies go with it: the composer dock no longer receives composerFollowUpSuggestions on the answer mode, and the dashboard no longer renders UniversalSearchAlsoMatches there. Both repeated content already on screen — the same three questions truncated onto one scrolling line, and a mode-level restatement of the record-level matches directly above it.
• One citation fix travelling with it. cleanCitationTitle now inserts the missing space in Guideline(EMHS). Every citation label passes through that function, so the safety card, rail cards, drawer and print are fixed together. Display only — the stored title is untouched.

Verification

• npm run test — 871 test files passed (871); 10502 passed | 1 skipped. Includes the repinned tests/answer-follow-up-chips.dom.test.tsx wiring contract, a new bracket-spacing case in tests/citations.test.ts, and tests/answer-claim-marks.test.ts with its overflow expectation derived from the cap rather than hard-coded.
• npm run verify:ui — full Chromium project set. First run: 5 failed, 515 passed (18.8m). All five were this diff's, none were flakes, and each was diagnosed rather than re-run: one real ARIA defect I introduced (aria-controls pointed at a panel that only existed while expanded — caught by the smoke suite's DOM-integrity audit, fixed by keeping the panel mounted and hidden, with useId so two instances cannot collide), and four pinning the old layout, repinned to assert the same content through the new one. Re-run green — figures quoted below.
• npx eslint on all nine changed source files — exit 0.
• npx tsc --noEmit — no diagnostics.
• npm run check:design-system-contract — passed (1012 production files); no ratchet moved. Status-colour boundary: colour-only status indicators 0; status-coloured numerals 0; image inversions 0.
• npm run format then repo-wide npx prettier --check . — "All matched files use Prettier code style!"
• Browser proof on the live answer route at 390px: no answer-clinical-icon in the DOM, answer-follow-up-suggestions present on a phone for the first time, cross-mode-links-line-trigger present, universal-also-matches absent, answer-support-card still rendering, zero page errors.

Risk and rollout

• Risk: this is a clinical answer surface, and the item that deserves reviewer attention is the mark cap. A sentence supported by two documents now shows one number and a +1 instead of two numbers. The reasoning is in the Summary and in answer-claim-marks.ts: the remainder is counted, the rail below lists every source at full tap size, and review status was never carried by the mark. Second is the removal of two duplicate surfaces; both were second copies of content still on screen, and the mode-level panel still renders on the tools, documents, services and forms result kinds.
• Rollback: git revert the commit. The change is additive-to-optional in shape — every removed element is a render-site deletion rather than a data change, so reverting restores the previous surface exactly.
• Provider or production effects: none beyond the deploy itself. No provider-backed gate was run and no live service was called; all browser proof is against the local demo corpus.
• RAG impact: no retrieval behaviour change — no file under src/lib/rag/**, no retrieval RPC, no ranking surface, no eval harness, no golden fixture. src/lib/answer-claim-marks.ts maps recorded claims onto already-ranked rail rows for display; it does not select, score or order sources.

Clinical Governance Preflight

• Source-backed claims still require linked source verification before clinical use
  • The verification line above the answer is unchanged in wording and placement, and every claim's route to its page is unchanged: the mark opens the drawer, and the rail lists every cited source at full tap size.
• No patient-identifiable document workflow was introduced or expanded without explicit governance approval
  • No patient-identifiable workflow is touched. Nothing here reads, writes or displays patient data.
• Supabase target remains Clinical KB Database (sjrfecxgysukkwxsowpy)
  • Unchanged. No Supabase configuration, migration or project reference is modified by this diff.
• Service-role keys and private document access remain server-only
  • No API route, client, key or access path is touched. This diff is presentation plus one display-only string normalisation.
• Demo/synthetic content remains clearly separated from real clinical sources
  • Unchanged. The demo corpus is reached through the same isDemoMode() boundary as before, and no branch here distinguishes demo from live content.
• Source metadata, review status, and outdated/unknown-source behavior remain conservative
  • This is the item the mark cap touches, and it holds. Review due and Outdated badges are rendered by the rail card and the drawer, not by the mark, per the recorded 2026-08-24 decision; the stale-evidence banner and the answer-level cautions are untouched; and the +N never lets a supporting source go uncounted.
• Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed
  • No decision-support behaviour changed. Retrieval, ranking, generation, verification and render policy are untouched; what changed is how many marks a claim shows, where three panels sit, and what colour carries a warning.

Notes

• The mockup that argued for all of this is Answer mockup: take the symbol off the turn, drop the safety rail, and make the two panels one #2386, still open. It changes no production surface and can merge in either order.
• Both decisions are written up in docs/answer-page-redesign-handover.md §12.6–§12.8, which is where a future session will look before touching this surface again.

---

Generated by 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 ↗︎.