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

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 55

Parent issues created

None — no orphan cluster of 5+ unambiguously related issues without an existing parent was found.

Links created (30 total)

Parent	Theme	Sub-issues	Reasoning
#1285	Recurring agentic workflow failure incidents	#1441, #1435, #1430, #1412, #1389, #1388, #1373, #1369, #1365, #1351, #1338, #1336, #1323, #1320, #1308	All are individual [aw] pipeline run failure reports (rate-limit, no-safe-outputs, engine failure) — exactly the incident pattern #1285 tracks
#1283	Track upstream deps release notes	#1305, #1304, #1253	All three [deps-release-notes] issues (awf, mcpg, copilot-cli) are direct work items spawned by the tracker the parent describes
#1321	MCPG infrastructure and safe-output tooling improvements	#1034, #945, #254	All three relate to MCPG container integration: Docker reference format bug, MCP env passthrough gap, and surfacing MCPG backend failures
#1428	Safe-output executor E2E test coverage and tool correctness	#1422, #1413, #1103, #381, #471	#1422 is an explicit E2E gap; #1413, #1103, #381, #471 are safe-output tool correctness bugs (create-pull-request shallow clone, add-pr-comment inline threads, upload-workitem-attachment staging, upload-pipeline-artifact permissions)
#1286	Compiler internals and pipeline generation improvements	#1378, #987, #384, #237	All four are compiler refactors explicitly named in the parent's scope: unify AzureCLI@2 helpers, split agentic-pipeline shape, replace manual YAML string building, and prompt-body decoupling

Suggested (not linked — for maintainer review)

• Agent configuration improvements (feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451, Inject runtime parameter values into the agent prompt via ado-script (sanitization at runtime, not compile time) #432, Allow config overrides e.g. npmrc for built ins #253, Reject unwireable cross-job provider-env macros on engine.env (follow-up to #1372) #1375, feat(ir): add EnvValue::RuntimeExpression variant to prevent $[] in step env #1081): five open enhancement issues touching front-matter schema alignment, runtime parameter injection, built-in config overrides, engine.env macro validation, and EnvValue::RuntimeExpression — could warrant a new [Parent] Agent configuration, environment handling, and schema alignment parent, but the breadth across layers makes the cluster somewhat loose
• Recompile fixture chores (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 recurring chore(workflows): recompile safe-output fixtures with ado-aw vX.Y.Z issues share a pattern and could become sub-issues of a housekeeping parent once there are five or more
• Compiler operational bugs (compile: directory argument silently no-ops instead of auto-discovering or erroring #867, debug: v0.31.1 compiler emits different YAML than committed *.lock.yml files from #861, breaking integrity check #866, debug: Noop smoke pipeline fails to pull non-existent ghcr.io/github/gh-aw-mcpg:v0.3.7 (manifest unknown) #621): three debug/compile bugs (directory no-op, YAML integrity mismatch, image manifest failure) share a "pipeline runs unexpectedly broken" theme but vary enough in root cause that linking is speculative

Observations

• [aw] Detection Runs #793 and [aw] No-Op Runs #13 ([aw] Detection Runs / [aw] No-Op Runs) are infrastructure-managed meta-tracking issues created by gh-aw automation; they carry "Do not assign to an agent" notices and should not be treated as work items or linked as sub-issues
• [Parent] Issue Arborist - Issue Group #1284 ([Parent] Issue Arborist - Issue Group) has an ambiguous title with no clear scope — no issues were confidently attributed to it; may benefit from a retitle or closure
• 🔴 Red Team Audit — High: Shell injection via runtimes.lean.toolchain #855 (Shell injection via runtimes.lean.toolchain) is a high-priority standalone security finding with no parent; worth triaging separately
• The backlog has a very high volume of recurring [aw] failure incidents (15 linked this run alone to [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285) — reducing rate-limit failures upstream would significantly reduce backlog noise

Generated by Issue Arborist · 64.8 AIC · ⌖ 9.75 AIC · ⊞ 6K · ◷

• expires on Jul 16, 2026, 9:04 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1466.