[Issue Arborist] Run summary — 2026-09-01

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 62

Parent issues created

Parent	Theme	Sub-issues	Reasoning
#2076 "Track self-optimization design follow-ups (extracted from #1061)"	Follow-ups to closed self-optimization design PR #1061	#2067, #2068, #2069, #2070, #2071	All five issues explicitly state "Follow-up extracted from #1061," share the same closed source PR, and together sequence the safe path (hoisting → strict validation → telemetry grounding → preview-only proposal → front-matter editor) toward auto-applied optimizations. Clear, unambiguous cluster with no existing parent.

Links created

Parent	Sub-issue	Reasoning
#1321	#1964	#1964 is a gateway/MCP-server auth improvement (Azure federated token refresh for user-defined MCP servers); #1321 already tracks "MCPG infrastructure and safe-output tooling improvements" and #1964 explicitly cross-references #1652 and #945, both already under this umbrella.
#1649	#1652	#1652 (Stage 1 ADO-proxy read isolation) is an agent-runtime/execution-pipeline credential improvement; #1649 is the umbrella for exactly this category and already links sibling issues (#1486, #860, #432, #237, #1375) with the same shape.
#1286	#1834	#1834 is a typed-IR/codegen refactor (install steps as typed steps, not rendered YAML) — squarely "compiler internals... IR types, YAML gen" which #1286 already tracks (e.g. #1081, #987, #384).
#1428	#1798	#1798 is explicitly a safe-output executor E2E coverage task (create-github-issue / set-github-issue-type scenarios) for the executor-e2e harness — exactly #1428's scope, and #1798 already declared has_parent: true pointing at #1428 (confirmed, not newly established).
#1286	#1192	#1192 is a docs-drift fix for the typed-IR task-builder API, matching #1286's "compiler internals... IR types" scope; it already listed has_parent: 1286 in GitHub.

Suggested (not linked — for maintainer review)

• docs: conclusion job token reference omits SC_WRITE_TOKEN #1766 and docs: fix AGENTS.md accuracy — add trigger-e2e to ado-script tree and export-fact-catalog to CLI index #1583 both already show has_parent: #1286 per GitHub but were not separately reconfirmed here — no action needed, listed for completeness.
• [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044 (agent-supplied work-item fields), [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 (runtime-variable engine.model), [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 (declarative pipeline variables:), [agent-issue]: support weekday-only fuzzy schedules and cron parity #1965 (weekday fuzzy schedules), feat: allow enable to target individual pipeline files #1634 (enable target individual files) are all standalone enhancement requests without 5+ shared-theme siblings; not linked.
• [deps-release-notes] mcpg — upstream release action items #2040/[deps-release-notes] copilot-cli — upstream release action items #2041/[deps-release-notes] awf — upstream release action items #2028 are the three canonical rolling dependency-release-note trackers already parented under [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 — no new linking needed.
• [agent-issue]: align GitHub issue-reporting token variable names #1632 (align GitHub issue-reporting token variable names) is thematically close to chore(security): minimize AWF agent environment and mask unused gh CLI #1818 (minimize AWF agent environment) and Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 (ado-proxy) as "credential/token hygiene" work, but scopes differ enough (naming consistency vs. runtime isolation) that a confident parent-child link wasn't warranted — flagging for maintainer judgment.

Observations

• The backlog already has healthy hygiene: most substantive issues are pre-parented ([Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, [Parent] MCPG infrastructure and safe-output tooling improvements #1321, [Parent] Safe-output executor E2E test coverage and tool correctness #1428, [Parent] Track agent runtime and execution pipeline improvements #1649, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283), so this run mostly picked up recent unparented arrivals (Hoist deterministic repeated agent work into workflow steps #2067–Preserve comments when updating workflow front matter #2071) and a few issues whose parent linkage existed in GitHub metadata but hadn't been reflected via link_sub_issue yet.
• Several [agent-issue]-tagged external reports ([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, [agent-issue]: support weekday-only fuzzy schedules and cron parity #1965, [agent-issue]: Gateway-managed, auto-refreshed Azure federated token file for user-defined MCP servers #1964) are high-quality, well-scoped feature requests from external users of the compiler — worth periodic triage into themed parents once 5+ accumulate around a specific area (e.g., "front-matter schema extensions" is trending: [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 both request new compile-time-configurable front-matter surfaces).

Generated by Issue Arborist · auto · 78.6 AIC · ⌖ 2.02 AIC · ⊞ 9.7K · ◷

• expires on Sep 8, 2026, 8:34 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2092.