Problem
The automation health dashboard surfaces link-health and dep-bump metrics but shows nothing about the clawgenti PR reviewer. There is no executive-facing view of how many PRs the bot reviews or whether reviewed PRs merge faster.
Rationale
The dashboard is a pure consumer of per-program report files. Once the PR-review program emits an impact report (tracked in kagenti/automation#19), the dashboard should read it alongside the existing PR-review queue and throughput data and present it the same way it presents the other programs.
Scope (this repo)
Extend the automation-health-dashboard skill to:
- Detect the PR-review program and count it as active
- Add a PR Review section: cumulative reviews, current queue depth, and median time-to-merge (reviewed vs. unreviewed, and before vs. after each repo's activation), with a recent-activity trend
- Add PR Review to the cross-program coverage table and the cron health table
- Surface per-repo activation dates so the before/after split is transparent
- Degrade gracefully when the impact report is absent
Acceptance
- Dashboard renders a PR Review section and bumps the active-programs count
- Stays read-only (no new GitHub queries in the dashboard itself)
- Documented in SKILL.md
Related: kagenti/automation#19 (impact data producer)
Problem
The automation health dashboard surfaces link-health and dep-bump metrics but shows nothing about the clawgenti PR reviewer. There is no executive-facing view of how many PRs the bot reviews or whether reviewed PRs merge faster.
Rationale
The dashboard is a pure consumer of per-program report files. Once the PR-review program emits an impact report (tracked in kagenti/automation#19), the dashboard should read it alongside the existing PR-review queue and throughput data and present it the same way it presents the other programs.
Scope (this repo)
Extend the automation-health-dashboard skill to:
Acceptance
Related: kagenti/automation#19 (impact data producer)