docs(comments): name the renamed seats in two test comments #1154
No reviewers
Labels
No labels
burndown-2026-08
move-to-repo
coilyco-bridge-deploy
move-to-repo
coilyco-flight-deck-agent-compose
move-to-repo
coilyco-gaming-eco-app
move-to-repo
coilysiren-inbox
move-to-repo
unknown
🔒⚠️📦⚠️🔒 SANDBOXED 🔒⚠️📦⚠️🔒
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
c#
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
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-gaming/sirens-echo!1154
Loading…
Reference in a new issue
No description provided.
Delete branch "aos/claude/vu59-roster-recall"
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?
agent-compose#344 renamed the sysadmin seat to Vera and the eval seat to Evie. Two test comments point at work those seats did, and a seat survives its own rename, so they carry the current name.
Cosmetic, comment-only.
go test ./internal/community/green, hooks green.The tracked role snapshots under
agent/rendered/roles/still carry pre-v3 slugs (exec,ai) alongside the old seats. Regenerating them needs a bake and is the v3 debt rather than this pass, tracked separately.Refs coilyco-flight-deck/agent-compose#344
Blocked, and not by this diff.
ci / testandci / image-buildare red onmainfor everything since 2026-08-23, because the dev-base image picked up a post-v3 agent-compose and this repo's compose layer is still keyed on the pre-v3 slugs. Full diagnosis and done condition in #1155.These two comment lines stand on their own and merge once
mainis green. Leaving the branch open rather than closing it, since the work is correct and the blocker is upstream of it.