feat(roster)!: follow the eval, tpm and devrel slug renames #1357
No reviewers
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/agentic-os!1357
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/ad84"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1354. Closes the fixture half of #1347.
Mirrors
agent-compose@d1395f8andhousecast-v0.1.12.evalbecomessciencetpmbecomesdirectordevrelbecomesadvocate.agents/roles.kdland.agents/harness-launch-profiles.yamlcarry the role keys, which is the item #1354 called out as the one worth doing first: both now answer for the new slugs, so those seats get role-scoped projection again once the repository plan recompiles.Fixtures were regenerated, not hand-patched
aterm/testdata/roster.jsoncame fromagent-compose catalog roles --json, and the four overlays fromagent-compose overlay --json --expression acting, both against a build of the renamed roster. That was the argument on #1347:roster.jsoncarriesskill_digestvalues that moved with the SKILL.md bodies, so a hand edit would have left the fixture internally inconsistent in a way no test catches.tpm-codex-overlay.jsonis renamed todirector-codex-overlay.json.eval was read per occurrence, not swept
evalalso names the activity here, so a blanket rename would have done real damage. Verified as other senses and left untouched:aos-evaland its package,evalkit, theeval-refdocsevalshell builtin inshell/common.sh- a sweep turnedeval "$script"intoscience "$script", which would have broken aterm completion in every shell. Caught and reverted.never run evalin.specgen/guardfiles/aosguard/redis.kdl--evalCLI flag incheck_actions_run_one_line.pyWhat deliberately did not move
The eight
tooling-<slug>-*composed skill packages keep their names, and the roles.kdl globs still match them, so nothing breaks. Whether that prefix names the seat or the practice is the open question on #1354 and a slug rename does not settle it. Their acting-seat prose did move, per the #1223 rule: "Use when eval verifies" became "Use when science verifies".Verification
uv run pytest- 748 passedaos-cliGo suite - cleanatermGo suite - clean withagent-composeoff PATH, which is how CI runs itTestLiveDefaultSeatBelongsToItsRolefails on a developer host that has anagent-composebinary predating the rename:aosreadsharness-launch-profiles.yamlfrom the checkout and answers for the new slugs, while the stale binary still reports the old ones. The test skips whenagent-composeis absent from PATH. It is a host-local migration artifact that clears when agent-compose is reinstalled, not a defect in this change.Boundary
Authored from the science seat. This repository is
build-foundational-softwareand belongs to platform; Kai directed the crossing explicitly. Naming it rather than leaving it implicit.