Repository navigation
[AW Top 10] 05 Harden AWF binary installation startup step #76174
Description
Priority 5/10 | 5 source issues | Impact 4/5 | Confidence 3/5 | Effort 2/5
One assignment, one coherent fix
Several workflows fail at the Install AWF binary step before the agent starts, including Windows probes and main-branch daily workflows.
Implementation scope
Make the compiler-generated AWF install step retry transient download failures, verify checksums, and emit the underlying error text in failure diagnostics. Route Windows installs through the supported shell path.
Done when
- The install step retries transient download failures and prints the failing command output.
- A regression test covers the generated install step for Linux and Windows lock files.
Why now
Four runs on pull requests and main failed at the same step with no captured engine error, so the whole fleet is exposed. The exact root cause is unverified because logs were not captured, so diagnostics come first.
AW source issues and corroborating reports
#76145 #76146 #76147 #74815 #74817
No corroborating AW discussion; evidence comes from the source issues.
Unchanged AW sources close only after this summary is completed. Newer source activity and not-planned retirement do not trigger source closure. Assigned summaries are frozen; unassign to allow reclustering.
Generated by AW Essential Issue Clustering · copilot · auto · ~31 AIC · ⌖ ~2 AIC · ⊞ 9.7K · ◷
Activity
github-actions commentedon Nov 9, 2026
🍪 Issue Monster selected this for Copilot
I've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.
If assignment succeeds, Copilot will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪