Move default substrate repo ownership into aos #373

New issue

Closed

opened 2026-07-09 15:51:54 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-07-09 15:51:54 +00:00

Member

PR ward#802 tried to remove coilyco-flight-deck/ward from ward's embedded default substrate manifest, but the desired ownership is the other way around: the default repo substrate belongs in aos, alongside the dev-base image and public substrate seed.

Current state:

aos has docker/dev-base/substrate-image-repos.txt, including coilyco-flight-deck/ward.
That file currently says it is a denormalized copy of ward's canonical list.
ward has cmd/ward/containerassets/preclone-repos.txt, which PR ward#802 changed to remove ward and made ward docs/tests assert that policy.

Desired state:

aos is canonical for the default/image-tier substrate repo set that the dev-base image bakes and publishes.
The aos docs should say this is owned here because aos owns the dev-base image and seed content.
coilyco-flight-deck/ward should remain in the default image-tier substrate list unless a separate product decision removes it from the dev-base seed.
ward should not be the source of truth for the default substrate set. It can consume/generated-copy the list or document the boundary, but the default repo substrate should not be authored in ward.

Acceptance:

Update docker/dev-base/substrate-image-repos.txt and nearby docs/comments so aos is clearly canonical, not a denormalized consumer of ward.
Add or update tests/scripts/docs that guard the aos-owned default substrate list if there is already a local pattern for generated assets.
Coordinate with ward so PR ward#802's ward-side removal/assertions are reverted or reshaped to point at aos ownership rather than deleting ward from substrate.
Run the repo's ward/pre-commit validation.

Related: coilyco-flight-deck/ward#802

PR ward#802 tried to remove `coilyco-flight-deck/ward` from ward's embedded default substrate manifest, but the desired ownership is the other way around: the default repo substrate belongs in aos, alongside the dev-base image and public substrate seed. Current state: * aos has `docker/dev-base/substrate-image-repos.txt`, including `coilyco-flight-deck/ward`. * That file currently says it is a denormalized copy of ward's canonical list. * ward has `cmd/ward/containerassets/preclone-repos.txt`, which PR ward#802 changed to remove ward and made ward docs/tests assert that policy. Desired state: * aos is canonical for the default/image-tier substrate repo set that the dev-base image bakes and publishes. * The aos docs should say this is owned here because aos owns the dev-base image and seed content. * `coilyco-flight-deck/ward` should remain in the default image-tier substrate list unless a separate product decision removes it from the dev-base seed. * ward should not be the source of truth for the default substrate set. It can consume/generated-copy the list or document the boundary, but the default repo substrate should not be authored in ward. Acceptance: * Update `docker/dev-base/substrate-image-repos.txt` and nearby docs/comments so aos is clearly canonical, not a denormalized consumer of ward. * Add or update tests/scripts/docs that guard the aos-owned default substrate list if there is already a local pattern for generated assets. * Coordinate with ward so PR ward#802's ward-side removal/assertions are reverted or reshaped to point at aos ownership rather than deleting ward from substrate. * Run the repo's ward/pre-commit validation. Related: https://forgejo.coilysiren.me/coilyco-flight-deck/ward/pulls/802

coilyco-ops referenced this issue from a commit

2026-07-09 15:59:25 +00:00

fix: make dev-base substrate seed canonical

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

2026-07-09 16:01:17 +00:00

fix: make dev-base substrate seed canonical #374

coilyco-ops closed this issue

2026-07-09 16:18:45 +00:00