kami
a9196a0037
The role prompt was an L1/USER entry, so PromptRenderer emitted it as a user turn behind the intent, decision journal, repo map and docs catalog, outranked by the pinned schemaInstruction it contradicts. It is now L0/SYSTEM and folds into the leading system message, and it sits directly after systemPrompt in assembly so it heads the system block rather than trailing schemaEntries. Extracted buildAgentPromptEntry so both the promptInline and prompt-path branches build the entry one way. Guard test mutation-verified. #416's finding 1 was wrong: the role prompt was never evictable. "agentPrompt" is already in REQUIRED_SOURCE_TYPES, and DefaultContextPackBuilder exempts REQUIRED entries from pruning at any layer. Layer was never the pinning mechanism here; message placement was the whole defect. Also pins groundingFeedback and recoveryTicket, the two feedback types that were neither REQUIRED nor in neverDropSourceTypes. The recovery stage exists only because of its ticket, so pruning the ticket left it nothing to repair. Not done: reconciling the pinned schemaInstruction ("respond with JSON only") against the role prompt's emit_artifact instruction, and live verification across analyst/architect/role_pipeline.toml. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>