[Issue Arborist] 🌳 Issue Arborist Report

[github-actions[bot]]

Issues analyzed: 71

Parent issues created

None — every genuine cluster found already had an existing [Parent] tracking issue, so no new parents were created (0/3 used).

Links created

Parent	Sub-issue	Reasoning
#1549	#2162	Issue Triage engine failure — recurring non-rate-limit workflow failure
#1549	#2156	Docs Writer failed jobs — recurring non-rate-limit workflow failure
#1549	#2155	Issue Triage produced no safe outputs
#1549	#2153	Issue Triage engine failure
#1549	#2149	Issue Triage produced no safe outputs
#1549	#2142	Cyclomatic Complexity Reducer engine failure
#1549	#2141	Agent Documentation Maintainer engine failure
#1549	#2140	Issue Triage engine failure
#1549	#2137	Issue Triage produced no safe outputs
#1549	#2134	Issue Triage engine failure
#1549	#2121	Agent Documentation Maintainer produced no safe outputs
#2076	#2067	Self-optimization follow-up: hoist deterministic agent work into steps
#2076	#2068	Self-optimization follow-up: strict validation for raw step fragments
#2076	#2069	Self-optimization follow-up: preview-only proposal safe output
#2076	#2070	Self-optimization follow-up: telemetry-grounded optimization proposals
#1649	#1486	Agent runtime/execution: Copilot sidecar execution model
#1649	#432	Agent runtime/execution: inject runtime params into prompt via ado-script
#1649	#237	Agent runtime/execution: decouple prompt body from compiled pipeline
#1649	#1375	Agent runtime/execution: reject unwireable cross-job provider-env macros
#1649	#860	Agent runtime/execution: built-in PR context precomputation
#1286	#1081	Compiler internals: EnvValue::RuntimeExpression IR type
#1286	#987	Compiler internals: split agentic-pipeline shape out of standalone_ir.rs
#1286	#384	Compiler internals: typed IR for compile_gate_step_external
#1286	#432	Compiler internals: runtime prompt injection (shared theme with #1649)
#1286	#237	Compiler internals: prompt/pipeline output decoupling (shared theme with #1649)
#1321	#621	MCPG/safe-output tooling: noop smoke pipeline pull failure
#1321	#254	MCPG/safe-output tooling: surface MCPG backend failures in logs
#1321	#1103	MCPG/safe-output tooling: add-pr-comment inline suggestion rendering
#1321	#381	MCPG/safe-output tooling: upload-workitem-attachment file staging
#1321	#471	MCPG/safe-output tooling: upload-pipeline-artifact access denied

Note: hit the 30-link-per-run cap after 30 successful links; #2071 (5th self-optimization follow-up for #2076) was attempted but rejected by the limit — it is a strong, unambiguous match and should be linked to #2076 in a future run.

Suggested (not linked — for maintainer review)

• Preserve comments when updating workflow front matter #2071 → [Parent] Track self-optimization design follow-ups (extracted from #1061) #2076 (blocked only by this run's 30-link cap; link next run)
• [agent-issue]: Allow model-selected reviewers in create-pull-request #2090, [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [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 ([agent-issue] runtime/config feature requests) share a loose "runtime-configurable value" theme with [Parent] Track agent runtime and execution pipeline improvements #1649/[Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 but each targets a distinct mechanism (reviewers, work-item fields, variable groups, model selection) — not confident enough to force under one parent.
• Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 (Stage 1 ADO proxy credential isolation) is closely related to the ado-proxy work referenced in [Parent] MCPG infrastructure and safe-output tooling improvements #1321's security context but is its own large security effort — left unlinked pending a dedicated parent if more proxy-related issues appear.
• [deps-release-notes] awf — upstream release action items #2028/[deps-release-notes] mcpg — upstream release action items #2040/[deps-release-notes] copilot-cli — upstream release action items #2041 (deps-release-notes rolling trackers) and [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 (dependency umbrella) already function as their own canonical rolling issues; no additional linking needed.
• [aw] Detection Runs #793 and [aw] No-Op Runs #13 are auto-maintained rolling logs (detection-problem and no-op runs), not backlog items — excluded from clustering.

Observations

• The backlog already has strong [Parent] umbrella hygiene from prior Arborist runs; most new orphans map cleanly onto existing trackers rather than needing fresh clusters.
• A steady stream of [aw] ... failed / produced no safe outputs issues continues to accumulate against [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 — worth prioritizing root-cause fixes there since it's now the largest sub-issue cluster.
• Four [agent-issue] feature requests ([agent-issue]: Allow model-selected reviewers in create-pull-request #2090, [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [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) around runtime-configurable pipeline values could become a 5th cluster if 1-2 more similar requests are filed.

Generated by Issue Arborist · auto · 79.5 AIC · ⌖ 2.04 AIC · ⊞ 9.1K · ◷

• expires on Sep 21, 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 #2171.