Reporting replaced the old Coverage page (2026-08-11). It is read-only, client-aggregated, and every tab reads live tables — there is no reporting warehouse.
Reporting → Scope: repo inventory with check status across the fleet

​
The demo.reset baseline rule

History starts at the org’s latest demo.reset audit row, if one exists. This is how the demo estate gets a clean reporting slate per demo run without deleting audit rows (which is impossible — the log is append-only by trigger).
  • Real customer orgs never have a demo.reset row → their History shows everything.
  • Settings → Audit is deliberately not baselined — the full chain stays visible for every org; that is the compliance view.
  • If someone reports “Reporting History is empty but the audit log has events”, check for a recent demo.reset row before suspecting a bug — that is the intended behaviour on demo orgs.
Reporting → History: violations recorded and resolved, most recent first

​
Support notes

  • Scope’s status reflects the named scope of each check (repo or repo+PR), not a global pass/fail — a red PR check and a green push check on the same repo are both real and not contradictory.
  • API probes to /v1/check that omit repo in the body write no service_checks row, so smoke tests never pollute these numbers.
  • llm_calls rows carry source (github-app, action, full-scan, mcp) — useful to attribute cost spikes to a path.