assertEquals("Q2", request.getMessages().get(0).getContent());
        assertEquals("A2", request.getMessages().get(1).getContent());
    }

    // ========== addHistoryWithBudget — turn-based packing tests ==========

    @Test
    public void test_addHistoryWithBudget_turnBasedPacking_twoCompleteTurns() {
        final List<LlmMessage> history = new ArrayList<>();
        history.add(LlmMessage.user("Q1")); // 2

nfiguration/assign-pod-node/). Node affinity/anti-affinity allow you to specify rules for restricting which node(s) a pod can schedule onto, based on the labels on the node. Pod affinity/anti-affinity allow you to specify rules for spreading and packing pods relative to one another, across arbitrary topologies (node, zone, etc.) These affinity rules are now be specified in a new-in-1.6 `affinity` field of the PodSpec. Kubernetes 1.6 continues to support the alpha `scheduler.alpha.kubernetes.io/affinity`...