[aw-maintenance:failures-investigator] Failure Report: githubnext/gh-aw-workshop (last 24h)

- **Target repository**: `githubnext/gh-aw-workshop`
- **Window**: last 24 hours (from 2026-09-02T23:44:28Z)
- **Failed agentic runs**: 41
- **Failure buckets**: 1 (P0: 1, P1: 0, P2: 0)
- **Agentic workflows in repository**: 22

### Failure Buckets

| Severity | Workflow | Error signature | Runs | Tracking |
|---|---|---|---|---|
| P0 | All agentic workflows (`Workshop Builder`, `Workflow Skills Editor`, `Workshop Link Checker`, others) | `##[error]Blocked compile-agentic version: v0.82.13 is in the blocked versions list. Update gh-aw to the latest version and recompile your workflow.` at activation job step "Check compile-agentic version" | 41 (all failed runs in window; 5 sampled, all identical) | new issue |

### Resolved Buckets

none

Evidence

Every one of the 5 sampled failures (`33815258690`, `33810480125`, `33807856135`, `33807178518`, `33805019420`) fails in the `activation` job at step `Check compile-agentic version`, with identical error text:

```
##[error]Blocked compile-agentic version: v0.82.13 is in the blocked versions list. Update gh-aw to the latest version and recompile your workflow.
```

This is a startup-time version gate implemented in the activation job's github-script step (`check_version_updates.cjs`), which fetches a compat/allow-list config from `https://raw.githubusercontent.com/github/gh-aw-actions/main/.github/aw/compat.json` and fails the run before the agent job even starts. Representative run: https://github.com/githubnext/gh-aw-workshop/actions/runs/33815258690

Because this check runs in every workflow's activation job before agent execution, it blocks **every** agentic workflow run in the target repository compiled with `gh-aw` `v0.82.13`, regardless of workflow content — this is why the failure count (41) roughly matches all recent runs across multiple distinct workflow files.

### Next Steps

1. (P0) Update `gh-aw` to a non-blocked version in `githubnext/gh-aw-workshop` and recompile all `.lock.yml` workflow files (see fix issue).
2. Re-run one workflow after the update to confirm the activation job's version check passes.
3. Consider adding CI/dependency-update automation in the target repo to prevent gh-aw from drifting onto a blocked version again.

### Control Plane
- Correlation ID: 33818396937-30
- Central repository: githubnext/gh-aw-cao
- Control plane run URL: https://github.com/githubnext/gh-aw-cao/actions/runs/33818396937

> Generated by [:rotating_light: AW Maintenance / Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33818777613) · copilot · auto · 35 AIC · ⌖ 10.5 AIC · ⊞ 14.9K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Faw-failures-investigator%22&type=issues)
> - [x] expires on Sep 17, 2026, 11:49 PM UTC

Start with the target repository githubnext/gh-aw-workshop and inspect its compiled .lock.yml workflow files and the activation job that runs check_version_updates.cjs. Update gh-aw as described, recompile all affected workflows, then rerun one workflow and confirm the version-check step passes without the blocked-version error.

Written by the indexing model from the issue text.