[Issue Arborist] Issue Arborist Run — no new links (backlog already well-organized)

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 60 (pre-fetched open, non-sub-issues)

Parent issues created

None this run.

Links created

None this run.

Suggested (not linked — for maintainer review)

• [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 ("support declarative Azure DevOps pipeline variables in workflow source") and [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 ("Allow engine.model to be driven by an ADO pipeline variable / variable group") are thematically related to each other (both about compile-time-vs-runtime ADO pipeline variable configurability) and arguably fit under the existing [Parent] Compiler internals and pipeline generation improvements ([Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286). I did not link them because only two issues share the theme (below the 5+ orphan-cluster bar) and [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286's existing scope is IR/YAML-gen/prompt-decoupling work rather than variable-configuration UX — a maintainer with fuller context should judge whether [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 is the right home, or whether these two alone don't yet warrant linking.

Observations

• The backlog is already well-curated by prior Arborist runs: six [Parent] trackers exist (#1283 deps release-notes, #1286 compiler internals, #1321 MCPG/safe-output tooling, #1428 safe-output E2E coverage, #1649 agent runtime/execution pipeline, #1535 AI-credits rate-limit failures, plus #1549 non-rate-limit execution failures), and the large majority of candidate issues in the 60-issue sample that looked like plausible children (e.g. feat(ir): add EnvValue::RuntimeExpression variant to prevent $[] in step env #1081, refactor(compile): split agentic-pipeline shape out of standalone_ir.rs; move Agent-job condition contributions into Declarations #987, YAML generation uses manual string building in compile_gate_step_external #384, Reject unwireable cross-job provider-env macros on engine.env (follow-up to #1372) #1375, [agent-issue]: align GitHub issue-reporting token variable names #1632, feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451, refactor(mcpg): type container runtime arguments and mounts #1835, [agent-issue]: create-pull-request cannot target a repository from another Azure DevOps organisation #1934, [agent-issue]: support weekday-only fuzzy schedules and cron parity #1965, MCPG step fails with docker: invalid reference format. — extra \ \ after -e ADO_MCP_AUTH_TOKEN in generated YAML (v0.36.0) #1034, fix(safe-outputs): add file staging to upload-workitem-attachment #381, feat: surface MCPG backend failures in pipeline logs #254, add-pr-comment: render inline threads as applyable single/multi-line suggestions #1103, Custom MCP container env passthrough never reaches the server (step env mapping missing) #945, debug: Noop smoke pipeline fails to pull non-existent ghcr.io/github/gh-aw-mcpg:v0.3.7 (manifest unknown) #621, debug: upload-pipeline-artifact fails with ContainerWriteAccessDeniedException when uploading to other builds #471, [agent-issue]: Gateway-managed, auto-refreshed Azure federated token file for user-defined MCP servers #1964, Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652) were already linked to one of these parents.
• No cluster of 5 or more currently-unlinked issues sharing a clear, unambiguous theme was found. Small thematic pairs exist (e.g. [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012/[aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 above) but fall short of the 5+ threshold this workflow requires for creating a new parent.
• Per the conservative-linking policy, I chose not to force any single-digit-count links to avoid low-confidence associations that would need manual cleanup.

Generated by Issue Arborist · auto · 111.9 AIC · ⌖ 1.84 AIC · ⊞ 9.7K · ◷

• expires on Sep 7, 2026, 8:36 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2077.