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

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 52

Parent issues created

None — all clusters had existing parents.

Links created

Parent	Sub-issue	Reasoning
#1535 Track AI-credits rate-limit failures	#1551	Issue Arborist hit AI credits rate limit — same failure category
#1535 Track AI-credits rate-limit failures	#1492	Dependency Version Updater hit AI credits rate limit
#1535 Track AI-credits rate-limit failures	#1478	Dependency Version Updater hit AI credits rate limit
#1535 Track AI-credits rate-limit failures	#1467	Issue Arborist hit AI credits rate limit
#1549 Recurring non-rate-limit workflow failures	#1493	Bash Step Hygiene Auditor failed
#1549 Recurring non-rate-limit workflow failures	#1485	Test Gap Finder failed
#1549 Recurring non-rate-limit workflow failures	#1483	Copilot Model List Updater reported incomplete result
#1549 Recurring non-rate-limit workflow failures	#1459	Bash Step Hygiene Auditor failed
#1321 MCPG infrastructure and safe-output tooling	#1541	create-pull-request breaks on shallow-fetch pipelines due to prepare-pr-base — a safe-output tooling bug
#1428 Safe-output executor E2E test coverage	#647	Test gap analysis covering compile/job, compile/stage, update_check — directly related to test coverage tracking

Total links created: 10

Suggested (not linked — for maintainer review)

• proposal: adopt Copilot sidecar (SDK-driver) execution model #1486 (Copilot sidecar SDK-driver proposal) and feat: support reusable cross-repository custom safe-output jobs #1473 (reusable cross-repo custom safe-output jobs) are already under [Parent] MCPG infrastructure and safe-output tooling improvements #1321; proposal: adopt Copilot sidecar (SDK-driver) execution model #1486 is a broader architectural proposal that could warrant its own parent if more implementation sub-tasks emerge.
• feat: built-in PR context precomputation for PR-triggered agents #860 (built-in PR context precomputation) appears largely implemented (exec-context-pr exists in the codebase); consider closing if complete.
• feat: align FrontMatter fields with gh-aw schema — run-name, labels, metadata, tracker-id, source, strict #451 (align FrontMatter fields with gh-aw schema) and feat: decouple prompt body from compiled pipeline output (runtime-import approach) #237 (decouple prompt body via runtime-import) are both under [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 — they could also form a dedicated "gh-aw schema alignment" parent if new sub-tasks emerge.
• 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 chores) are a recurring pattern (3 issues, below the 5-issue threshold) — consider a parent if the pattern continues.

Observations

• The backlog is well-structured with most clusters already having parents ([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] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286, [Parent] MCPG infrastructure and safe-output tooling improvements #1321, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283, [Parent] Safe-output executor E2E test coverage and tool correctness #1428).
• The main gap was 8 recent agentic-workflow failure issues not yet linked to their respective tracking parents.
• The [aw]-prefixed auto-generated failure issues accumulate quickly — the two failure-tracking parents ([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) are doing useful triage work.
• [aw] Detection Runs #793 and [aw] No-Op Runs #13 are long-lived no-op/detection-run tracking issues with no obvious parent; they appear to be operational sinks rather than feature work.

Generated by Issue Arborist · 36.4 AIC · ⌖ 6 AIC · ⊞ 6K · ◷

• expires on Jul 24, 2026, 8:41 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1570.