[deep-report] Bulk-close resolved [aw] failure issues from Apr 8–9 Copilot v1.0.21 outage

[github-actions]

There are currently 63 open [aw] ... failed issues — a record high. The majority were opened during the Apr 8–9 Copilot CLI v1.0.21 silent startup crash that caused 124 Copilot-engine workflows to fail with exit code 1 and zero output. With v1.0.22 now deployed and Copilot recovering (session completion rate 8% → 18% today), most of these failure issues are no longer actionable.

An agent should:

1. Enumerate all open [aw] * failed issues
2. For each issue, check the most recent run of the referenced workflow
3. Close issues where the workflow has since run successfully with a comment: "Resolved — workflow ran successfully after Copilot CLI v1.0.22 upgrade."
4. Leave open any issues where the workflow continues to fail for a different root cause

Expected Impact

Reduces open [aw] failure noise from ~63 to a manageable ~10–15 genuinely broken workflows, making the failure signal actionable again.

Suggested Agent

Codex or Claude engine — Use GitHub MCP to enumerate issues (filter by agentic-workflows label), query workflow run history per issue, then batch-close resolved ones via safe-outputs update_issue.

Estimated Effort

Medium (1–4 hours) — requires looping over ~63 issues and checking corresponding workflow run status.

Data Source

[DeepReport Intelligence Briefing — April 10, 2026] | Agent Performance Report — Week of 2026-04-10 | Issue #25468 (outage tracker)

Generated by DeepReport - Intelligence Gathering Agent · ● 368.7K · ◷

• expires on Apr 12, 2026, 3:04 PM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ● 218.5K · ◷