[Issue Arborist] Issue Arborist Report

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 70

Parent issues created

None this run — no orphan cluster reached the required 5+ clearly-related issues without an existing parent.

Links created

Parent	Sub-issue	Reasoning
#1549	#2156	[aw] Failed jobs: Docs Writer matches #1549's theme of recurring non-rate-limit agentic workflow execution failures
#1549	#2155	[aw] Issue Triage produced no safe outputs — same recurring-failure pattern already tracked under #1549
#1549	#2153	[aw] Issue Triage failed (engine terminated unexpectedly) — same recurring-failure pattern already tracked under #1549

Suggested (not linked — for maintainer review)

• chore(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156, chore(workflows): recompile safe-output fixtures with ado-aw v0.37.0 #1041, chore(workflows): recompile safe-output fixtures with ado-aw v0.36.0 #1027 — three chore(workflows): recompile safe-output fixtures with ado-aw vX.Y.Z issues share an identical recurring-maintenance theme, but there are only 3 (below the 5+ threshold for a new parent). Worth a lightweight parent if more of this pattern appears, or manual closure if superseded by newer fixture versions.
• [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 and [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 — both propose ways to make Azure DevOps pipeline configuration (model selection, arbitrary pipeline variables) resolvable outside compile-time source edits. They read as siblings of the same underlying need (runtime-configurable pipeline settings) but neither is clearly broader than the other, so no parent/child link was made.
• Allow config overrides e.g. npmrc for built ins #253 (Allow config overrides e.g. npmrc for built ins) could plausibly belong under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 ([Parent] Compiler internals and pipeline generation improvements), but the relationship (runtime tool config vs. compiler/IR/YAML generation) felt too loose to link with confidence.
• Feature request: first-class TLA+ / TLC (Java) runtime support #1222 (TLA+/TLC runtime support) and feat: allow enable to target individual pipeline files #1634 (enable targeting individual pipeline files) remain standalone feature requests with no clear existing parent or 5+ sibling cluster.
• docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763 (docs: repo-relative paths in prompts) is a lone docs-drift issue; the other open docs issues (docs: fix AGENTS.md accuracy — add trigger-e2e to ado-script tree and export-fact-catalog to CLI index #1583, docs(site): refresh IR typed-helper docs to builder-struct API #1192, docs: conclusion job token reference omits SC_WRITE_TOKEN #1766) are already linked under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, but docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763's fix is narrower (prompt files) and wasn't confidently placeable there.

Observations

• The backlog is already well-organized: 8 active [Parent] umbrella issues ([Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 compiler internals, [Parent] MCPG infrastructure and safe-output tooling improvements #1321 MCPG/safe-outputs, [Parent] Safe-output executor E2E test coverage and tool correctness #1428 executor E2E, [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 non-rate-limit failures, [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535 rate-limit failures, [Parent] Track agent runtime and execution pipeline improvements #1649 agent runtime, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 dependency release notes, [Parent] Track self-optimization design follow-ups (extracted from #1061) #2076 self-optimization follow-ups) already absorb the majority of open issues.
• Only 3 truly orphaned [aw] automated-failure issues ([aw] Failed jobs: Docs Writer #2156, [aw] Issue Triage produced no safe outputs #2155, [aw] Issue Triage failed #2153) were found this run and have been linked to [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549.
• Remaining orphans (~11) are mostly one-off feature requests or narrowly-scoped chores without 5+ siblings, so no new parents were warranted per the conservative linking policy.

Generated by Issue Arborist · auto · 63.3 AIC · ⌖ 1.88 AIC · ⊞ 9.1K · ◷

• expires on Sep 20, 2026, 8:35 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2165.