rjv-replica-screenshotlisted

# Replica screenshot from real payload Sometimes you fix a UI-visible bug but **can't screenshot the real screen**: the dev build is broken by an unrelated import, the state is impractical to stage, the route is feature-flagged, or the change is backend-only and the page won't render locally. You still want a credible before/after in the PR. The move: render a **faithful HTML replica of the actual component**, populated with the **real server payload strings**, and screenshot that. Done honestly it is real evidence — the exact bytes the component renders, in the component's own layout — not a fabricated mockup. ## When to use - The real UI genuinely won't render locally, AND the change is visible in the UI. - You can obtain the exact strings the component receives (see Step 1). ## When NOT to use - The real page renders → screenshot the real page. A replica is a fallback, never a shortcut. - You'd have to invent any value. If you can't get the real string, don't fake it — report the payload as text instead and say the screen couldn't render. ## The honesty contract (non-negotiable) 1. **Real data only.** Every value in the replica is the exact string the real code path emits — dumped, not typed. If you type a number, it's a mockup, not evidence. 2. **Faithful markup.** Mirror the real component's DOM structure and classes so the replica *looks like the product*, not a generic card. Read the component first. 3. **Label it.** A caption in the image (and a line in