aos-cli release fails: check-aos-release.sh still launches a warded director without work text #1045

Closed
opened 2026-08-13 18:41:39 +00:00 by coilyco-ops · 0 comments
Owner

What happens

The release workflow run for aos-v* fails at ward exec aos-release-check:

ward: exec aos-release-check in /workspace/coilyco-flight-deck/agentic-os
...
aosward: --warded role director needs work text
exit status 1
Job 'release' failed

Failing run: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/3285 (job release, head bf2f66ed).

Cause

refactor(aos): drop the director/engineer/qa and kubeconfig carve-outs (#1040) made every warded role require work text and made buildWardLaunchPlan always emit ward agent run --role <role>. That PR updated aos-cli/composition_test.go, aos-cli/launch_test.go, and the docs, but not scripts/check-aos-release.sh, which still asserts the retired shape:

  • it launches aosward --agent codex --role director --image agentic-os:test --dry-run with no trailing work text, which validateIntegratedLaunch now rejects
  • it then greps the plan for ward agent director, the fixed-lane spelling buildWardLaunchPlan no longer emits

The first of those is the observed failure. The second would fail on the next line once the launch succeeds.

Reproduction

$ ./dist/aosward-darwin-arm64 --agent codex --role director --image agentic-os:test --dry-run
aosward: --warded role director needs work text

With work text appended, the plan renders and carries the new lane:

ward agent run --role director 'aos release smoke' --agent codex --image agentic-os:test --context-bundle '<AOS_CONTEXT_BUNDLE>'

Fix

Pass work text to the smoke launch and assert ward agent run --role director instead of ward agent director.

Scope note

CI is otherwise green. ci.yml, promote.yml, and mirror-to-github.yml all passed on the same commit. This is the only failing workflow.

## What happens The `release` workflow run for `aos-v*` fails at `ward exec aos-release-check`: ``` ward: exec aos-release-check in /workspace/coilyco-flight-deck/agentic-os ... aosward: --warded role director needs work text exit status 1 Job 'release' failed ``` Failing run: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/actions/runs/3285 (job `release`, head `bf2f66ed`). ## Cause `refactor(aos): drop the director/engineer/qa and kubeconfig carve-outs (#1040)` made every warded role require work text and made `buildWardLaunchPlan` always emit `ward agent run --role <role>`. That PR updated `aos-cli/composition_test.go`, `aos-cli/launch_test.go`, and the docs, but not `scripts/check-aos-release.sh`, which still asserts the retired shape: * it launches `aosward --agent codex --role director --image agentic-os:test --dry-run` with no trailing work text, which `validateIntegratedLaunch` now rejects * it then greps the plan for `ward agent director`, the fixed-lane spelling `buildWardLaunchPlan` no longer emits The first of those is the observed failure. The second would fail on the next line once the launch succeeds. ## Reproduction ``` $ ./dist/aosward-darwin-arm64 --agent codex --role director --image agentic-os:test --dry-run aosward: --warded role director needs work text ``` With work text appended, the plan renders and carries the new lane: ``` ward agent run --role director 'aos release smoke' --agent codex --image agentic-os:test --context-bundle '<AOS_CONTEXT_BUNDLE>' ``` ## Fix Pass work text to the smoke launch and assert `ward agent run --role director` instead of `ward agent director`. ## Scope note CI is otherwise green. `ci.yml`, `promote.yml`, and `mirror-to-github.yml` all passed on the same commit. This is the only failing workflow.
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#1045
No description provided.