Description
README and entry pages repeatedly hard-code metric, log-event, collector, dashboard, and rule counts. These numbers had diverged across the public documentation. Derive or check the summary values from the same sources that generate the detailed artifacts.
Acceptance Criteria
- #1 A deterministic source provides the public metric, log-event, collector, dashboard, alert-rule, and recording-rule counts
- #2 README, docs index, Comparison, FAQ, and navigation summaries cannot drift silently from those sources
- #3 The check fails with an actionable regeneration or edit instruction
Definition of Done
- #1 go build ./… && go vet ./… && go test -race ./…
- #2 golangci-lint run
- #3 scripts/regen-generated.sh (only if a generated artifact’s inputs changed)
Implementation Plan
Derive six public capability counts from catalog and shipped artifacts, add the frozen generated source/checker, then reconcile every owned numeric summary.
Implementation Notes
Generated capability counts and public-summary drift checks are committed in bundled pause snapshot 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522. Current derived values are 293 metrics, 17 log events, 16 collectors, 2 dashboards, 100 alert rules, and 23 recording rules. Resume with exact-head CI.
Final evidence: capability-count checker passed in the integrated GATE; exact-head CI run 33047209645 succeeded. Derived totals remain 293 metrics, 17 log events, 16 collectors, 2 dashboards, 100 alert rules, and 23 recording rules.
Final Summary
Generated capability counts are committed in 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522; parked pending exact-head CI.
Completion: verified by negative tests, full gate, and exact-head CI.