Retire the Python agent-compose generator in favor of the Go cascade #618

New issue

Closed

opened 2026-07-23 00:15:24 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-23 00:15:24 +00:00

Member

Context

agent-compose v0.2.0 absorbed the v1 composer: agent-compose cascade (agent-compose#23) reproduces generate_agent_compose.py byte-for-byte on shared fixtures - COMPOSED slices, load-point symlinks, and the mount-eligibility manifest ward reads. The Python generator is now redundant everywhere the Go binary is installed (brew tap, scoop bucket, and Forgejo release binaries all exist).

What to do

Repoint the check-agent-compose-drift pre-commit hook at agent-compose cascade --check (binary presence becomes the hook's dependency instead of the agentic_os package).
Fleet cutover via infrastructure: hosts run agent-compose cascade where they ran generate-agent-compose (Ansible/SessionStart freshen hooks); confirm the mount-eligibility manifest keeps flowing to ward uninterrupted.
Special-case Kai's workstation: its COMPOSED.* snapshots carry hand edits (per the 2026-07-01 note in its agent-compose.yaml) that must be reconciled into source files before the first native cascade run, or they will be regenerated away.
Remove agentic_os/generators/generate_agent_compose.py, its console entry points (generate-agent-compose, check-agent-compose-drift's Python path), and tests/test_agent_compose.py once no host or hook references them.
Keep check-agent-compose-size / check-agent-compose-dedup / check-context-budget: they validate content, not composition, and are untouched by the absorption.

Sequencing

Hook repoint and fleet cutover can run in either order but both precede removal. The workstation reconciliation is HITL and independent.

References

agent-compose#23 (absorption, cross-check record)
agent-compose docs/cascade.md and docs/integration.md (migration state)

Filed by Claude Code from the agent-compose v0.2.0 absorption, on Kai's direction.

## Context agent-compose v0.2.0 absorbed the v1 composer: `agent-compose cascade` (agent-compose#23) reproduces generate_agent_compose.py byte-for-byte on shared fixtures - COMPOSED slices, load-point symlinks, and the mount-eligibility manifest ward reads. The Python generator is now redundant everywhere the Go binary is installed (brew tap, scoop bucket, and Forgejo release binaries all exist). ## What to do - [ ] Repoint the check-agent-compose-drift pre-commit hook at `agent-compose cascade --check` (binary presence becomes the hook's dependency instead of the agentic_os package). - [ ] Fleet cutover via infrastructure: hosts run `agent-compose cascade` where they ran generate-agent-compose (Ansible/SessionStart freshen hooks); confirm the mount-eligibility manifest keeps flowing to ward uninterrupted. - [ ] Special-case Kai's workstation: its COMPOSED.* snapshots carry hand edits (per the 2026-07-01 note in its agent-compose.yaml) that must be reconciled into source files before the first native cascade run, or they will be regenerated away. - [ ] Remove agentic_os/generators/generate_agent_compose.py, its console entry points (generate-agent-compose, check-agent-compose-drift's Python path), and tests/test_agent_compose.py once no host or hook references them. - [ ] Keep check-agent-compose-size / check-agent-compose-dedup / check-context-budget: they validate content, not composition, and are untouched by the absorption. ## Sequencing Hook repoint and fleet cutover can run in either order but both precede removal. The workstation reconciliation is HITL and independent. ## References - agent-compose#23 (absorption, cross-check record) - agent-compose docs/cascade.md and docs/integration.md (migration state) Filed by Claude Code from the agent-compose v0.2.0 absorption, on Kai's direction.

coilyco-ops added the

autonomy

async-consult

priority

labels

2026-07-29 03:44:50 +00:00

coilyco-ops added

priority

and removed

priority

labels

2026-07-29 06:19:36 +00:00

coilyco-ops referenced this issue

2026-08-05 07:49:03 +00:00

Consume role repository metadata and compile native residency #895

coilyco-ops commented

2026-08-05 07:49:14 +00:00

Author

Member

The Python-generator retirement is now part of the broader role-repository migration:

Parent: coilyco-flight-deck/agent-compose#200
AOS implementation: #895

The earlier checkpoint to keep the standalone mount-eligibility manifest flowing is transitional only. The accepted final state removes that manifest after verified role-bundle consumers land.

The Python-generator retirement is now part of the broader role-repository migration: * Parent: https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose/issues/200 * AOS implementation: https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/issues/895 The earlier checkpoint to keep the standalone mount-eligibility manifest flowing is transitional only. The accepted final state removes that manifest after verified role-bundle consumers land.

coilyco-ops referenced this issue from a commit

2026-08-05 09:50:50 +00:00

feat(context): consume verified repository plans

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-05 09:51:50 +00:00

feat(context): consume verified repository plans #896