[Issue Arborist] Issue Arborist Report

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 74 (open, non-sub-issues)

Parent issues created

Parent	Theme	Sub-issues	Reasoning
—	—	—	No new parent created: no orphan cluster of 5+ unparented issues shared a clear theme. Most backlog issues are already organized under existing [Parent] tracking issues (#1284, #1286, #1321, #1428, #1535, #1549, #1649, #1283, #2076).

Links created

Parent	Sub-issue	Reasoning
#1549	#2180	#1549 already tracks recurring non-rate-limit [aw] workflow execution failures (11 similar [aw] Issue Triage/Docs Writer/Cyclomatic Complexity Reducer failures already linked). #2180 ([aw] Issue Triage failed) is the same failure pattern and was the only unlinked orphan of that type found.
#1286	#2186	#1286 tracks compiler-internals / pipeline-generation improvements (engine invocation, YAML gen, prompt handling). #2186 (fix(engine): pass Copilot prompt using attached --prompt= form) is a concrete engine-invocation bug matching that scope and had no parent.

Suggested (not linked — for maintainer review)

• [aw] No-Op Runs #13 ([aw] No-Op Runs) is a standing aggregator issue by design (accumulates no-op comments); not a genuine parent/child candidate.
• Feature request: first-class TLA+ / TLC (Java) runtime support #1222 (TLA+/TLC runtime request), Allow config overrides e.g. npmrc for built ins #253 (config overrides for built-ins/npmrc), feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451 (align FrontMatter fields) sit close in theme to [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286's compiler-internals umbrella, but each is a standalone feature proposal rather than an implementation task of that epic — left unlinked pending maintainer judgment on scope fit.
• feat: allow enable to target individual pipeline files #1634 (enable targeting individual pipeline files), test(smoke): report scheduled smoke failures as GitHub issues from the orchestrator #1796 (report scheduled smoke failures from orchestrator), 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 (safe-output fixture recompiles for older ado-aw versions) are each isolated, one-off asks with no sibling cluster — no confident parent found.
• [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, [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, refactor(engine): emit typed install steps instead of YAML strings #1834, fix(smoke): route multi-repo Cargo through the internal feed #1823, chore(security): minimize AWF agent environment and mask unused gh CLI #1818, test(executor-e2e): add create-github-issue and set-github-issue-type scenarios #1798, docs: conclusion job token reference omits SC_WRITE_TOKEN #1766, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763, Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652, [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, refactor(compile): unify AzureCLI@2 token-mint steps behind a shared typed helper #1378, docs(site): refresh IR typed-helper docs to builder-struct API #1192, compile: directory argument silently no-ops instead of auto-discovering or erroring #867, debug: v0.31.1 compiler emits different YAML than committed *.lock.yml files from #861, breaking integrity check #866, 🔴 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 were all already correctly linked under an existing parent — no action needed.

Observations

• The backlog is well-tracked: the majority of open issues already roll up under nine existing [Parent] umbrella issues, leaving very few true orphans this run.
• The [aw] failure-report issues (Issue Triage, Docs Writer, Cyclomatic Complexity Reducer, etc.) are auto-generated by scheduled workflows and mostly already flow into [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549; only [aw] Issue Triage failed #2180 needed catching up.
• Recompile-fixture chores (chore(workflows): recompile safe-output fixtures with ado-aw v0.36.0 #1027, chore(workflows): recompile safe-output fixtures with ado-aw v0.37.0 #1041, chore(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156) recur per-release but are typically closed quickly rather than accumulating into a lasting cluster, so they don't currently warrant a dedicated parent.

Generated by Issue Arborist · auto · 71.7 AIC · ⌖ 1.67 AIC · ⊞ 8.6K · ◷

• expires on Sep 24, 2026, 8:39 PM UTC