[Issue Arborist] Issue Arborist Report — 2026-07-26

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 54

Parent issues created

None this run — no orphan cluster of 5+ unlinked issues with a clear shared theme was found.

Links created

Parent	Sub-issue	Reasoning
#1286 (Compiler internals and pipeline generation improvements)	#451 (feat: align FrontMatter fields with gh-aw schema)	Front matter fields are a core compiler-internal concern; #451 proposes types.rs changes with compiler wiring and doc updates that fit squarely under #1286's scope.
#1649 (Track agent runtime and execution pipeline improvements)	#855 (🔴 Red Team Audit — High: Shell injection via runtimes.lean.toolchain)	The vulnerability is in the Lean 4 runtime compilation path, directly an agent runtime concern scoped under #1649.

Suggested (not linked — for maintainer review)

• feat: allow enable to target individual pipeline files #1634 (feat: allow enable to target individual pipeline files) — lifecycle command enhancement with no existing lifecycle parent. Could warrant a new "Lifecycle command improvements" parent if more lifecycle issues accumulate.
• Feature request: first-class TLA+ / TLC (Java) runtime support #1222 (Feature request: first-class TLA+ / TLC (Java) runtime support) and Allow config overrides e.g. npmrc for built ins #253 (Allow config overrides e.g. npmrc for built-ins) — both runtime-layer concerns; only 2 unlinked runtime issues, not enough for a new parent, but worth tracking together.
• chore(workflows): recompile safe-output fixtures with ado-aw v0.38.0 #1156, 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 (recompile safe-output fixtures v0.38/0.37/0.36) — recurring chore cluster (3 issues); below the 5-issue threshold for a new parent, but a "lock-file sync" parent may be warranted once Consumer repos have no built-in way to keep generated *.lock.yml in sync (drift/freshness gap) #1663 (consumer drift/freshness gap) progresses and more related issues emerge.
• [aw] Detection Runs #793 ([aw] Detection Runs) and [aw] No-Op Runs #13 ([aw] No-Op Runs) — agentic workflow monitoring dashboards, not failure reports. They don't clearly fit under either [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535 (rate-limit failures) or [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 (non-rate-limit failures). Maintainers may want a dedicated "Agentic Workflow Monitoring" parent.

Observations

• The backlog is well-structured: most active issue groups ([Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535, [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, [Parent] MCPG infrastructure and safe-output tooling improvements #1321, [Parent] Safe-output executor E2E test coverage and tool correctness #1428, [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, [Parent] Track agent runtime and execution pipeline improvements #1649) already have parent issues and sub-issue links.
• The rate-limit parent ([Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535) and non-rate-limit failure parent ([Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549) are doing good work absorbing recurring [aw] failure issues automatically.
• [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 (upstream deps tracking) is well-populated with all three deps-release-notes issues already linked.
• The unlinked remainder is small (10 issues) and heterogeneous — no large orphan cluster was found this run.

Generated by Issue Arborist · 50.7 AIC · ⌖ 8.27 AIC · ⊞ 6.1K · ◷

• expires on Aug 2, 2026, 8:43 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1691.