[Issue Arborist] Issue Arborist Run Summary

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 72 open, non-sub-issue issues (plus follow-up reads on ~50 individual issues to verify live parent-link status)

Parent issues created

Parent	Theme	Sub-issues	Reasoning
none	—	—	No cluster of 5+ genuinely-unparented issues sharing a clear theme was found. Every large thematic cluster in the dataset (compiler/IR internals, MCPG infra, agent runtime, rate-limit failures, non-rate-limit [aw] ... failed, dependency release-notes) already rolls up to an existing [Parent] issue (#1286, #1321, #1649, #1535, #1549, #1283, master #1284).

Links created

Parent	Sub-issue	Reasoning
#1535	#1950	[aw] Issue Arborist hit AI credits rate limit — exact theme of #1535 ("Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows"); confirmed via live get that #1950 had no parent link despite the cluster's other members already being linked.

Suggested (not linked — for maintainer review)

• chore(workflows): recompile safe-output fixtures with ado-aw v0.36.0 #1027, chore(workflows): recompile safe-output fixtures with ado-aw v0.37.0 #1041, chore(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156 — all "recompile safe-output fixtures" chores, identical theme, but only 3 issues (below the 5+ threshold for a new parent). Worth a manual parent if the theme grows.
• test(audit): add end-to-end integration suites for audit and debug commands #1819 (audit/debug E2E integration test coverage) and test(smoke): report scheduled smoke failures as GitHub issues from the orchestrator #1796 (report scheduled smoke failures as GitHub issues from orchestrator) — both currently unparented test issues, thematically adjacent to [Parent] Safe-output executor E2E test coverage and tool correctness #1428 ("Safe-output executor E2E test coverage") but scoped to different subsystems (audit tooling vs. smoke orchestration vs. executor correctness); not linked since the fit isn't unambiguous.
• feat: allow enable to target individual pipeline files #1634 (enable target for individual pipeline files) — standalone enhancement, no clear cluster partner found.
• [agent-issue]: create-pull-request cannot target a repository from another Azure DevOps organisation #1934 (cross-org create-pull-request targeting) and [agent-issue]: create-work-item hardcodes System.Description, so Bug work items are filed blank #1924 (create-work-item hardcoded description field) — both high-quality [agent-issue]-sourced bug reports with open fix PRs (fix(safe-outputs): reject cross-organization repos in create-pull-request #1935, fix(safe-outputs): make create-work-item body field configurable #1926 respectively); no shared parent theme identified with other open issues, left standalone.

Observations

• The backlog is already well-organized: nearly every issue I sampled across the "rate-limit failures," "non-rate-limit failures," "MCPG infra," "compiler/IR," and "dependency release-notes" themes was already correctly linked to its existing parent issue.
• Only one new, unambiguous link was found this run ([aw] Issue Arborist hit AI credits rate limit #1950 → [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535), reflecting how thoroughly prior Arborist runs have already swept the backlog.
• No genuinely new 5+ orphan cluster emerged; the closest candidates (recompile-fixture chores, test-infra issues) fall short of the threshold or lack an unambiguous common parent, so per the "prefer precision over recall" guidance they were left unlinked and noted above for maintainer judgment.

Generated by Issue Arborist · auto · 101.9 AIC · ⌖ 1.89 AIC · ⊞ 9.7K · ◷

• expires on Aug 26, 2026, 8:38 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1967.