docs: PDF and photo viewer redesign plan

[BigSimmo]

Summary

• Adds docs/plans/document-viewer-redesign-plan.md: a phased programme to dramatically improve PDF and photo/figure viewer design, approach, functionality, and optimisation.
• Phase 0 closes known debt (#214 passive wheel / INP, #219 error announce, partial #215 image decode).
• Phase 1 extracts the ~1.7k-line DocumentViewer shell without UX rewrite.
• Phase 2 unifies DocumentFrame chrome + lightbox photo path + page↔figure sync.
• Phase 3 adds virtualization, keyboard reading mode, and measured raster optimisations.
• Encodes hard constraints: one composer owner, zero hidden phone reserve, pixel-faithful sources, auth-clear signed URLs, on-demand pdf.js.

Verification

• Flightplan written: .local/workflow-evidence/2026-08-06T17-27-05-553Z-flightplan.json (paths classified ui; behavioural note in plan elevates clinical document surface + privacy for implementation PRs)
• npm run verify:pr-local -- --files docs/plans/document-viewer-redesign-plan.md — exit 0 (docs-only: format:changed, sitemap, docs index/inventory/scripts/links, ledger, outstanding-issues; lint/typecheck/unit/RAG/build skipped as recognised low-risk scope)
• UI verification not run: no UI code in this PR
• Release verification not run: docs-only plan; no product behaviour change

Risk and rollout

• Risk: Documentation only; no runtime change
• Rollback: Revert the plan doc commit
• Provider or production effects: None

Notes

• Next recommended execution: Phase 0 on a dedicated branch before any visual redesign.
• Implementation PRs that touch source rendering / document access must complete Clinical Governance Preflight even though this plan PR does not.

[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:59 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: 64eefaac-7515-4fd2-956b-0003eb03df6b

📥 Commits

Reviewing files that changed from the base of the PR and between 40b449d and 905174d.

📒 Files selected for processing (1)

• docs/plans/document-viewer-redesign-plan.md

---

_{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.