(Formerly tracked under #1936, the beta-stable self-host roadmap — unlinked since this is a marketing/trust surface, not a beta-release blocker. #1936 closed as complete with this as its one deferred item.)
Problem
Only a global homepage aggregate and a private maintainer digest currently surface review-quality signal. There is no public, per-repo review-quality leaderboard/changelog that a maintainer could point to as a trust/marketing signal ("this repo's gate has a 98% precision rate," etc.), unlike some competitor tools that surface this. This is a marketing/trust surface, not an operational gap — lowest priority in this batch, no urgency.
Requirements
- Design and ship a public, per-repo review-quality summary (e.g. gate precision/recall trend, false-positive rate trend, merge-vs-close ratio over time) surfaced on the public site, reusing existing aggregate/telemetry data (
src/review/ops-wire.ts's false-positive tracking, existing public-stats infra) rather than inventing new metrics.
- Must respect the existing public/private boundary — no raw trust scores, reward values, or private scoring surfaces publicly, matching every other public-surface feature's sanitization rules.
- Opt-in per repo (a maintainer may not want quality metrics public), matching the house config-driven pattern.
Deliverables
- A per-repo public review-quality page/section, reusing existing telemetry.
- A
publicQualityMetrics (or equivalent) opt-in setting wired through the config-as-code chain.
Acceptance criteria
- A repo that opts in has a public page/section showing its review-quality trend using only already-public-safe metrics.
- A repo that hasn't opted in shows nothing (no default-on public exposure of a repo's gate performance).
- No private/sensitive data (raw scores, rewards, reputation internals) ever reaches the public surface.
Expected outcome
Maintainers who want to showcase their gate's reliability get a public trust signal to point to, using data this repo already collects — a lower-priority, marketing-oriented capability rather than an operational necessity.
(Formerly tracked under #1936, the beta-stable self-host roadmap — unlinked since this is a marketing/trust surface, not a beta-release blocker. #1936 closed as complete with this as its one deferred item.)
Problem
Only a global homepage aggregate and a private maintainer digest currently surface review-quality signal. There is no public, per-repo review-quality leaderboard/changelog that a maintainer could point to as a trust/marketing signal ("this repo's gate has a 98% precision rate," etc.), unlike some competitor tools that surface this. This is a marketing/trust surface, not an operational gap — lowest priority in this batch, no urgency.
Requirements
src/review/ops-wire.ts's false-positive tracking, existing public-stats infra) rather than inventing new metrics.Deliverables
publicQualityMetrics(or equivalent) opt-in setting wired through the config-as-code chain.Acceptance criteria
Expected outcome
Maintainers who want to showcase their gate's reliability get a public trust signal to point to, using data this repo already collects — a lower-priority, marketing-oriented capability rather than an operational necessity.