[Epic] Report export & sharing — shareable, printable review artifacts

**Epic · Report export & sharing** — turn a checagem into a shareable, print-ready review artifact, in-product.

# 🎯 Strategic Context

## Why Now?

Today, producing a shareable feedback document for a checagem (report + cross-checking + review) requires **exporting the database and assembling the file by hand**. That work is manual, error-prone, and only the founders/operators can do it. As we onboard institutional hubs and formalize the editorial hand-off (Epic B · Process & operations), reviewers and leads increasingly need a clean, self-contained artifact of a single check — for internal review, for archival, and for sharing feedback with the fact-checker — without exposing internal review material to the public fact-check surface.

This is a distinct workstream from measurement (Epic A), process (Epic B), and scaling/monetization (Epic C): it is **reviewer/editorial tooling for producing report artifacts**.

## Problem Statement

#### For Fact-Checking Teams (reviewers & leads):
There is no in-product way to render a full check — analysis + cross-checking + review comments anchored to the passages they refer to — as a single, printable page. Reviewers reconstruct this by hand from a DB export. Internal review material (cross-checking notes, reviewer comments) has no gated surface, so it can only be shared via ad-hoc exports.

#### For Platform Operators & Institutional Partners:
No standardized, exportable review artifact exists to hand to a partner or archive against a published check.

## Solution Hypothesis

Build the report-artifact surface incrementally, reusing what already exists — the `visualEditor → HTML` serializer (the same output stored in `reviewDataHtml`), the internal reference parser that resolves `sources[].props.textRange`, and the existing RBAC role/permission middleware — starting with a gated, print-friendly single-report view and expanding toward bulk and server-rendered outputs only if demand justifies it.

# 🧩 Child items

- [ ] #2533 — **RPT-1 · Printable report view (reviewer/admin only)** — gated, print-optimized single-report page: header + report + cross-checking + review comments anchored to the exact passage; browser Print → "Save as PDF". _(first deliverable)_

## Candidate future children (not scoped yet)
_These are the v1 out-of-scope items from RPT-1; promote to real issues when prioritized._

- [ ] Batch / bulk export of many reports at once.
- [ ] Server-side PDF rendering (no browser Print dependency).
- [ ] Certificate generation.

# Related
- #2483 — Restrict verification-request access to staff (access-control pattern)
- #2487 — Unit tests for the frontend RBAC core (`permissions.ts`) — the policy layer RPT-1 reuses

Start with child issue #2533, which defines the first deliverable: a reviewer/admin-only printable single-report page. Read the visualEditor → HTML serializer, the reviewDataHtml output, the sources[].props.textRange reference parser, and the RBAC permissions.ts pattern; done means a gated report view containing the specified review material that works with browser Print → Save as PDF.

索引モデルが issue の本文から書いたものです。