coilyco-flight-deck/agentic-os

Watch

Remove stale Ward QA fixture repository pointers #1294

New issue

Open

opened 2026-08-27 03:25:00 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-27 03:25:00 +00:00

Owner

Outcome

Remove the stale Ward QA fixture repository pointer and all generated inventory derived from it. The repository was intentionally deleted by Kai on 2026-08-05 and must not be recreated.

Context

Ward #1645 removes the public verification-fixture product mode. The canonical private composition source still exposes a repo-ward-qa-fixture skill whose pointer now resolves to an absent checkout and a deleted Forgejo repository.

Scope

Remove the canonical repo-ward-qa-fixture skill source from its owning repository.
Remove roster, catalog, generated-skill, expected-repository, or composition references derived from that source.
Regenerate composed or installed outputs through their owning generation workflow rather than editing generated copies.
Search for remaining references to ward-qa-fixture across composition and fleet inventory.
Do not recreate, restore, or replace the deleted repository.
Keep Ward implementation work in Ward #1645.

Acceptance

No active skill or repository inventory points at coilyco-flight-deck/ward-qa-fixture.
Generated composition outputs are refreshed from canonical sources.
Expected-repository and workspace inputs no longer request the deleted checkout.
Repository-wide validation passes in each changed owner.
Ward #1645 links this issue as the cross-repository cleanup owner.

coilyco-flight-deck/ward#1645

## Outcome Remove the stale Ward QA fixture repository pointer and all generated inventory derived from it. The repository was intentionally deleted by Kai on 2026-08-05 and must not be recreated. ## Context Ward #1645 removes the public verification-fixture product mode. The canonical private composition source still exposes a `repo-ward-qa-fixture` skill whose pointer now resolves to an absent checkout and a deleted Forgejo repository. ## Scope * Remove the canonical `repo-ward-qa-fixture` skill source from its owning repository. * Remove roster, catalog, generated-skill, expected-repository, or composition references derived from that source. * Regenerate composed or installed outputs through their owning generation workflow rather than editing generated copies. * Search for remaining references to `ward-qa-fixture` across composition and fleet inventory. * Do not recreate, restore, or replace the deleted repository. * Keep Ward implementation work in Ward #1645. ## Acceptance * No active skill or repository inventory points at `coilyco-flight-deck/ward-qa-fixture`. * Generated composition outputs are refreshed from canonical sources. * Expected-repository and workspace inputs no longer request the deleted checkout. * Repository-wide validation passes in each changed owner. * Ward #1645 links this issue as the cross-repository cleanup owner. ## Related * https://forgejo.coilysiren.me/coilyco-flight-deck/ward/issues/1645

coilyco-ops referenced this issue from a commit

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

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

coilyco-ops referenced this issue

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

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

coilyco-ops commented

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

Author

Owner

The agentic-os half is landed. Two of the four remaining references are not deletions.

Merged as #1339. aos-cli/repositories/sealed-repos.gitignore no longer lists coilyco-flight-deck/ward-qa-fixture. That mattered more than a stale line usually does: 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 deleted on 2026-08-05.

coilyco-flight-deck/ward is untouched, both its sealed entry and the ! override below it. Ward is archived rather than deleted, so it still resolves. aos-cli/repositories/substrate-repos.txt carried no ward entries at all.

Full sweep of `~/projects`, five hits

Done (1): agentic-os/aos-cli/repositories/sealed-repos.gitignore.

Already satisfied, needs no edit (2):

~/projects/.agents/skills/repo-ward-qa-fixture/SKILL.md
~/projects/.agent-compose/projection.json

Both are installed host state rather than repository content, and the canonical source this issue asks to remove is already gone: no repo carries that skill source, and agentic-os-kai's registry does not list the fixture, so the pointer-skill generator will not re-emit it. They clear on the next agent-compose convergence, which is what "regenerate through the owning generation workflow rather than editing generated copies" asks for. Nothing to do here beyond not hand-editing them.

Deliberately not touched (2): infrastructure/scripts/forgejo_github_mirror_sync.py and its test keep the fixture in a skip list, commented "Installation lookup returns 404 for these failing targets. #738 tracks their distinct intended states without presuming one shared cause."

That is not a stale pointer of the kind this issue is about. It is an instruction not to touch the repository, and removing it would let the mirror sync attempt a deleted target rather than skip it. The comment also ties it to #738, which is explicitly tracking these entries as distinct states. So it wants that issue's decision, in that repo, rather than a delete here.

Acceptance status

No active skill or repository inventory points at the fixture. The two that still name it are a generated artifact awaiting convergence and a deliberate skip entry.
Generated composition outputs refresh from canonical sources, which no longer carry it.
Expected-repository input no longer requests the deleted checkout. This was the real one, and it is fixed.
Repository-wide validation passes: 753 tests and pre-commit run --all-files exit 0.

Leaving this open for the infrastructure / #738 half rather than closing on the agentic-os change alone.

## The agentic-os half is landed. Two of the four remaining references are not deletions. Merged as **#1339**. `aos-cli/repositories/sealed-repos.gitignore` no longer lists `coilyco-flight-deck/ward-qa-fixture`. That mattered more than a stale line usually does: `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 deleted on 2026-08-05. `coilyco-flight-deck/ward` is untouched, both its sealed entry and the `!` override below it. Ward is archived rather than deleted, so it still resolves. `aos-cli/repositories/substrate-repos.txt` carried no ward entries at all. ## Full sweep of `~/projects`, five hits **Done (1):** `agentic-os/aos-cli/repositories/sealed-repos.gitignore`. **Already satisfied, needs no edit (2):** * `~/projects/.agents/skills/repo-ward-qa-fixture/SKILL.md` * `~/projects/.agent-compose/projection.json` Both are **installed host state rather than repository content**, and the canonical source this issue asks to remove is already gone: no repo carries that skill source, and `agentic-os-kai`'s registry does not list the fixture, so the pointer-skill generator will not re-emit it. They clear on the next agent-compose convergence, which is what "regenerate through the owning generation workflow rather than editing generated copies" asks for. Nothing to do here beyond not hand-editing them. **Deliberately not touched (2):** `infrastructure/scripts/forgejo_github_mirror_sync.py` and its test keep the fixture in a **skip list**, commented *"Installation lookup returns 404 for these failing targets. #738 tracks their distinct intended states without presuming one shared cause."* That is not a stale pointer of the kind this issue is about. It is an instruction **not** to touch the repository, and removing it would let the mirror sync attempt a deleted target rather than skip it. The comment also ties it to #738, which is explicitly tracking these entries as distinct states. So it wants that issue's decision, in that repo, rather than a delete here. ## Acceptance status * No **active** skill or repository inventory points at the fixture. The two that still name it are a generated artifact awaiting convergence and a deliberate skip entry. * Generated composition outputs refresh from canonical sources, which no longer carry it. * Expected-repository input no longer requests the deleted checkout. **This was the real one**, and it is fixed. * Repository-wide validation passes: 753 tests and `pre-commit run --all-files` exit 0. Leaving this open for the `infrastructure` / #738 half rather than closing on the agentic-os change alone.

coilyco-ops added the

role/platform

autonomy

headless

labels

2026-08-29 07:01:30 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilyco-flight-deck/agentic-os#1294

No description provided.

Rows
Columns