[Issue Arborist] Issue Arborist Report — 2026-07-11

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 55

Parent issues created

None — all clusters had existing parent issues.

Links created

Parent	Sub-issues	Theme	Reasoning
#1284 Issue Arborist Group	#1467, #1430, #1388, #1365, #1351	Issue Arborist rate-limit incidents	All are [aw] Issue Arborist hit AI credits rate limit incidents
#1285 Recurring agentic workflow failures	#1441, #1412, #1389, #1373, #1435, #1459, #1414, #1369	Recurring workflow failures (rate limits, no safe outputs, failures)	All are agentic workflow failure incidents matching the parent's scope
#1283 Upstream dependency action items	#1304, #1305, #1253	Upstream release notes (awf, copilot-cli, mcpg)	All are [deps-release-notes] tracking issues for upstream components
#1321 MCPG infrastructure improvements	#945, #254, #1034	MCPG bugs and features	Custom MCP env passthrough bug (#945), surface MCPG failures (#254), docker reference format bug in generated YAML (#1034)
#1286 Compiler internals improvements	#987, #384, #1378, #1081	Compiler refactors and IR enhancements	Agentic pipeline shape refactor (#987), YAML manual string building (#384), unify AzureCLI@2 token-mint steps (#1378), EnvValue::RuntimeExpression IR variant (#1081)

Total links created: 23

Suggested (not linked — for maintainer review)

• [aw]: Follow-up to #1453: create-pull-request MCP-preflight still fails on shallow/detached-HEAD checkouts in the Agent job #1457 + [agent-issue]: fail closed or deepen history when synthetic PR merge-base is unavailable #1451: Both are shallow-checkout / merge-base failures for create-pull-request. Could form a small parent but only 2 issues.
• feat: decouple prompt body from compiled pipeline output (runtime-import approach) #237 (decouple prompt body) and Inject runtime parameter values into the agent prompt via ado-script (sanitization at runtime, not compile time) #432 (inject runtime param values via ado-script): Related to runtime-import and ado-script bundle work; could go under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 if maintainers consider them compiler-internals.
• 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 (recompile safe-output fixtures for v0.36–v0.38): Recurring chore pattern; could benefit from a parent if the pattern continues.
• feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451 (FrontMatter alignment with gh-aw schema): Broad schema alignment effort; worth its own parent if sub-tasks are tracked.

Observations

• The backlog has 6 well-formed parent issues that were missing most of their children — 23 orphaned sub-issues have now been linked.
• The largest orphan cluster was recurring agentic workflow failures (8 issues) all clearly in scope for [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285.
• Rate-limit incidents dominate the agentic-workflows label; the root cause likely warrants investigation at the infra level.
• [aw] Detection Runs #793 ([aw] Detection Runs) and [aw] No-Op Runs #13 ([aw] No-Op Runs) appear to be long-lived tracking issues with no obvious parent — may be intentional operational trackers.

Generated by Issue Arborist · 52.9 AIC · ⌖ 6.16 AIC · ⊞ 6K · ◷

• expires on Jul 18, 2026, 8:39 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1481.