Verify the v2 AOS convergence boundary on real host classes #699
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/infrastructure#699
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Follow-up verification for infrastructure #694 and #697, required by agent-compose #142. The implementation is locally validated and landed, but the engineer run did not mutate or iterate against live hosts. An operator or director must follow docs/ansible-aos-native-role.md on one client-class host and one server-class host. Record: the pinned AOS 0.140.0 and paired Aguard versions; first check/apply outcome; a second check showing current idempotent state; catalogue manifest creation; client native Claude and Codex MCP projection; server mcporter fallback without native projection; and absence of the retired Agent Compose MCP mutation path. Do not include raw inventory payloads or secrets. Return the exact run evidence to agent-compose #142 before v2.0.0 dispatch.
Closing as unnecessary release ceremony for Agent Compose v2. Kai exercises the steady-state native Agent Compose path repeatedly in normal use, and no live convergence defect is known. The remaining fresh-host and server-class checklist is not required as a v2 release gate. Infrastructure retains the committed rollout and rollback runbook if a future host-specific failure needs targeted verification.