Process completed with exit code 22.\\n ```\\n4. The agent step never runs. The failure handler posts an extremely terse comment to the existing failure issue (no diagnostics).\\n\\n## Root cause\\n\\n`github/gh-aw-firewall` has a release gap: tags `v0.25.21` through `v0.25.39` do not exist on the releases endpoint:\\n\\n```\\n$ gh api repos/github/gh-aw-firewall/releases --jq \\u0026#39;.[].tag_name\\u0026#39; | sort -V\\n… v0.25.18, v0.25.19, v0.25.20, v0.25.40, v0.25.41, v0.25.42 …\\n```\\n\\nIt looks like one or more releases in that range were deleted (or never published after a version bump in the `gh-aw` compiler). Any compiled workflow that captured a tag in the gap is now permanently broken until either:\\n- the workflow is recompiled against a newer `gh-aw` (manual action by every user), **or**\\n- the missing releases are re‑published.\\n\\n`install_awf_binary.sh` has no fallback path: it `set -e` exits as soon as the checksum download 404s.\\n\\n## Affected runs (microsoft/aspire `pr-docs-check`, all pinned `awf v0.25.28`)\\n\\n15 runs in the last ~12 days:\\n\\n| Run | Date (UTC) |\\n|---|---|\\n| [25467588686](https://github.com/microsoft/aspire/actions/runs/25467588686) | 2026‑05‑06 |\\n| [25476576962](https://github.com/microsoft/aspire/actions/runs/25476576962) | 2026‑05‑07 |\\n| [25480215464](https://github.com/microsoft/aspire/actions/runs/25480215464) | 2026‑05‑07 |\\n| [25503081313](https://github.com/microsoft/aspire/actions/runs/25503081313) | 2026‑05‑07 |\\n| [25506161577](https://github.com/microsoft/aspire/actions/runs/25506161577) | 2026‑05‑07 |\\n| [25699326056](https://github.com/microsoft/aspire/actions/runs/25699326056) | 2026‑05‑11 |\\n| [25699293489](https://github.com/microsoft/aspire/actions/runs/25699293489) | 2026‑05‑11 |\\n| [25699559470](https://github.com/microsoft/aspire/actions/runs/25699559470) | 2026‑05‑11 |\\n| [25826083607](https://github.com/microsoft/aspire/actions/runs/25826083607) | 2026‑05‑13 |\\n| [25831283389](https://github.com/microsoft/aspire/actions/runs/25831283389) | 2026‑05‑13 |\\n| [25879145495](https://github.com/microsoft/aspire/actions/runs/25879145495) | 2026‑05‑14 |\\n| [25879025905](https://github.com/microsoft/aspire/actions/runs/25879025905) | 2026‑05‑14 |\\n| [25883720698](https://github.com/microsoft/aspire/actions/runs/25883720698) | 2026‑05‑14 |\\n| [25885698482](https://github.com/microsoft/aspire/actions/runs/25885698482) | 2026‑05‑14 |\\n| [25996129485](https://github.com/microsoft/aspire/actions/runs/25996129485) | 2026‑05‑17 |\\n\\nAll 15 surface as the same generic failure comment on `microsoft/aspire#16138` because of the failure‑issue aggregation bug already filed as #33060.\\n\\n## Suggested fixes (any one or combination)\\n\\n1. **Re‑publish the missing releases** (`v0.25.21`–`v0.25.39`) on `github/gh-aw-firewall` so existing compiled workflows can install. This is the cheapest fix and unblocks every existing compiled workflow.\\n2. **Make `install_awf_binary.sh` fallback to a known-good version** when the pinned tag 404s. The script could:\\n - Probe `releases/latest` and use that if the pinned version 404s, **or**\\n - Have a hard‑coded minimum/maximum fallback list.\\n3. **Validate the pinned version exists at compile time** in `gh-aw` so we never embed a missing tag into a `.lock.yml`.\\n4. **Improve the failure surface**: when `install_awf_binary.sh` fails (or any pre‑agent step fails), the downstream failure handler should include the underlying error (`curl: (22) ...`) rather than emitting a bare \\u0026#34;Agent job failed.\\u0026#34; comment.\\n\\n## Workaround for affected users\\n\\nRecompile workflows against `gh-aw v0.72.0` or newer:\\n\\n```bash\\ngh extension upgrade github/gh-aw\\ngh aw compile\\ngit commit -am \\u0026#34;Recompile workflows for newer awf\\u0026#34;\\n```\\n\\n(But this needs to be done by every consumer; the fundamental gap in published releases is what makes the problem widespread.)\\n\\n## Environment\\n\\n- `gh-aw` compile