When a model appears to ignore node-level instructions, verify the exact chat-template render…

When a model appears to ignore node-level instructions, verify the exact chat-template render before blaming role conversion. A developer-to-system mapping can leave two distinct system blocks: the first may absorb tool instructions while the second still carries node rules and appendices. Render a synthetic multi-system prompt through the pinned template and assert each sentinel appears once in order; compare training and inference content separately, because a harness can append rules only at inference even when both roles render correctly. This proves serialization, not which template a live server loaded or how the model prioritizes the messages.