build(dev-base): take agent-compose 2.51.0, carrying the seat retitles #1239
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!1239
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/vu59-dev-base-agent-compose-251"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The pin sat at
2.47.0, past the Core Roster reflow but before agent-compose#344. So every warded container, CI job, and downstream bake still composedOlaf,Lucia,Saiyaand the old titles, while the release carryingVera,Evie,Portia(v2.50.0, published today) reached nothing running.2.51.0rather than2.50.0because it is the current release. Alongside the retitles it carries the tpm gate's close and revert exits (#327), the tpm execution-limit wording (#328), and--nestedlaunch.The roster shape does not move: still seven roles and ten personalities, so
verify-common.sh's counters stay as they are. One ARG line.uv run pytest tests/test_dev_base_image.pygreen (11 passed), hooks green.This unblocks coilyco-gaming/sirens-echo#1155, whose tracked role records can only be regenerated once the image carries this release.
Refs coilyco-flight-deck/agent-compose#344