[aw] Analyze CI Failure failed

### Workflow Failure

**Workflow:** [Analyze CI Failure](https://github.com/microsoft/aspire/blob/main/.github/workflows/analyze-ci-failure.md)
**Branch:** main
**Run:** https://github.com/microsoft/aspire/actions/runs/31990551738

> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated before producing output.

The engine exited immediately without producing any output. This often indicates a transient infrastructure issue (e.g., service unavailable, API rate limiting). If this failure recurs, check the GitHub Copilot status page and review the firewall audit logs.

### Action Required

**Assign this issue to an agent** to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/microsoft/aspire/actions/runs/31990551738
````

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.

- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow analyze-ci-failure failure in https://github.com/microsoft/aspire/actions/runs/31990551738`

> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>

> Generated from [Analyze CI Failure](https://github.com/microsoft/aspire/actions/runs/31990551738) · [◷](https://github.com/search?q=repo%3Amicrosoft%2Faspire+is%3Aissue+%22gh-aw-workflow-id%3A+analyze-ci-failure%22&type=issues)
> - [x] expires on Aug 24, 2026, 3:18 AM UTC

Start with the failed run 31990551738 and the workflow documentation at .github/workflows/analyze-ci-failure.md. Read .github/skills/agentic-workflows/SKILL.md or the linked debugging guide, then determine why the copilot engine exited without output. Done means the workflow failure is diagnosed and fixed, or its failure reporting is intentionally disabled if appropriate.

Written by the indexing model from the issue text.