Allow Content Manager to land content-only code changes #159
No reviewers
Labels
No labels
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/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-flight-deck/agent-compose!159
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-156-content-code"
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 #156
Gives Content Manager the same narrow implementation shape Designer already has, using a content effect test instead of a file-extension rule. Human-facing literals and static content inside code qualify only when control flow, state, schemas, structured contracts, and executable behavior remain unchanged. Behavioral prompts, identifiers, flags, APIs, dependencies, deployment, and live verification stay outside the exception.
Updates the public role boundary, adds a loader regression assertion, and replaces the Content completion scenario with a content-inside-code case. The Core Roster remains 8 packs and 96 cases. The new Content digest is sha256:f6ce445542c04ddae95dc2713132b3c988997b9181806a2d675345569a265c40.
Validation: