[Issue Arborist] Run summary — 21 links added across 3 existing parents

[github-actions[bot]]

🌳 Issue Arborist Report

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

Parent issues created

None — no orphan cluster of 5+ unparented issues was found this run; all clear clusters already had an established parent.

Links created

Parent	Sub-issue	Reasoning
#1535	#1897	AI-credits rate-limit incident (Dependency Version Updater) — matches parent's exact theme
#1535	#1893	AI-credits rate-limit incident (Issue Triage)
#1535	#1884	AI-credits rate-limit incident (Issue Arborist)
#1549	#1907	Test Quality Sentinel workflow failure — non-rate-limit execution failure
#1549	#1906	TypeScript Code Quality Reviewer failure
#1549	#1905	Compiler Contract Reviewer failure
#1549	#1904	PR Security Reviewer failure
#1549	#1903	Docs Writer failure
#1549	#1902	Issue Triage failure
#1549	#1900	Agent Documentation Maintainer failure
#1549	#1894	Clippy Fixer failure
#1549	#1892	Red Team Security Auditor failure
#1549	#1891	Issue Arborist failure
#1549	#1890	Agent Documentation Maintainer failure
#1549	#1889	Test Reducer failure
#1549	#1888	Bash Step Hygiene Auditor failure
#1549	#1887	Dependency Version Updater failure
#1549	#1885	Issue Triage failure
#1286	#1834	refactor(engine): emit typed install steps instead of YAML strings — compiler internals/typed-IR/YAML-gen theme, same as parent's tracked issues
#1286	#1835	refactor(mcpg): type container runtime arguments and mounts — same theme, spawned from same PR #1824 review as #1834
#1428	#1798	test(executor-e2e): add create-github-issue and set-github-issue-type scenarios — safe-output executor E2E coverage gap matching parent's scope (note: this issue was already showing under the parent's sub-issue list at read time; link call was a no-op/idempotent confirmation)

Suggested (not linked — for maintainer review)

• Docs-drift cluster: docs: conclusion job token reference omits SC_WRITE_TOKEN #1766, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763, docs: fix AGENTS.md accuracy — add trigger-e2e to ado-script tree and export-fact-catalog to CLI index #1583, docs(site): refresh IR typed-helper docs to builder-struct API #1192 all touch documentation accuracy/staleness, but only 4 issues — below the 5-issue threshold for a new parent, and no existing docs umbrella parent was found.
• chore(security): minimize AWF agent environment and mask unused gh CLI #1818 (security: minimize AWF agent environment) and Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 (Proxy Stage 1 ADO reads) are both security-hardening but different enough in scope (agent env vs. token exposure) that I didn't link them together.

Observations

• Two long-running failure-tracking parents ([Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535 for rate-limit incidents, [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 for other execution failures) are the project's dominant backlog-organization pattern for [aw] auto-filed workflow-failure issues; both had accumulated several newly-filed, unlinked incidents that fit their exact existing scope.
• [Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 (compiler internals) continues to absorb refactor issues spawned from PR review threads (feat(ado-proxy): add credential-isolated Azure DevOps reads #1824 in this case) — worth keeping an eye on as a recurring source pattern.
• No new 5+ orphan cluster met the conservative bar for creating a new parent this run.

Generated by Issue Arborist · auto · 60.6 AIC · ⌖ 2.48 AIC · ⊞ 9.7K · ◷

• expires on Aug 21, 2026, 8:38 PM UTC

[github-actions[bot]]

This discussion has been marked as outdated by Issue Arborist.

A newer discussion is available at Discussion #1919.