[Issue Arborist] Issue Arborist Report

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 66

Parent issues created

None — no orphan cluster of 5+ unlinked issues was found this run.

Links created

Parent	Sub-issue	Reasoning
#1549	#2142	Same-pattern [aw] ... failed workflow-failure report; siblings #2137, #2134, #2121 already linked to this parent
#1549	#2141	Same-pattern [aw] ... failed workflow-failure report; matches parent's non-rate-limit failure theme
#1549	#2140	Same-pattern [aw] Issue Triage failed report; sibling #2137/#2134 already linked
#1652	#1818	#1818 is explicit follow-up work (env hardening, gh masking) for the credential-isolated ADO proxy design tracked by #1652
#253	#1823	Both concern configuring per-ecosystem internal package feeds (npmrc/Cargo config) reaching the AWF sandbox; #1823 is a concrete Cargo-feed incident under the general feed-override request

Suggested (not linked — for maintainer review)

• [aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035 (runtime-configurable engine.model) and [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012 (declarative pipeline variables:) are both about compile-time-only config that operators want runtime/variable-group driven — a plausible shared theme, but only 2 issues, below the 5+ cluster threshold.
• [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044 (agent-writable arbitrary work-item fields) and [agent-issue]: Allow model-selected reviewers in create-pull-request #2090 (agent-supplied PR reviewers) share a theme of "safe-output params need runtime-computed fields the schema currently rejects" — worth a parent if more surface.
• test(smoke): report scheduled smoke failures as GitHub issues from the orchestrator #1796 (file GitHub issue on scheduled smoke failure) and test(executor-e2e): add create-github-issue and set-github-issue-type scenarios #1798 (executor-e2e scenario gaps) both touch smoke/E2E coverage gaps but are different enough in mechanism (deterministic reporting vs. test scenarios) that I did not link them.
• feat: allow enable to target individual pipeline files #1634 (enable cannot target one pipeline file) is related in spirit to lifecycle-command safety but has no existing parent umbrella for CLI lifecycle-command UX; not linked due to lack of a clear existing home.
• docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763 (docs: repo-relative paths) and docs: conclusion job token reference omits SC_WRITE_TOKEN #1766 (docs: SC_WRITE_TOKEN reference) are both doc-freshness issues but docs: conclusion job token reference omits SC_WRITE_TOKEN #1766 already sits under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 (compiler internals) which is not a strong fit for pure docs content — flagged for maintainer judgment rather than linked speculatively.

Observations

• The backlog is already well-groomed: the large majority of substantive issues (compiler internals [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, MCPG/safe-outputs [Parent] MCPG infrastructure and safe-output tooling improvements #1321, agent runtime [Parent] Track agent runtime and execution pipeline improvements #1649, executor-e2e [Parent] Safe-output executor E2E test coverage and tool correctness #1428, dependency release-notes [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, rate-limit failures [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535, non-rate-limit failures [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549, self-optimization follow-ups [Parent] Track self-optimization design follow-ups (extracted from #1061) #2076) already have an active parent umbrella with sub-issues linked.
• Most [deps-release-notes] and [aw] auto-filed issues from this batch were already parented; only the 3 newest [aw] ... failed reports ([aw] Cyclomatic Complexity Reducer failed #2142/[aw] Agent Documentation Maintainer failed #2141/[aw] Issue Triage failed #2140) were orphaned stragglers from the same recurring pattern.
• No genuinely new 5+ orphan cluster emerged in this batch — recent agent-filed feature requests ([aw]: Allow engine.model to be driven by an ADO pipeline variable / variable group #2035, [agent-issue]: Agents cannot supply work-item fields; custom-fields is compile-time only, so runtime-computed values never reach ADO #2044, [agent-issue]: Allow model-selected reviewers in create-pull-request #2090, [agent-issue]: support declarative Azure DevOps pipeline variables in workflow source #2012, Add preview-only self-optimization safe output #2069/Add strict validation for untrusted raw step fragments #2068/Ground optimization proposals in recorded telemetry #2070/Preserve comments when updating workflow front matter #2071 already parented) are each distinct enough in mechanism to avoid speculative grouping.

Generated by Issue Arborist · auto · 123.2 AIC · ⌖ 1.82 AIC · ⊞ 9.1K · ◷

• expires on Sep 18, 2026, 8:40 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #2152.