[Issue Arborist] Issue Arborist Run Summary

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 62 (last 100 open issues not already sub-issues)

Parent issues created

None this run — no orphan cluster of 5+ unrelated issues met the confidence bar for a new parent.

Links created

Parent	Sub-issue	Reasoning
#1549	#2134	[aw] Issue Triage failed — a recurring non-rate-limit [aw] execution failure (engine terminated unexpectedly), matching #1549's exact theme and existing sub-issue pattern (e.g. #1544, #1523).
#1549	#2121	[aw] Agent Documentation Maintainer produced no safe outputs — another non-rate-limit [aw] execution failure report, same theme as #1549 (cf. #1435 "produced no safe outputs").

Suggested (not linked — for maintainer review)

• Hoist deterministic repeated agent work into workflow steps #2067, Add strict validation for untrusted raw step fragments #2068, Add preview-only self-optimization safe output #2069, Ground optimization proposals in recorded telemetry #2070, Preserve comments when updating workflow front matter #2071 are already sub-issues of [Parent] Track self-optimization design follow-ups (extracted from #1061) #2076 ("self-optimization design follow-ups") — no action needed, noted for completeness.
• [deps-release-notes] awf — upstream release action items #2028, [deps-release-notes] mcpg — upstream release action items #2040, [deps-release-notes] copilot-cli — upstream release action items #2041 ([deps-release-notes] items for awf/mcpg/copilot-cli) look like natural candidates for [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 ("Track and act on upstream dependency release-note action items"), but I could not confirm via the pre-fetched file body whether they're still open/unlinked without an extra read, and [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283's tracked list is already large (28+ sub-issues) with older items explicitly deferred — left for maintainer judgment rather than auto-linking.
• refactor(engine): emit typed install steps instead of YAML strings #1834 (typed install steps) and refactor(compile): unify AzureCLI@2 token-mint steps behind a shared typed helper #1378 (unify AzureCLI@2 token-mint helper) are both compiler-internals refactors in the same spirit as [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 ("Compiler internals and pipeline generation improvements"), but [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286's existing scope (IR types, YAML gen, prompt decoupling) is narrower than these two general refactors — plausible but not unambiguous, so left unlinked.
• [aw] No-Op Runs #13 ([aw] No-Op Runs) and [aw] Detection Runs #793 ([aw] Detection Runs) are long-running tracking issues (not genuine sub-issues of anything) — no action, listed for awareness only.

Observations

• The backlog already has good parent/tracker coverage: six active [Parent] umbrella issues ([Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, [Parent] MCPG infrastructure and safe-output tooling improvements #1321, [Parent] Safe-output executor E2E test coverage and tool correctness #1428, [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535, [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549, [Parent] Track agent runtime and execution pipeline improvements #1649, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, [Parent] Track self-optimization design follow-ups (extracted from #1061) #2076) capture most thematic clusters (compiler internals, MCPG/safe-outputs, dependency releases, rate-limit failures, execution failures, agent-runtime work, self-optimization follow-ups).
• Remaining "loose" issues in the fetched set are mostly one-off bugs/feature requests (feat: allow enable to target individual pipeline files #1634, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763, test(smoke): report scheduled smoke failures as GitHub issues from the orchestrator #1796, chore(security): minimize AWF agent environment and mask unused gh CLI #1818, fix(smoke): route multi-repo Cargo through the internal feed #1823, [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012, [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035, [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [agent-issue]: Allow model-selected reviewers in create-pull-request #2090, Allow config overrides e.g. npmrc for built ins #253, chore(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156, 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, Feature request: first-class TLA+ / TLC (Java) runtime support #1222) that don't share enough overlap with each other (5+) to justify a new parent this run.
• No new 5+-issue orphan cluster was identified this run; the two links above close the gap for the newest execution-failure reports.

Generated by Issue Arborist · auto · 102.6 AIC · ⌖ 1.82 AIC · ⊞ 9.1K · ◷

• expires on Sep 16, 2026, 8:37 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2138.