[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-23T04:05:53Z

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 completed 59 runs since the window opened on 2026-06-08T13:53:53Z. No [ci-scan] KBE issues have been filed. The persistent skip reason remains stale build window (>14d) / no follow-up build yet, defer to next run: MachineLearning-CI (definition 167, main) has had no build complete since build #1453653 (failed, 2026-06-08).

Both latest runs concluded with noop:

• Run 59 (2026-06-23T01:20:35Z): stale build window (>14d) and no follow-up build yet, defer to next run — tally: | 0 | 0 | 0 | 0 |
• Run 58 (2026-06-22T19:41:10Z): same — tally: | 0 | 0 | 0 | 0 |

8 [ci-scan-feedback] issues remain open as fallback artifacts from failed PR push attempts (#7627, #7630, #7636, #7637, #7639, #7640, #7641 + this tick). The pending edit (Hard Rule 10 — force early exit on no scannable build) was committed locally to branch ci-scan-feedback/hard-rule-10-early-exit-2026-06-23 but the create_pull_request push to origin failed for the 8th consecutive time; a patch was generated at /tmp/gh-aw/aw-ci-scan-feedback-hard-rule-10-early-exit-2026-06-23.patch. To apply manually: download the agent artifact from this workflow run and follow the git am instructions.

Rubric scorecard: zero rows (no [ci-scan] KBE issues exist to score).

run-id	issue	title-scoped	classification	match-specific	occurrence-honest	log-cross-check	maintainer-feedback
(no rows — zero KBE issues filed since window-start)

[Filtered] count: 2

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

Note

🔒 Integrity filter blocked 3 items

The following items were blocked because they don't meet the GitHub integrity level.

• AccessViolationException when running Microsoft.ML.Scenarios.ScenariosTests.TestRegressionScenario #6960 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [DatabaseLoader] Create higher level convenient methods for DatabaseLoader #4182 list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #7610 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

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