Verdict preview

Maintainer review happens through an interactive HTML page: one row per entry with your seeded verdict and reason, a Keep/Drop toggle and a reason field for the maintainer, and a Copy feedback button that exports only changed or commented rows as JSON. Generate the page, wait for the pasted JSON, then apply it. Entry changes land in README.md only after the review — and only on an explicit go.

Generate the preview

1. Build the DATA array. A group is [section, subcategory, rows]; a row is [entry, url, downloads, verdict, reason].
   • subcategory may carry a note after — (rendered muted): use it for proposed splits, re-homes, or anything the maintainer should weigh for the whole group.
   • downloads is PyPI last-month as a comma-formatted string; use — when no signal exists (e.g. agent skill packs), stdlib for standard-library modules, fetch failed when the lookup failed. State the fetch date in the sub-header.
   • verdict is keep or drop, seeded from the current adjudication or dry-run.
   • reason is plain language the maintainer reads cold — no invented shorthand. When fresh evidence contradicts the seeded verdict (a big d…