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

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 57

Parent issues created

None this run — no orphan cluster of 5+ unparented issues meeting the threshold was found.

Links created

Parent	Sub-issue	Reasoning
#1285 Recurring agentic workflow failure incidents	#1459	Bash Step Hygiene Auditor failed — recurring pipeline failure
#1285	#1441	Dependency Version Updater rate limit
#1285	#1435	Test Reducer produced no safe outputs
#1285	#1430	Issue Arborist rate limit
#1285	#1414	Bash Step Hygiene Auditor failed
#1285	#1412	Dependency Version Updater rate limit
#1285	#1389	Rust PR Reviewer rate limit
#1285	#1388	Issue Arborist rate limit
#1285	#1373	Dependency Version Updater rate limit
#1285	#1369	Test Gap Finder failed
#1285	#1365	Issue Arborist rate limit
#1285	#1351	Issue Arborist rate limit
#1285	#1338	Test Reducer produced no safe outputs
#1285	#1336	Dependency Version Updater rate limit
#1286 Compiler internals and pipeline generation improvements	#384	YAML generation uses manual string building in compile_gate_step_external — IR/codegen quality
#1286	#987	Split agentic-pipeline shape out of standalone_ir.rs — compiler refactor
#1286	#1081	EnvValue::RuntimeExpression variant — typed IR improvement
#1286	#1378	Unify AzureCLI@2 token-mint steps behind shared typed helper — compiler refactor
#1283 Track upstream dependency release-note action items	#1253	mcpg release-notes tracking issue
#1283	#1304	awf release-notes tracking issue
#1283	#1305	copilot-cli release-notes tracking issue

Total links created: 21

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, [aw]: Follow-up to #1413 / #1425: create-pull-request worktree fails — the prepare-pr-base step runs in the Agent job, but the executor runs in the SafeOutputs job (standalone target) #1453 (create-pull-request shallow-clone chain) could both be sub-issues of [Parent] Safe-output executor E2E test coverage and tool correctness #1428 (safe-output executor E2E test coverage) or of a new parent tracking prepare-pr-base correctness. Only 2 issues — below the new-parent threshold, but worth linking manually.
• [agent-issue]: support per-job pool overrides for generated jobs #1464 (per-job pool overrides) and [agent-issue]: support standard Azure Pipelines pool demands #1450 (pool demands) are thematically related. Only 2 issues; worth a parent if more pool-configuration requests emerge.
• Custom MCP container env passthrough never reaches the server (step env mapping missing) #945 (custom MCP container env passthrough), MCPG step fails with docker: invalid reference format. — extra \ \ after -e ADO_MCP_AUTH_TOKEN in generated YAML (v0.36.0) #1034 (MCPG docker invalid reference), feat: surface MCPG backend failures in pipeline logs #254 (surface MCPG backend failures) are all MCPG wiring issues — consider linking to [Parent] MCPG infrastructure and safe-output tooling improvements #1321 (MCPG infrastructure improvements).
• 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 fixtures chores) are mechanically identical; a parent tracking "fixture recompile cadence" might be useful but the issues are effectively resolved once done.
• [agent-issue]: make generated SafeOutputs MCP trusted and explicitly allowed by Copilot CLI #1452 (SafeOutputs MCP not trusted by Copilot CLI) could be related to [Parent] MCPG infrastructure and safe-output tooling improvements #1321 (MCPG/safe-output tooling improvements).
• feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451 (align FrontMatter with gh-aw schema) is a large feature request that could parent several targeted FrontMatter field issues if those are filed separately.

Observations

• AI credits rate limiting is the dominant failure mode: 9 of the 14 recurring failure incidents under [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285 are rate-limit hits. This is worth a dedicated investigation/mitigation issue.
• [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285 had no sub-issues despite tracking exactly these incidents — now fully populated.
• [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 had no sub-issues despite three active deps-tracking issues existing.
• The backlog has a healthy set of existing parent issues ([Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, [Parent] Recurring agentic workflow failure incidents (docs-freshness, dependency-updater rate-limit, test-gap-finder) #1285, [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) that were just missing their children.
• [Parent] Issue Arborist - Issue Group #1284 ("Issue Arborist — Issue Group") appears to be a stale meta-issue from a previous arborist run; no clear children to link.

Generated by Issue Arborist · 53.6 AIC · ⌖ 6.25 AIC · ⊞ 6K · ◷

• expires on Jul 17, 2026, 8:53 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1474.