Retire legacy repo-local codex.COMPOSED.md and claude.COMPOSED.md files #106

New issue

Closed

opened 2026-07-27 18:27:12 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-07-27 18:27:12 +00:00

Member

Decision

Retire the legacy per-agent, repository-local codex.COMPOSED.md and claude.COMPOSED.md files. These artifacts predate the agent-compose CLI and must no longer be generated, loaded, validated, or treated as canonical context.

The current agent-compose CLI and its CLI-managed harness load points remain the composition path.

Migration

The work inventories every tracked instance of codex.COMPOSED.md and claude.COMPOSED.md across the repository fleet.
Each owning repository deletes those legacy files.
Each owning subsystem removes scripts, hooks, configuration, and documentation that generate, consume, or validate those files.
If a legacy file contains hand-authored material not represented in a current canonical source, the owning repository moves that material to the correct source before deleting the legacy artifact. The migration does not preserve the old file as a compatibility surface.
Infrastructure removes any fleet rollout or convergence behavior that recreates the repo-local files.

Acceptance

A repository-fleet search finds no tracked codex.COMPOSED.md or claude.COMPOSED.md files.
Active code, configuration, validation, and documentation contain no remaining load or generation contract for those files.
Running the current agent-compose convergence path does not recreate either repo-local artifact.
Agent-compose's current CLI-managed composition and harness load points continue to work.
Every touched repository passes its declared Ward validation.
Cross-repo changes land through each repository's resolved workflow.

Ownership

Each repository owns deletion of its checked-in legacy artifacts and local references.
Agent-compose owns any compatibility cleanup and regression coverage needed to prove its CLI does not recreate or consume them.
Infrastructure owns fleet convergence changes needed to stop rollout from restoring them.

Non-goals

Retiring .agents/composed/*/COMPOSED.md provider skill sources.
Removing composed-skill bindings from .agents/roles.kdl.
Removing or renaming agent-compose's CLI-managed ~/.agent-compose/COMPOSED.md or COMPOSED.<harness>.md outputs.
Changing provider, role, personality, bundle, or delivery contracts.

## Decision Retire the legacy per-agent, repository-local `codex.COMPOSED.md` and `claude.COMPOSED.md` files. These artifacts predate the agent-compose CLI and must no longer be generated, loaded, validated, or treated as canonical context. The current agent-compose CLI and its CLI-managed harness load points remain the composition path. ## Migration * The work inventories every tracked instance of `codex.COMPOSED.md` and `claude.COMPOSED.md` across the repository fleet. * Each owning repository deletes those legacy files. * Each owning subsystem removes scripts, hooks, configuration, and documentation that generate, consume, or validate those files. * If a legacy file contains hand-authored material not represented in a current canonical source, the owning repository moves that material to the correct source before deleting the legacy artifact. The migration does not preserve the old file as a compatibility surface. * Infrastructure removes any fleet rollout or convergence behavior that recreates the repo-local files. ## Acceptance * A repository-fleet search finds no tracked `codex.COMPOSED.md` or `claude.COMPOSED.md` files. * Active code, configuration, validation, and documentation contain no remaining load or generation contract for those files. * Running the current agent-compose convergence path does not recreate either repo-local artifact. * Agent-compose's current CLI-managed composition and harness load points continue to work. * Every touched repository passes its declared Ward validation. * Cross-repo changes land through each repository's resolved workflow. ## Ownership * Each repository owns deletion of its checked-in legacy artifacts and local references. * Agent-compose owns any compatibility cleanup and regression coverage needed to prove its CLI does not recreate or consume them. * Infrastructure owns fleet convergence changes needed to stop rollout from restoring them. ## Non-goals * Retiring `.agents/composed/*/COMPOSED.md` provider skill sources. * Removing `composed-skill` bindings from `.agents/roles.kdl`. * Removing or renaming agent-compose's CLI-managed `~/.agent-compose/COMPOSED.md` or `COMPOSED.<harness>.md` outputs. * Changing provider, role, personality, bundle, or delivery contracts.

coilyco-ops referenced this issue from coilyco-flight-deck/agentic-os

2026-07-27 18:27:26 +00:00

Remove checked-in role COMPOSED sources from AOS #764

coilyco-ops changed title from ~~Retire repository COMPOSED skill sources from the provider contract~~ to Retire legacy repo-local codex.COMPOSED.md and claude.COMPOSED.md files

2026-07-27 18:51:44 +00:00

coilyco-ops commented

2026-07-27 19:50:56 +00:00

Author

Member

Fleet retirement verification completed with no source changes required.

Canonical inventory

Enumerated all 32 non-archived canonical repositories across coilyco-flight-deck, coilyco-bridge, coilyco-gaming, and coilysiren.
Took a shallow no-checkout snapshot of each canonical main tree.
git ls-tree -r --name-only HEAD found zero tracked codex.COMPOSED.md or claude.COMPOSED.md files across all 32 repositories.

Active reference audit

Searched every complete Forgejo main tree's text-bearing code, configuration, workflow, script, and documentation blobs case-insensitively for the two exact legacy names.
Large or API-truncated repositories were completed from their exact canonical-main Git object trees rather than accepting a truncated result.
One skipped blob across the complete scans was agentic-os/static/wallpaper-verdant.jpg, a JPEG raster image. It is not an active text surface.
Final result: zero active references, with no unresolved request, decode, tree-truncation, or grep failures.

Agent-compose behavior

The current agent-compose source has zero references to either repo-local legacy filename.
ward exec test and ward exec smoke pass on canonical main 5923d2d.
The smoke exercises first convergence, idempotent second convergence, verbose reapply, CLI-managed ~/.agent-compose/COMPOSED.md, native skills, MCP projection, and harness load points. It creates no repo-local legacy artifact.
.agents/composed/*/COMPOSED.md provider sources and CLI-managed composed outputs remain intact, matching the issue's non-goals.

The migration had already converged before this audit. No owning repository currently contains an artifact or compatibility path to delete, so a verification-only close is the smallest complete resolution.

Fleet retirement verification completed with no source changes required. ## Canonical inventory * Enumerated all 32 non-archived canonical repositories across `coilyco-flight-deck`, `coilyco-bridge`, `coilyco-gaming`, and `coilysiren`. * Took a shallow no-checkout snapshot of each canonical `main` tree. * `git ls-tree -r --name-only HEAD` found **zero** tracked `codex.COMPOSED.md` or `claude.COMPOSED.md` files across all 32 repositories. ## Active reference audit * Searched every complete Forgejo main tree's text-bearing code, configuration, workflow, script, and documentation blobs case-insensitively for the two exact legacy names. * Large or API-truncated repositories were completed from their exact canonical-main Git object trees rather than accepting a truncated result. * One skipped blob across the complete scans was `agentic-os/static/wallpaper-verdant.jpg`, a JPEG raster image. It is not an active text surface. * Final result: **zero active references**, with no unresolved request, decode, tree-truncation, or grep failures. ## Agent-compose behavior * The current `agent-compose` source has zero references to either repo-local legacy filename. * `ward exec test` and `ward exec smoke` pass on canonical main `5923d2d`. * The smoke exercises first convergence, idempotent second convergence, verbose reapply, CLI-managed `~/.agent-compose/COMPOSED.md`, native skills, MCP projection, and harness load points. It creates no repo-local legacy artifact. * `.agents/composed/*/COMPOSED.md` provider sources and CLI-managed composed outputs remain intact, matching the issue's non-goals. The migration had already converged before this audit. No owning repository currently contains an artifact or compatibility path to delete, so a verification-only close is the smallest complete resolution.

coilyco-ops closed this issue

2026-07-27 19:50:57 +00:00

coilyco-ops referenced this issue

2026-07-27 19:58:59 +00:00

Land the next three unblocked agent-compose engineering issues #108