Make the AOS release build work under Ward on Windows #743

Closed
opened 2026-07-25 14:06:02 +00:00 by coilyco-ops · 1 comment
Owner

Problem

On Windows, ward exec aos-release-build fails during the pinned specgen download with curl error 23. The identical Git curl download, including the retry flags, succeeds outside the Ward process environment.

PR #733 normalized CRLF shell inputs, Windows asset suffixes, and checksum output. The failure still occurs before specgen compilation begins. Linux PR CI is green, so this does not block the supported release runner.

Evidence

  • The Ward release verb retries the write and returns curl error 23.
  • A direct download to the same workspace volume succeeds.
  • Focused Aguard and release tests pass on Windows.
  • Shellcheck and the documentation-layout hook pass.
  • Forgejo CI passes 593 tests, full pre-commit, and Ward doctor on Linux.

Acceptance

  • ward exec aos-release-build completes on Windows from a clean synchronized checkout.
  • The build downloads and verifies the pinned Windows specgen asset through the Ward process environment.
  • The release check smokes the native Aguard wrapper from an empty directory.
  • Linux release behavior remains unchanged.
## Problem On Windows, `ward exec aos-release-build` fails during the pinned specgen download with curl error 23. The identical Git curl download, including the retry flags, succeeds outside the Ward process environment. PR #733 normalized CRLF shell inputs, Windows asset suffixes, and checksum output. The failure still occurs before specgen compilation begins. Linux PR CI is green, so this does not block the supported release runner. ## Evidence * The Ward release verb retries the write and returns curl error 23. * A direct download to the same workspace volume succeeds. * Focused Aguard and release tests pass on Windows. * Shellcheck and the documentation-layout hook pass. * Forgejo CI passes 593 tests, full pre-commit, and Ward doctor on Linux. ## Acceptance * `ward exec aos-release-build` completes on Windows from a clean synchronized checkout. * The build downloads and verifies the pinned Windows specgen asset through the Ward process environment. * The release check smokes the native Aguard wrapper from an empty directory. * Linux release behavior remains unchanged.
Author
Owner

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901).

This issue carried priority/P4, the icebox tier, meaning it had already been judged parked rather than planned. The burn-down changed what an open issue means: the tracker now holds work that is actually on the list, and the icebox lives in closed state instead of at the bottom of open.

Nothing here was judged wrong or worthless. If this becomes live work, reopen it. The whole set is recoverable with state:closed label:burndown-2026-08.

Closed in the 2026-08-26 backlog burn-down (coilyco-bridge/agentic-os-kai#901). This issue carried `priority/P4`, the icebox tier, meaning it had already been judged parked rather than planned. The burn-down changed what an open issue means: the tracker now holds work that is actually on the list, and the icebox lives in closed state instead of at the bottom of open. Nothing here was judged wrong or worthless. If this becomes live work, reopen it. The whole set is recoverable with `state:closed label:burndown-2026-08`.
coilyco-ops 2026-08-27 02:57:54 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agentic-os#743
No description provided.