[Issue Arborist] Weekly backlog scan — no new links, suggestions for review

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 62 (open, not already sub-issues)

Parent issues created

None.

Links created

None.

Suggested (not linked — for maintainer review)

The vast majority of open issues already sit under existing parent-tracking
issues (#1283 deps-release-notes, #1286 compiler internals, #1321 MCPG/safe-output
tooling, #1428 executor E2E, #1549 recurring failures, #1649 agent runtime, #2076
self-optimization follow-ups), confirmed via each issue's parent link. The
remaining orphans are related in theme but not in an unambiguous parent/child
sense, so I did not link them:

• [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 (engine.model driven by ADO pipeline variable), [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 (declarative ADO
  pipeline variables in workflow source), and [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044 (agents cannot supply
  runtime-computed work-item fields) all touch "surface ADO
  variables/runtime values into workflow source" but are parallel
  features of similar scope — none is clearly broader than the others.
• 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(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156 ("chore(workflows): recompile safe-output fixtures with
  ado-aw vX.Y.Z") are a recurring maintenance pattern but only 3 open
  instances — below the 5-issue threshold for a new parent, and each is a
  one-off release chore rather than a durable epic.
• refactor(compile): unify AzureCLI@2 token-mint steps behind a shared typed helper #1378 (unify AzureCLI@2 token-mint steps) and Reject unwireable cross-job provider-env macros on engine.env (follow-up to #1372) #1375 (reject unwireable
  cross-job provider-env macros) are both compiler-internals refactors that
  could arguably join [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, but neither is currently linked and I could not
  confirm scope-containment without deeper code review.
• [aw] Agent Documentation Maintainer produced no safe outputs #2121 ([aw] Agent Documentation Maintainer produced no safe outputs) is a
  fresh (today) failure report; too new to confidently cluster.

Observations

• The backlog is well-curated: nearly all substantive open issues already
  belong to a tracking parent from prior Arborist runs.
• No cluster of 5+ genuinely-orphaned, clearly-themed issues was found this
  run, so no new parent issues were created (conservative-linking policy).
• Candidates worth a maintainer's manual look: whether refactor(compile): unify AzureCLI@2 token-mint steps behind a shared typed helper #1378/Reject unwireable cross-job provider-env macros on engine.env (follow-up to #1372) #1375 belong
  under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, and whether the three pipeline-variable-surfacing issues
  ([aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035, [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012, [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044) should be grouped under a new "runtime-computed
  configuration values" epic once a 4th/5th related issue appears.

Generated by Issue Arborist · auto · 84.5 AIC · ⌖ 1.83 AIC · ⊞ 9.7K · ◷

• expires on Sep 15, 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 #2135.