Delete aos-eval and its nine reference sites #1389

Merged

coilyco-ops merged 1 commit from aos/claude/ee98-aoseval into main

2026-08-29 08:34:43 +00:00

coilyco-ops commented

2026-08-29 08:32:49 +00:00

Owner

Closes #1374. This breaks a live consumer, deliberately, and the recovery is already handed over.

The decision

Kai lifted the gate ("once sirens-echo has moved to housecast grade") on 2026-08-29 with the consumer-breakage caveat in front of her. Decision, not oversight.

It has not moved, and I checked rather than assumed

sirens-echo 9f27988, scripts/task.sh:187:

aos_eval_ref="${AOS_EVAL_REF:-main}"
aos_eval_spec="aos-eval @ git+https://.../agentic-os.git@${ref}#subdirectory=aos-eval"

A live dependency on this repo's main. just grade, just taxonomy, and just grade-check stop resolving when this lands. sirens-echo#1166 is open and states this had to land first.

Already notified, with the one-line fix using their own escape hatch: AOS_EVAL_REF=aos-eval-v0.12.0, the newest tag still carrying the package, which I verified before naming it. Better than letting them find it through a failing grading run.

The nine sites, exactly as the issue counted

Deleted: aos-eval/, docs/aos-eval.md, .agents/skills/tooling-aos-eval/, .forgejo/workflows/aos-eval-release.yml.

Edited: ci.yml loses the aos-eval-tests job, promote.yml its step, both their cache-key half, justfile both verbs, pyproject.toml its note, docs/FEATURES.md and docs/release.md their entries.

A grep for aos-eval and aos_eval across the repo now returns nothing. 752 tests pass, full hook suite clean, and both Actions validators pass on the edited workflows.

Two consequences worth naming

ci / aos-eval-tests has been failing on main and goes away with the job rather than being fixed. I checked before deleting: the package's own 78 tests pass locally, so the CI failure was environmental. Nobody should read this as having repaired it.

docs/ drops to 39 of 40. That is the first free slot in that budget since it filled, and #1312, #1274, and #1341 are all blocked on exactly that. Kai's answer there was to keep the cap and force merges; a deletion is the merge-equivalent that pays for one of them.

Sequencing note for `#1118`

Kai sequenced the aos-eval/agent-compose crossed-ownership question behind this, on the reasoning that positioning a boundary inside a package scheduled for deletion is work that evaporates. With the package gone, #1118 should be re-read rather than answered as filed.

Closes `#1374`. **This breaks a live consumer**, deliberately, and the recovery is already handed over. ## The decision Kai lifted the gate ("once sirens-echo has moved to housecast grade") on 2026-08-29 with the consumer-breakage caveat in front of her. Decision, not oversight. ## It has not moved, and I checked rather than assumed sirens-echo `9f27988`, `scripts/task.sh:187`: ```sh aos_eval_ref="${AOS_EVAL_REF:-main}" aos_eval_spec="aos-eval @ git+https://.../agentic-os.git@${ref}#subdirectory=aos-eval" ``` A live dependency on this repo's `main`. `just grade`, `just taxonomy`, and `just grade-check` stop resolving when this lands. `sirens-echo#1166` is open and states this had to land first. **Already notified**, with the one-line fix using their own escape hatch: `AOS_EVAL_REF=aos-eval-v0.12.0`, the newest tag still carrying the package, which I verified before naming it. Better than letting them find it through a failing grading run. ## The nine sites, exactly as the issue counted Deleted: `aos-eval/`, `docs/aos-eval.md`, `.agents/skills/tooling-aos-eval/`, `.forgejo/workflows/aos-eval-release.yml`. Edited: `ci.yml` loses the `aos-eval-tests` job, `promote.yml` its step, both their cache-key half, `justfile` both verbs, `pyproject.toml` its note, `docs/FEATURES.md` and `docs/release.md` their entries. A grep for `aos-eval` and `aos_eval` across the repo now returns nothing. 752 tests pass, full hook suite clean, and both Actions validators pass on the edited workflows. ## Two consequences worth naming **`ci / aos-eval-tests` has been failing on main** and goes away with the job rather than being fixed. I checked before deleting: the package's own 78 tests pass locally, so the CI failure was environmental. Nobody should read this as having repaired it. **`docs/` drops to 39 of 40.** That is the first free slot in that budget since it filled, and `#1312`, `#1274`, and `#1341` are all blocked on exactly that. Kai's answer there was to keep the cap and force merges; a deletion is the merge-equivalent that pays for one of them. ## Sequencing note for `#1118` Kai sequenced the aos-eval/agent-compose crossed-ownership question behind this, on the reasoning that positioning a boundary inside a package scheduled for deletion is work that evaporates. With the package gone, `#1118` should be re-read rather than answered as filed.

coilyco-ops added 1 commit

2026-08-29 08:32:49 +00:00

feat(aos-eval): delete the package and its nine reference sites

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

Details

ci / gate (pull_request) Successful in 56s

Details

5b1262f64a

Kai lifted the gate on 2026-08-29: delete regardless of whether sirens-echo has
moved to `housecast grade`. I put the option with the consumer-breakage caveat
attached and she chose it with that visible, so this is the decision rather than
an oversight.

It has not moved, and I checked rather than assumed. sirens-echo `9f27988`:

scripts/task.sh:187
aos_eval_ref="${AOS_EVAL_REF:-main}"
aos_eval_spec="aos-eval @ git+https://.../agentic-os.git@${ref}#subdirectory=aos-eval"

That is a live dependency on this repo's `main`, not a stale mention, so `just
grade`, `just taxonomy`, and `just grade-check` break there the moment this
lands. sirens-echo#1166 is open and says plainly that it has to land first.

The recovery is one line and uses the escape their own script already has:
`AOS_EVAL_REF=aos-eval-v0.12.0`, the newest tag still carrying the package.
Commented on their issue in the same turn rather than leaving it to a failing
grading run.

Nine reference sites, exactly as the issue counted:

* `aos-eval/`, `docs/aos-eval.md`, `.agents/skills/tooling-aos-eval/`,
`.forgejo/workflows/aos-eval-release.yml` - deleted
* `ci.yml` loses the aos-eval-tests job, `promote.yml` its step, both their
cache-key half, `justfile` both verbs, `pyproject.toml` its note,
`docs/FEATURES.md` and `docs/release.md` their entries

Two consequences worth naming. `ci / aos-eval-tests` has been failing on main
and goes away with the job rather than being fixed. And `docs/` drops to 39 of
40, freeing the first slot in that budget since it filled, which is what #1312,
#1274, and #1341 are all blocked on.

752 tests pass and the full hook suite is clean. A grep for `aos-eval` and
`aos_eval` across the repo returns nothing.

Refs coilyco-flight-deck/agentic-os#1374

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