[Issue Arborist] Issue Arborist run - no confident links this cycle

[github-actions[bot]]

🌳 Issue Arborist Report

Issues analyzed: 59

Parent issues created

None this run — no orphan cluster of 5+ unparented issues sharing a clear theme was found.

Links created

None this run — no unambiguous parent/child relationship met the confidence bar.

Suggested (not linked — for maintainer review)

• chore(security): minimize AWF agent environment and mask unused gh CLI #1818 (chore(security): minimize AWF agent environment and mask gh CLI) shares infra/security themes with Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 (Proxy Stage 1 ADO reads) but scopes different concerns (env/token plumbing vs read-token exposure) — not clearly parent/child.
• [agent-issue]: create-pull-request cannot target a repository from another Azure DevOps organisation #1934 (create-pull-request cross-org targeting) and Proxy Stage 1 Azure DevOps reads without exposing SC_READ_TOKEN #1652 (ado-proxy token exposure) both touch cross-repo/cross-org credential handling in the safe-output executor, but are separate root causes — left unlinked.
• docs: conclusion job token reference omits SC_WRITE_TOKEN #1766, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763 (docs-accuracy fixes) are small standalone doc fixes; only 2 exist currently, below the 5+ cluster threshold.
• 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 per release) form a recurring theme but only 3 open instances exist — below the 5+ threshold for a new parent.
• [agent-issue]: support weekday-only fuzzy schedules and cron parity #1965, [agent-issue]: Gateway-managed, auto-refreshed Azure federated token file for user-defined MCP servers #1964, [agent-issue]: create-pull-request cannot target a repository from another Azure DevOps organisation #1934 (agent-issue bug/feature reports) share the [agent-issue] intake template but cover unrelated technical areas (schedules, MCP token refresh, cross-org PRs) — only 3, not thematically unified enough to group.

Observations

• Most substantive open issues are already organized under existing parents ([Parent] Compiler internals and pipeline generation improvements (IR types, YAML gen, prompt decoupling) #1286 compiler internals, [Parent] MCPG infrastructure and safe-output tooling improvements #1321 MCPG/safe-outputs, [Parent] Safe-output executor E2E test coverage and tool correctness #1428 executor E2E, [Parent] Track agent runtime and execution pipeline improvements #1649 agent runtime, [Parent] Track and resolve recurring AI-credits rate-limit failures in scheduled agentic workflows #1535 rate-limit incidents, [Parent] Track and resolve recurring agentic workflow execution failures (non-rate-limit) #1549 non-rate-limit failures, [Parent] Track and act on upstream dependency release-note action items (awf, mcpg, copilot-cli) #1283 dependency release-notes), so the backlog is already well-triaged.
• Remaining unparented issues ([agent-issue]: support weekday-only fuzzy schedules and cron parity #1965, [agent-issue]: Gateway-managed, auto-refreshed Azure federated token file for user-defined MCP servers #1964, [agent-issue]: create-pull-request cannot target a repository from another Azure DevOps organisation #1934, fix(smoke): route multi-repo Cargo through the internal feed #1823, test(audit): add end-to-end integration suites for audit and debug commands #1819, chore(security): minimize AWF agent environment and mask unused gh CLI #1818, test(smoke): report scheduled smoke failures as GitHub issues from the orchestrator #1796, docs: conclusion job token reference omits SC_WRITE_TOKEN #1766, docs(prompts): use repo-relative paths instead of hardcoded absolute checkout paths #1763, feat: allow enable to target individual pipeline files #1634, Feature request: first-class TLA+ / TLC (Java) runtime support #1222, 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) are either singletons, small (<5) same-theme groups, or standalone meta-tracking issues ([aw] No-Op Runs #13, [aw] Detection Runs #793, [Parent] Issue Arborist - Issue Group #1284) that intentionally have no parent.
• No new parent issues were created and no links were made this run to avoid low-confidence groupings; revisit once any sub-5 cluster (fixture recompiles, docs-accuracy, agent-issue intake) grows to 5+.

Generated by Issue Arborist · auto · 57.7 AIC · ⌖ 1.81 AIC · ⊞ 9.7K · ◷

• expires on Aug 28, 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 #1985.