[Issue Arborist] Issue Arborist Report

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 69

Parent issues created

None. No new orphan cluster of 5+ issues had a clear shared parent.

Links created

Parent	Sub-issue	Reasoning
#1283	#2322	copilot-cli upstream release action items fall under the dependency release-note tracker
#1283	#2252	awf upstream release action items fall under the same tracker
#1283	#2040	mcpg upstream release action items fall under the same tracker
#1428	#1798	Executor E2E scenarios for GitHub issue safe outputs fall under the safe-output E2E coverage tracker

Suggested (not linked — for maintainer review)

• [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [agent-issue]: Allow agent-supplied priority on work items #2354, [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 all ask for runtime or variable-driven values (work-item fields, priority, pipeline variables, engine.model). They could share a parent, but only 4 issues were involved, so I did not create one.
• perf(compile): avoid blocking fs reads in the async compile path for the package-config check #2358, fix(compile): surface unreadable repository roots in the package-config check #2359, fix(compile): decide how the package-config check treats symlinked config files #2360 and test(package-feeds): assert the cargo branch of the package-manager wrapper #2357 are package-config check follow-ups, 4 issues in total. They would form a cluster if one more appears.
• 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 and chore(workflows): recompile safe-output fixtures with ado-aw v0.36.0 #1027 are recurring "recompile safe-output fixtures" chores and are likely stale now that the smoke suite is markdown-only. Consider closing them.
• MCPG step fails with docker: invalid reference format. — extra \ \ after -e ADO_MCP_AUTH_TOKEN in generated YAML (v0.36.0) #1034, debug: Noop smoke pipeline fails to pull non-existent ghcr.io/github/gh-aw-mcpg:v0.3.7 (manifest unknown) #621 and debug: v0.31.1 compiler emits different YAML than committed *.lock.yml files from #861, breaking integrity check #866 are old bug reports that may already be fixed.

Observations

• The backlog already has many [Parent] trackers: [Parent] Track agent runtime and execution pipeline improvements #1649, [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] Safe-output executor E2E test coverage and tool correctness #1428, [Parent] MCPG infrastructure and safe-output tooling improvements #1321, [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 and [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283.
• Issues labelled [aw] ([aw] Detection Runs #793, [aw] No-Op Runs #13, [aw] Test Gap Finder is missing required data #2398) are workflow-generated noise, not candidates for linking.

Generated by Issue Arborist · auto · 21.5 AIC · ⊞ 5.6K · ◷

• expires on Nov 2, 2026, 8:37 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2411.