[Issue Arborist] Issue Arborist Run — 2026-09-30

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 73 (last 100 open issues not already sub-issues)

Parent issues created

None. No orphan cluster of 5+ clearly related issues without an existing parent was found — every thematic cluster I identified already has one of the existing [Parent] tracking issues (#1286 compiler internals, #1321 MCPG/safe-outputs, #1428 executor E2E, #1549 non-rate-limit failures, #1649 agent runtime, #1652 ADO-proxy, #2076 self-optimization, #1283 dependency release notes).

Links created

Parent	Sub-issue	Reasoning
#1549	#2269	"[aw] Issue Triage is missing required tool" is a non-rate-limit recurring workflow-execution failure, matching #1549's scope exactly.
#1286	#2270	target: 1es configurability request is a compiler/IR pipeline-generation improvement.
#1321	#1041	"recompile safe-output fixtures with v0.37.0" is MCPG/safe-output tooling maintenance.
#1321	#1027	Same as above, v0.36.0 fixture recompile.
#1286	#1834	refactor(engine): emit typed install steps is a compiler-internals/IR refactor.
#1286	#1378	refactor(compile): unify AzureCLI@2 token-mint steps is a compiler-internals refactor.
#1649	#13	"[aw] No-Op Runs" tracks agentic-workflow execution outcomes, broadly under agent runtime/execution-pipeline tracking (lower-confidence link — see below).

Suggested (not linked — for maintainer review)

• [aw] Issue Triage failed #2264, [aw] Issue Triage produced no safe outputs #2262, [aw] Cyclomatic Complexity Reducer failed #2257, [aw] Issue Triage failed #2255, [aw] Issue Triage failed #2251, [aw] Failed jobs: Dependency Version Updater #2249, [aw] Issue Triage produced no safe outputs #2248, [aw] Issue Triage failed #2242, [aw] Issue Triage failed #2235 — all recent [aw] ... failed / no safe outputs reports already carry has_parent: true pointing at [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549, so no action was needed; verified already linked.
• [aw] Detection Runs #793 "[aw] Detection Runs" is a standing rolling-log issue (parent: null), same shape as [aw] No-Op Runs #13. I linked [aw] No-Op Runs #13 to [Parent] Track agent runtime and execution pipeline improvements #1649 but left [aw] Detection Runs #793 unlinked since "Detection Runs" is more a threat-detection log than an execution-pipeline improvement — a maintainer may want to create a dedicated "rolling logs" parent for [aw] No-Op Runs #13/[aw] Detection Runs #793/[Parent] Issue Arborist - Issue Group #1284/[deps-release-notes] awf — upstream release action items #2252/[deps-release-notes] awf — upstream release action items #2230/[deps-release-notes] copilot-cli — upstream release action items #2232/[deps-release-notes] mcpg — upstream release action items #2040 instead (these six are all rolling/tracking issues rather than discrete work items, and don't fit neatly as sub-issues of the work-tracking parents).
• Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 already has a sub-issue relationship (has_children: true) worth double-checking for completeness — did not re-link since it already has 1 child tracked.
• [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [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, Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652, proposal: adopt Copilot sidecar (SDK-driver) execution model #1486, Reject unwireable cross-job provider-env macros on engine.env (follow-up to #1372) #1375, add-pr-comment: render inline threads as applyable single/multi-line suggestions #1103, fix(safe-outputs): add file staging to upload-workitem-attachment #381, debug: upload-pipeline-artifact fails with ContainerWriteAccessDeniedException when uploading to other builds #471, feat: surface MCPG backend failures in pipeline logs #254, debug: Noop smoke pipeline fails to pull non-existent ghcr.io/github/gh-aw-mcpg:v0.3.7 (manifest unknown) #621, test(executor-e2e): add create-github-issue and set-github-issue-type scenarios #1798, docs(site): refresh IR typed-helper docs to builder-struct API #1192, feat(ir): add EnvValue::RuntimeExpression variant to prevent $[] in step env #1081, feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451, Inject runtime parameter values into the agent prompt via ado-script (sanitization at runtime, not compile time) #432, debug: v0.31.1 compiler emits different YAML than committed *.lock.yml files from #861, breaking integrity check #866, compile: directory argument silently no-ops instead of auto-discovering or erroring #867, 🔴 Red Team Audit — High: Shell injection via runtimes.lean.toolchain #855, 🧪 Test gap analysis — 3 gaps found in compile/job, compile/stage, and update_check #647, docs: conclusion job token reference omits SC_WRITE_TOKEN #1766, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763, feat: allow enable to target individual pipeline files #1634, [agent-issue]: align GitHub issue-reporting token variable names #1632, docs: fix AGENTS.md accuracy — add trigger-e2e to ado-script tree and export-fact-catalog to CLI index #1583, Feature request: first-class TLA+ / TLC (Java) runtime support #1222 — all already carry a parent per the GitHub sub-issue API; no new action needed, confirmed in place.

Observations

• The backlog is well-organized: nearly every substantive issue already rolls up into one of ~10 standing [Parent] tracking issues, so this run mostly confirmed existing structure rather than creating new links.
• The six rolling/dependency-log issues ([aw] Detection Runs #793, [aw] No-Op Runs #13, [Parent] Issue Arborist - Issue Group #1284, [deps-release-notes] awf — upstream release action items #2252/[deps-release-notes] awf — upstream release action items #2230/[deps-release-notes] copilot-cli — upstream release action items #2232/[deps-release-notes] mcpg — upstream release action items #2040 dep-release-notes) form a recognizable "standing infrastructure logs" cluster that isn't naturally a sub-issue of any work-item parent; flagging for maintainers to decide if a dedicated parent is warranted.
• No 5+-issue orphan cluster met the bar for a new parent this run.

Generated by Issue Arborist · auto · 171.3 AIC · ⌖ 1.75 AIC · ⊞ 9.4K · ◷

• expires on Oct 7, 2026, 8:44 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2276.