The bundle-surface anchor pins a sentence upstream owns, so a copy edit breaks the build #773

New issue

Closed

opened 2026-08-14 04:48:43 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-14 04:48:43 +00:00

Member

🤖 Filed by Claude Code on Kai's behalf.

ValidateSystemPrompt requires a composing profile's prompt to contain the literal:

Agent-compose assigned the

That is the opening of a sentence agent-compose writes into every identity card, and agent-compose owns the wording. In 2.20.0 it became Agent-compose assigned **you** the ..., so every composing role now fails against a current bundle:

role ai: composed profile is missing bundle surface "Agent-compose assigned the"

It fails closed, which is right — a bundle that did not compose must not ship as a quietly neutral agent. But the trigger here is a copy edit upstream, not a composition failure, and the two are indistinguishable from the error.

The fix

Anchor on Agent-compose assigned, the half of the line that identifies the card rather than the sentence built around it. That matches both the 2.19.0 and 2.20.0 wording, so it is safe to land before or after the base image moves, and it stops a future rewording from being a build break here.

The other three anchors (<composed-identity>, ## Personality meld, **Role skill //) are structural rather than prose and stay as they are. Verified all four against real bundles baked from both versions.

Why this is separate from #770

#770 carries the seat rename, which requires 2.20.0 and therefore cannot pass CI until agentic-os:release ships it. This one is backward compatible and can land immediately, which removes the window where the base-image bump would leave main unbuildable.

Split out of #770 for that reason.

🤖 Filed by Claude Code on Kai's behalf.

> 🤖 Filed by Claude Code on Kai's behalf. `ValidateSystemPrompt` requires a composing profile's prompt to contain the literal: ``` Agent-compose assigned the ``` That is the opening of a sentence agent-compose writes into every identity card, and agent-compose owns the wording. In 2.20.0 it became `Agent-compose assigned **you** the ...`, so every composing role now fails against a current bundle: ``` role ai: composed profile is missing bundle surface "Agent-compose assigned the" ``` It fails closed, which is right — a bundle that did not compose must not ship as a quietly neutral agent. But the trigger here is a copy edit upstream, not a composition failure, and the two are indistinguishable from the error. ## The fix Anchor on `Agent-compose assigned`, the half of the line that identifies the card rather than the sentence built around it. That matches both the 2.19.0 and 2.20.0 wording, so it is safe to land before or after the base image moves, and it stops a future rewording from being a build break here. The other three anchors (`<composed-identity>`, `## Personality meld`, `**Role skill //`) are structural rather than prose and stay as they are. Verified all four against real bundles baked from both versions. ## Why this is separate from #770 #770 carries the seat rename, which requires 2.20.0 and therefore cannot pass CI until `agentic-os:release` ships it. This one is backward compatible and can land immediately, which removes the window where the base-image bump would leave `main` unbuildable. Split out of #770 for that reason. > 🤖 Filed by Claude Code on Kai's behalf.

coilyco-ops referenced this issue from a commit

2026-08-14 04:49:01 +00:00

fix(compose): anchor on the card, not on upstream's sentence

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-14 04:49:21 +00:00

Anchor on the card, not on upstream's sentence #774

coilyco-ops referenced this issue

2026-08-14 04:49:38 +00:00

Name Echo's seat, and unpin the card wording #771