[aw] CI Outer-Loop Failure Scanner failed

### Workflow Failure

**Workflow:** [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/blob/main/.github/workflows/ci-failure-scan.md)
**Branch:** main
**Run:** https://github.com/dotnet/runtime/actions/runs/33702401528

> [!WARNING]
> **Engine Failure**: The `copilot` engine terminated unexpectedly.

**Last agent output:**
```
Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes +0 -0
Duration 19m 20s
Tokens ↑ 1.8m (1.7m cached) • ↓ 9.9k
Resume copilot --resume=e21316d7-747f-4c8b-b799-f7471c46b90f
Authentication failed with provider at http://172.30.0.30:10002 (HTTP 403).
Check your COPILOT_PROVIDER_API_KEY or COPILOT_PROVIDER_BEARER_TOKEN.
Changes +0 -0
Duration 1s
Resume copilot --resume=ae51426c-d50b-484f-a934-a7ba6f4fd210
```

### 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/dotnet/runtime/actions/runs/33702401528
````

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 ci-failure-scan failure in https://github.com/dotnet/runtime/actions/runs/33702401528`

> [!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 [CI Outer-Loop Failure Scanner](https://github.com/dotnet/runtime/actions/runs/33702401528) · 993.1 AIC · [◷](https://github.com/search?q=repo%3Adotnet%2Fruntime+is%3Aissue+%22gh-aw-workflow-id%3A+ci-failure-scan%22&type=issues)

Start with .github/workflows/ci-failure-scan.md and the failed run linked in the issue. Inspect the copilot provider authentication failure and the workflow's failure-reporting configuration; done means the scanner completes without the HTTP 403 engine failure or correctly handles the failure.

Written by the indexing model from the issue text.