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

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 55

Parent issues created

None — all clusters had existing parents.

Links created (25 total)

Parent	Theme	Sub-issues
#1285 Recurring agentic workflow failures	[aw] rate-limit / failure incidents	#1369, #1373, #1388, #1389, #1412, #1414, #1430, #1435, #1441, #1459, #1467, #1478, #1483, #1485, #1492, #1493
#1283 Track upstream deps release-notes	[deps-release-notes] tracking issues	#1253 (mcpg), #1304 (awf), #1305 (copilot-cli)
#1286 Compiler internals improvements	Compile refactors	#384 (YAML gen manual string building), #987 (split agentic-pipeline shape), #1378 (unify AzureCLI@2 token-mint)
#1321 MCPG infrastructure improvements	MCP/container issues	#254 (surface MCPG failures), #945 (custom MCP env passthrough), #1034 (MCPG docker invalid reference)

Suggested (not linked — for maintainer review)

• fix(safe-outputs): add file staging to upload-workitem-attachment #381, add-pr-comment: render inline threads as applyable single/multi-line suggestions #1103, feat: support reusable cross-repository custom safe-output jobs #1473, debug: upload-pipeline-artifact fails with ContainerWriteAccessDeniedException when uploading to other builds #471 could form a "safe-output tool correctness & improvement" cluster under [Parent] Safe-output executor E2E test coverage and tool correctness #1428, but only 4 issues — below the 5+ threshold. Worth revisiting once more accumulate.
• feat: decouple prompt body from compiled pipeline output (runtime-import approach) #237, Inject runtime parameter values into the agent prompt via ado-script (sanitization at runtime, not compile time) #432, feat: built-in PR context precomputation for PR-triggered agents #860 (runtime prompt decoupling / parameter injection / PR context) are thematically related; could warrant a parent around "agent execution context and runtime prompt features" if more issues accumulate.
• 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 (chore: recompile fixtures after version bumps) are routine maintenance, not failures — left unlinked from [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285 intentionally.
• 🔴 Red Team Audit — High: Shell injection via runtimes.lean.toolchain #855 (🔴 shell injection via runtimes.lean.toolchain) is a standalone security finding with no obvious parent; worth a dedicated security backlog parent if more red-team findings are filed.

Observations

• The backlog is dominated by recurring [aw] rate-limit / failure incidents — [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285 now absorbs 16 of them, making the failure cadence visible at a glance.
• Three existing parents ([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) had orphan children scattered in the top-100; all have been linked.
• Several enhancement issues (feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451, proposal: adopt Copilot sidecar (SDK-driver) execution model #1486, Feature request: first-class TLA+ / TLC (Java) runtime support #1222) remain orphans with no clear sibling cluster yet.

Generated by Issue Arborist · 60.5 AIC · ⌖ 6.1 AIC · ⊞ 6K · ◷

• expires on Jul 20, 2026, 8:47 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1514.