[Issue Arborist] 🌳 Issue Arborist Report — 9 links created

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 61

Parent issues created

None — no orphan cluster of 5+ unparented related issues met the confidence bar this run.

Links created

Parent	Sub-issue	Reasoning
#1286	#384	#384 ("YAML generation uses manual string building in compile_gate_step_external") is explicitly listed as a tracked area in #1286's compiler-internals table but was not yet linked as a sub-issue.
#1549	#1988	#1988 is a Clippy Fixer failed-jobs auto-report; #1549 is the umbrella for recurring non-rate-limit [aw] workflow execution failures.
#1283	#2040	[deps-release-notes] mcpg action-item issue matches #1283's umbrella scope for upstream dependency release-note action items (mcpg/awf/copilot-cli).
#1283	#2041	[deps-release-notes] copilot-cli action-item issue — same umbrella as above.
#1283	#2028	[deps-release-notes] awf action-item issue — same umbrella as above.
#1321	#254	#254 ("surface MCPG backend failures in pipeline logs") is explicitly named in #1321's MCPG-infrastructure list.
#1428	#1103	#1103 (add-pr-comment inline-suggestion rendering) is explicitly listed under #1428's "Related issues (tracked here)".
#1428	#381	#381 (upload-workitem-attachment file staging) is explicitly listed under #1428's related-issues list.
#1649	#1375	#1375 (reject unwireable cross-job provider-env macros) is explicitly listed in #1649's "Related issues" body.

Suggested (not linked — for maintainer review)

• refactor(engine): emit typed install steps instead of YAML strings #1834 / refactor(mcpg): type container runtime arguments and mounts #1835 (refactor: typed install steps / typed MCPG container args) share a "typed IR / codegen cleanup" theme with [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286's compiler-internals umbrella, but [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286's body doesn't reference them and the fit is looser than the linked items — worth a maintainer look.
• test(executor-e2e): add create-github-issue and set-github-issue-type scenarios #1798 (executor-e2e test scenarios for create-github-issue/set-github-issue-type) is thematically close to [Parent] Safe-output executor E2E test coverage and tool correctness #1428 (safe-output E2E coverage) but not explicitly named in [Parent] Safe-output executor E2E test coverage and tool correctness #1428's body, so left unlinked pending confirmation it's still open scope for that umbrella.
• [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 and [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 (ADO pipeline variable support) look related to each other (declarative pipeline variables vs. engine.model driven by a pipeline variable) but neither is a strict superset of the other, so no parent/child link was made.

Observations

• Several long-lived umbrella issues ([Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, [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 agentic workflow execution failures (non-rate-limit) #1549, [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535, [Parent] Track agent runtime and execution pipeline improvements #1649) already do a good job cataloguing related work in their bodies; many of the links made this run were simply promoting body-mentioned issues into real sub-issue relationships GitHub can track.
• No cluster of 5+ genuinely orphaned issues emerged this run — most unlinked issues are either one-off bugs/refactors or only loosely related to existing umbrellas, so no new parent issues were created (staying conservative per the linking policy).
• The deps-release-notes family ([deps-release-notes] mcpg — upstream release action items #2040, [deps-release-notes] copilot-cli — upstream release action items #2041, [deps-release-notes] awf — upstream release action items #2028) recurs regularly and is well-served by the existing [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 umbrella; future runs should keep checking for new instances of this pattern.

Generated by Issue Arborist · auto · 33.8 AIC · ⌖ 1.9 AIC · ⊞ 9.7K · ◷

• expires on Sep 5, 2026, 8:29 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2055.