The non-interactive query path builds its context in one shared place, meant to behave identically.
What's wrong with this entry?
The non-interactive query path no longer builds the same large context object inline in two places, which is intended to be behaviour-preserving.
- Context is built through a shared factory called with
phase: "input"andphase: "query" - Model and thinking configuration come from a single resolver
systemPromptarrives pre-rendered from the prompt builder, including appendSystemPrompt and mcpClients- Compact-boundary handling is delegated to
applyCompactBoundaryandflushBeforeCompactBoundary
applyCompactBoundary
Strings lifted out of the shipped bundle, so the claim above can be checked against them.