[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:** joperezr-merge-release-13-5-to-main
**Run:** https://github.com/microsoft/aspire/actions/runs/34413950706

> [!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/34413950706
````

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/34413950706`

> [!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/34413950706) · 147.7 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 16, 2026, 11:03 PM UTC

Start with .github/workflows/pr-docs-check.md and the failed run 34413950706, then read the agentic-workflows guidance in .github/skills/agentic-workflows/SKILL.md or debug.md. Inspect the workflow logs and determine whether the recurring HTTP 429 requires a workflow change, provider or concurrency investigation, or only different failure reporting; done means the workflow no longer fails unexpectedly under the intended rate-limit behavior.

Written by the indexing model from the issue text.