build(dev-base): agent-compose 2.32.0, for boundary-omit #1139

Merged

coilysiren merged 1 commit from build/agent-compose-2.32.0 into main

2026-08-19 02:41:10 +00:00

coilyco-ops commented

2026-08-19 02:25:06 +00:00

Member

Step 2 of the agent-compose#304 chain. One line.

agent-compose v2.32.0 shipped agent-compose#310, which adds the boundary-omit request node. The image still pins 2.31.0, and 2.31.0 rejects it:

agent-compose: request request.engineer.kdl: unknown node "boundary-omit"

That single error is what both of sirens-echo#1018's jobs fail on right now, image-build and role-drift-check alike. This bump is the whole fix for both.

Why verify-common still passes

verify-common.sh asserts roster shape rather than a version:

expect_roster '.source' 'roster:core'
expect_roster '.role_order | length' 8
expect_roster '.personalities | length' 18

2.32.0 changes the request parser and the resolver's boundary handling. It adds no role and no personality, so all three hold. Worth stating because the last pin bump here broke on exactly this assertion when the roster went 16 to 18.

After this

dev-base-publish republishes agentic-os:release, and then sirens-echo#1018 can merge and build. Nothing else in the chain is waiting on anything.

Step 2 of the agent-compose#304 chain. One line. agent-compose [v2.32.0](https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/releases/tag/v2.32.0) shipped agent-compose#310, which adds the `boundary-omit` request node. The image still pins 2.31.0, and 2.31.0 rejects it: ``` agent-compose: request request.engineer.kdl: unknown node "boundary-omit" ``` That single error is what both of sirens-echo#1018's jobs fail on right now, `image-build` and `role-drift-check` alike. This bump is the whole fix for both. ## Why verify-common still passes `verify-common.sh` asserts roster shape rather than a version: ``` expect_roster '.source' 'roster:core' expect_roster '.role_order | length' 8 expect_roster '.personalities | length' 18 ``` 2.32.0 changes the request parser and the resolver's boundary handling. It adds no role and no personality, so all three hold. Worth stating because the last pin bump here broke on exactly this assertion when the roster went 16 to 18. ## After this `dev-base-publish` republishes `agentic-os:release`, and then sirens-echo#1018 can merge and build. Nothing else in the chain is waiting on anything.

coilyco-ops added 1 commit

2026-08-19 02:25:06 +00:00

build(dev-base): agent-compose 2.32.0, for boundary-omit

ci / aos-eval-tests (pull_request) Successful in 5s

Details

ci / ward-doctor (pull_request) Successful in 13s

Details

ci / aos-cli-tests (pull_request) Successful in 20s

Details

ci / gate (pull_request) Successful in 53s

Details

dev-base-pr / build (pull_request) Successful in 12m5s

Details

bc8acc86a5

2.31.0 rejects the boundary-omit node with "unknown node", which is what
sirens-echo's image build and role-drift-check both fail on today. The
roster is unchanged at 8 roles and 18 personalities, so verify-common's
assertions hold.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-19 02:25:06 +00:00