chore(aos-cli): stop shipping a pointer to the deleted ward-qa-fixture repo #1339

Merged

coilyco-ops merged 1 commit from ops/1294-drop-ward-qa-fixture into main

2026-08-28 06:47:28 +00:00

coilyco-ops commented

2026-08-28 06:45:56 +00:00

Owner

Shipping a pointer to a repository that does not exist

aos-cli/repositories/sealed-repos.gitignore listed coilyco-flight-deck/ward-qa-fixture, deleted on 2026-08-05. scripts/aos-release-build.sh copies that file into every release bundle, so each aos release carried a sealed-repo entry naming a deleted repository.

Scope, and what is deliberately untouched

coilyco-flight-deck/ward stays, both its sealed entry and the ! override below it. Ward is archived rather than deleted, so it still resolves. Only the deleted fixture goes.

aos-cli/repositories/substrate-repos.txt carries no ward entries at all, so it needed nothing.

What remains on #1294, and why it is not in this PR

Swept ~/projects for ward-qa-fixture. Five hits, and only this one is a tracked file I own:

~/projects/.agents/skills/repo-ward-qa-fixture/SKILL.md and ~/projects/.agent-compose/projection.json are installed host state, not repository content. The canonical source is already gone: no repo carries that skill and agentic-os-kai's registry does not list the fixture, so the pointer-skill generator will not re-emit it. Both clear on the next agent-compose convergence rather than by hand-editing generated output, which the issue asks for explicitly.
infrastructure/scripts/forgejo_github_mirror_sync.py keeps it in a skip list, commented "installation lookup returns 404 for these failing targets". Removing that entry would let the sync attempt a deleted repository, so it wants an ops decision rather than a delete, and it belongs to that repo.

753 tests pass and pre-commit run --all-files exits 0.

## Shipping a pointer to a repository that does not exist `aos-cli/repositories/sealed-repos.gitignore` listed `coilyco-flight-deck/ward-qa-fixture`, deleted on 2026-08-05. `scripts/aos-release-build.sh` copies that file into every release bundle, so each `aos` release carried a sealed-repo entry naming a deleted repository. ## Scope, and what is deliberately untouched `coilyco-flight-deck/ward` **stays**, both its sealed entry and the `!` override below it. Ward is archived rather than deleted, so it still resolves. Only the deleted fixture goes. `aos-cli/repositories/substrate-repos.txt` carries no ward entries at all, so it needed nothing. ## What remains on #1294, and why it is not in this PR Swept `~/projects` for `ward-qa-fixture`. Five hits, and only this one is a tracked file I own: * `~/projects/.agents/skills/repo-ward-qa-fixture/SKILL.md` and `~/projects/.agent-compose/projection.json` are **installed host state**, not repository content. The canonical source is already gone: no repo carries that skill and `agentic-os-kai`'s registry does not list the fixture, so the pointer-skill generator will not re-emit it. Both clear on the next agent-compose convergence rather than by hand-editing generated output, which the issue asks for explicitly. * `infrastructure/scripts/forgejo_github_mirror_sync.py` keeps it in a **skip list**, commented "installation lookup returns 404 for these failing targets". Removing that entry would let the sync attempt a deleted repository, so it wants an ops decision rather than a delete, and it belongs to that repo. 753 tests pass and `pre-commit run --all-files` exits 0.

coilyco-ops added 1 commit

2026-08-28 06:45:56 +00:00

chore(aos-cli): stop shipping a pointer to the deleted ward-qa-fixture repo

ci / aos-eval-tests (pull_request) Successful in 7s

Details

ci / ward-doctor (pull_request) Successful in 7s

Details

ci / aos-cli-tests (pull_request) Successful in 29s

Details

ci / gate (pull_request) Successful in 48s

Details

09d2487c8b

aos-cli/repositories/sealed-repos.gitignore listed
coilyco-flight-deck/ward-qa-fixture, a repository Kai deleted on 2026-08-05.
scripts/aos-release-build.sh copies that file into every release bundle, so
each `aos` release was shipping a sealed-repo entry naming a repository that
does not exist.

`coilyco-flight-deck/ward` itself stays, both its sealed entry and the `!`
override below it. Ward is archived rather than deleted, so the repository is
still there and still resolves.

Refs #1294

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Agent-Role: platform

coilyco-ops merged commit 0ae1f84b0f into main

2026-08-28 06:47:28 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-28 06:47:29 +00:00

chore(aos-cli): stop shipping a pointer to the deleted ward-qa-fixture repo (#1339)

coilyco-ops referenced this pull request

2026-08-28 06:48:35 +00:00

Remove stale Ward QA fixture repository pointers #1294