Anchor on the card, not on upstream's sentence #774
No reviewers
Labels
No labels
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/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-gaming/sirens-echo!774
Loading…
Reference in a new issue
No description provided.
Delete branch "eng/unpin-the-card-wording"
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?
Two lines. Land this first — it is the only one of the three that is green today.
closes #773
What it fixes
ValidateSystemPromptrequired the literalAgent-compose assigned the. agent-compose owns that sentence and rewrote it in 2.20.0 toassigned **you** the, so every composing role fails against a current bundle:Failing closed is correct — a bundle that did not compose must never ship as a quietly neutral agent. But the trigger here was a copy edit upstream, and the error cannot distinguish that from a real composition failure.
The anchor now matches the half of the line that identifies the card rather than the sentence built around it. It holds against both the 2.19.0 and 2.20.0 wording. The other three anchors are structural rather than prose and are untouched.
Why it is split out, and the order that follows
I had the order wrong when I opened #771 and commented on agentic-os#1052. Correcting it here.
#771 carries the seat rename, which needs 2.20.0 to compose. The image build bakes with
agentic-os:release, which still ships 2.19.0 — so #771 failsci / image-buildtoday and cannot go first. Itsci / testpasses; only the bake fails.Because this PR is backward compatible, the real sequence is:
maintolerate either wording.agentic-os:releaseto republish.Without step 1, step 2 leaves
mainunbuildable until #771 merges. With it, there is no red window.Verification
go test ./...and the full pre-commit suite pass. I verified all four anchors against real bundles baked from both 2.19.0 and 2.20.0 against the live catalogue, which is how the break was found in the first place.🤖 Generated with Claude Code
ValidateSystemPrompt required the literal "Agent-compose assigned the" in a composing profile's prompt. agent-compose owns that sentence and rewrote it in 2.20.0 to "assigned you the", so every composing role fails against a current bundle: role ai: composed profile is missing bundle surface "Agent-compose assigned the" Failing closed is right, since a bundle that did not compose must not ship as a quietly neutral agent. But the trigger was a copy edit upstream, and the error cannot tell that apart from a real composition failure. The anchor now matches the half of the line that identifies the card rather than the sentence around it. It holds against both the 2.19.0 and 2.20.0 wording, so it lands safely on either side of the base-image bump, and a future rewording upstream stops being a build break here. The other three anchors are structural rather than prose and are unchanged. Split from the seat rename, which needs 2.20.0 and cannot pass CI until agentic-os:release carries it. This one removes the window where that bump would leave main unbuildable. closes #773 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>Closing as already landed.
internal/community/prompt.goandinternal/community/compose_test.goare both byte-identical betweenmainand this branch's head, andmainalready carries the loosened anchor: it has"Agent-compose assigned"and no longer has"Agent-compose assigned the".The fix is in effect. The
main...headcompare shows zero commits ahead, so there is nothing left to merge.Branch left in place, so this is reopenable.