Browser Review + Proof Page

Announce:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
browser-review-report started.
Target, account and Chrome first — then the reviewers.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

What this skill produces

1. Reviewer reports — one per agent: PASS / FAIL / PARTIAL per checkpoint, observed vs expected, screenshot file names, defects with severity and repro, console errors, cleanup/restore confirmation.
2. A proof page (review.html, published as an Artifact) — one block per change with Vorher / Jetzt / Review auf Stage and the screenshots that prove it, a fact strip (release tag, commit, test counts), a findings list with severity chips, and an operator to-do block. Screenshots are embedded as data URIs (resized to 1200 px JPEG), so the page is self-contained and stays under the 16 MB artifact limit.
3. A follow-up loop — defects go into a fix PR; the page is republished to the same URL with the new state; comments on the page are read and answered.

Reference run: NovaKnows „Matthias-Runde 2" (12.09.2026) — six changes, two reviewers, 39 screenshots, six defects found and shipped the same day. The content file of that run is in examples/novaknows-runde-2.json.