[WIP] Triage around 74 weekly agent-run-failure issues

[Copilot]

• Create aw-failure label in the GitHub repository
• Add aw-failure label constant to handle_agent_failure.cjs and include it in all new failure issue creation
• Update auto-triage-issues.md to recognize [aw] ... failed pattern issues and apply aw-failure label
• Update tests in handle_agent_failure.test.cjs to assert the aw-failure label is added to new failure issues
• Recompile workflows and run make agent-report-progress

[github-actions]

Hey @Copilot 👋 — thanks for picking up the issue-triage task! Keeping the signal-to-noise ratio healthy in the issue tracker is genuinely useful work. A few things to address before this is ready for review:

• Update the description — the PR body is still the auto-generated Copilot placeholder. Once work is complete, please replace it with a summary of what was actually done: which labels were applied, how many issues were tagged, whether the rollup tracking issue was created, and any decisions made (e.g. what label name was chosen for recurring [aw] failures).
• No file changes present — this is a WIP draft with 0 additions and 0 deletions. That's expected if work is still in progress, but if the triage was performed via API calls rather than file edits, the description should document that explicitly so reviewers understand the PR's impact.
• Scope signal — the CONTRIBUTING.md is focused on code/feature contributions; pure issue-management PRs don't have a clearly defined home in the process. A brief note in the body confirming this was triggered by the Deep Report automated pipeline (referencing the workflow run) would help reviewers understand the provenance.

If you'd like a hand wrapping this up, you can assign this prompt to your coding agent:

Update the description of PR github/gh-aw#43357 once the triage is complete.
The updated body should include:
1. A summary of what was done: which label(s) were created/applied to the ~74 [aw] agent-run-failure issues.
2. Confirmation that issue #42874 was labeled `bug` and assigned for investigation.
3. Whether a rollup/dedup tracking issue was opened for recurring [aw] failures.
4. A note that this PR was triggered by the Deep Report pipeline (link to the workflow run).
Replace the current placeholder body entirely with this factual summary.

Generated by ✅ Contribution Check · 165.9 AIC · ⌖ 29.5 AIC · ⊞ 6.3K · ◷