[Auto-Triage] Auto-Triage Report — 2026-03-23

[github-actions[bot]]

🏷️ Auto-Triage Report Summary

Report Period: 2026-03-23T18:30 UTC
Trigger: Scheduled run (every 6 hours)
Issues Scanned: 50 recent open issues
Labels Applied: 0 (all visible issues already labeled)
Unlabeled Visible: 0

---

Key Metrics

• Success Rate: 100% — all visible issues are already labeled
• Integrity-Filtered Issues: Issues below approved integrity threshold were not accessible and could not be triaged
• Most Common Label Clusters: automation+cookie, ai-generated+plan, agentic-workflows, documentation+report

---

Classification Summary

All 50 recently updated open issues examined in this scheduled run already carry at least one label. No new labeling actions were required.

View Label Distribution (sampled recent issues)

Label	Approx. Count	Examples
automation	15+	Performance regressions, smoke tests, CI reports
agentic-workflows	5+	Workflow failure reports
documentation	4+	Daily status reports
ai-generated + plan	6+	Static analysis action plans
refactoring + cookie	4+	Shared-component extraction tasks
maintenance	3+	Step-naming alignment, sync issues
safe-outputs + conformance	3+	Conformance check failures
testing	2+	Smoke test reports
performance	3+	Benchmark regression reports

---

⚠️ Integrity Filtering Limitation

The integrity policy (min-integrity: approved) filtered out issues below the approved threshold. These may include recently-opened community issues without approved status. The auto-triage workflow cannot label issues it cannot read.

To allow triage of all open issues, lower the minimum integrity level in the workflow frontmatter:

tools:
  github:
    min-integrity: unapproved  # allows newly-opened community issues

Or use the search_issues tool with min-integrity: none to find truly unlabeled issues regardless of approval status.

---

Recommendations

1. Lower min-integrity in the auto-triage-issues workflow to unapproved so newly-opened community issues can be triaged before they receive approvals
2. Add needs-triage as fallback — any issue the agent can read but cannot classify should receive needs-triage
3. Current label health: All approved/merged-PR-associated issues appear well-labeled

---

References:

• §23453639660

AI generated by Auto-Triage Issues · history

• expires on Mar 24, 2026, 6:34 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Auto-Triage Issues.

A newer discussion is available at Discussion #22554.