[aw] PR Documentation Check hit engine rate limit (HTTP 429)

### Workflow Failure

**Workflow:** [PR Documentation Check](https://github.com/microsoft/aspire/blob/main/.github/workflows/pr-docs-check.md)
**Branch:** ellahathaway-deno-debugger-failure
**Run:** https://github.com/microsoft/aspire/actions/runs/34740434228

> [!WARNING]
> **Engine Rate Limited (HTTP 429)**: The `copilot` engine hit provider rate limits and could not complete this run.

This signal was detected from engine runtime logs/OTLP telemetry.

**What to do next**
- Retry the workflow after a short delay.
- If this keeps happening, reduce concurrent workflow volume or review provider quota/rate-limit policies.

### 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/34740434228
````

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 pr-docs-check failure in https://github.com/microsoft/aspire/actions/runs/34740434228`

> [!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 [PR Documentation Check](https://github.com/microsoft/aspire/actions/runs/34740434228) · 143.2 AIC · [◷](https://github.com/search?q=repo%3Amicrosoft%2Faspire+is%3Aissue+%22gh-aw-workflow-id%3A+pr-docs-check%22&type=issues)
> - [x] expires on Sep 20, 2026, 5:45 AM UTC

Start with the failed run linked in the issue and inspect its engine runtime logs or OTLP telemetry for the HTTP 429. Read .github/workflows/pr-docs-check.md to understand the workflow configuration, then retry after a short delay and check whether the failure recurs. Done means the workflow completes successfully or the repository has a documented, validated change addressing the recurring rate limit.

Written by the indexing model from the issue text.