refactor(viewer): Phase 1 DocumentViewer shell extraction

[BigSimmo]

Summary

• Phase 1 of the PDF/photo viewer redesign: behaviour-preserving extraction of the DocumentViewer shell (~1677 → ~1470 LOC).
• New modules under src/components/document-viewer/:
  • signed-url-request.ts — shared signed-URL GET + rowsById
  • pdf-readers-lazy.tsx — real next/dynamic boundary for canvas/native PDF readers
  • use-document-viewer-route.ts — page/chunk URL sync without remount
  • use-pdf-viewer-preference.ts — canvas vs native localStorage preference
  • use-document-summarize.ts — /api/answer/stream summaryMode controller
• Clarifies document-viewer-lazy.tsx as an RSC compatibility re-export (not code-splitting); PDF split lives in pdf-readers-lazy.tsx.
• Updates lazy/perf contract tests to follow the new ownership.

Verification

• Focused vitest (viewer shell/lazy/perf/frame): 34 passed
• npm run test — 5447 passed | 1 skipped (515 files)
• npm run verify:pr-local -- --files <phase1 paths> — exit 0 (format, docs guards, lint, typecheck, full unit suite, build, client-bundle scan, RAG fixtures)
• Note: one earlier PR-local attempt hit a 30s timeout flake in design-system-adoption hosted-Linux provenance; isolated re-run passed; subsequent full verify:pr-local was green
• UI verification not run: no phone-chrome ownership, composer, or visual behaviour change — extraction only. verify:phone-chrome not required for this phase.
• Release verification not run: not a release handoff

Risk and rollout

• Risk: Clinical document surface refactor (auth-clear, signed URLs, summarize stream moved into hooks). Intended behaviour unchanged.
• Rollback: Revert the branch commit.
• Provider or production effects: None

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 — no CDS behaviour change; shell extraction only. Summarize still posts summaryMode: true to /api/answer/stream with the same abort/auth-epoch semantics.

Notes

• Detail load machine and composer chrome remain in DocumentViewer.tsx for a follow-up extraction if needed.
• Next programme step: Phase 2 unified DocumentFrame / photo chrome (after Phase 0 lands if not already).
• Flightplan evidence: .local/workflow-evidence/2026-08-06T18-02-00-331Z-flightplan.json

[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:33 minutes

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: c7817a85-e4a3-4b89-b20b-77b155b9c0de

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3e626 and 5e3aef4.

📒 Files selected for processing (9)

• src/components/DocumentViewer.tsx
• src/components/document-viewer-lazy.tsx
• src/components/document-viewer/pdf-readers-lazy.tsx
• src/components/document-viewer/signed-url-request.ts
• src/components/document-viewer/use-document-summarize.ts
• src/components/document-viewer/use-document-viewer-route.ts
• src/components/document-viewer/use-pdf-viewer-preference.ts
• tests/document-detail-performance.test.ts
• tests/document-viewer-pdf-reader-lazy.test.ts

---

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

[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 ↗︎.

[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.