[ci-scan-feedback] KPI Tracker

[github-actions]

Tracking quality of [ci-scan] issues since 2026-06-08T13:53:53Z. Updated every tick of ci-scan-feedback.agent.lock.yml. To raise a concern, comment on any [ci-scan] issue; the next tick reads in-scope feedback and either opens a [ci-scan-feedback] PR with prompt edits or pushes to the existing one.

Snapshot - 2026-06-11T04:07:03Z

Activity (last 7d)

artifact	opened	closed (good)	closed (wrong)
Issues	0	0	0

"closed (good)" = closed completed. "closed (wrong)" = closed not_planned/duplicate.

Quality (last 30d)

metric	count	rate
Total closures	0	-
Wrong closures	0	n/a (0<10)
Maintainer rejection comments	0	-
Duplicate KBEs	0	-

Outage signals (analyzed CI)

signal	threshold	24h	7d	status
New-KBE burst	day > 2x trailing 30d median (min 3)	0 / median 0	peak day 0	🟢
Build-break spike	>= 2 in any 24h	0	0	🟢
KBE re-filed after maintainer close	any in 7d	0	0	🟢
Wrong-closure rate (30d)	>= 30% with closed_30d >= 10	-	n/a (0<10)	🟢

---

Notes for this snapshot: The ci-scan workflow has now completed 11 runs (all noop). Build 1453653 (failed, 2026-06-08T08:49:54Z) has been the latest completed build on main for the entire window; no follow-up build has appeared, so the follow-up gate correctly defers filing on every run. Tally from the latest 2 runs: run #27300393816 (2026-06-10T19:21Z) → | 0 | 0 | 0 | 1 | (skipped: no follow-up build yet, defer to next run); run #27317702940 (2026-06-11T01:29Z) → | 0 | 0 | 0 | 1 | (same). All outage signals are 🟢 by virtue of zero KBE volume. Rubric scorecard has zero rows (nothing to score). No maintainer feedback found (no [ci-scan] issues exist yet). Integrity-filtered: 0.

[Filtered] count: 0

Generated by CI Failure Scanner - Feedback (machinelearning) · ● 3.2M · ◷