Fix Windows integration test: notification ordering race in MCP remote tests

On Windows, the `toolCallRunning` and `progress/Calling tool` notifications
can arrive in either order due to thread scheduling differences. The
`mcp-remote-tool-list-changed-via-tool-call` test assumed strict ordering,
causing it to fail on Windows CI.

Add `match-contents-unordered` helper that collects N notifications and
verifies each expected spec is matched regardless of arrival order. Apply
it to both `mcp-remote-tool-call-in-chat` and
`mcp-remote-tool-list-changed-via-tool-call` tests for the racing pair.

🤖 Generated with [eca](https://eca.dev)

Co-Authored-By: eca-agent <git@eca.dev>

Author: ericdallo

integration-test/integration/chat/mcp_remote_test.clj

@@ -4,7 +4,7 @@
    [clojure.test :refer [deftest is testing]]
    [integration.eca :as eca]
    [integration.fixture :as fixture]
-   [integration.helper :refer [match-content]]
+   [integration.helper :refer [match-content match-contents-unordered]]
    [llm-mock.mocks :as llm.mocks]
    [matcher-combinators.matchers :as m]
    [matcher-combinators.test :refer [match?]]
@@ -107,12 +107,14 @@
                                           :id "mcp-tool-1"
                                           :arguments {:message "hello from mcp"}
                                           :manualApproval false})
-      (match-content chat-id "assistant" {:type "toolCallRunning"
-                                          :origin "mcp"
-                                          :name "echo"
-                                          :id "mcp-tool-1"
-                                          :arguments {:message "hello from mcp"}})
-      (match-content chat-id "system" {:type "progress" :state "running" :text "Calling tool"})
+      ;; toolCallRunning and progress may arrive in either order on Windows
+      (match-contents-unordered
+       [chat-id "assistant" {:type "toolCallRunning"
+                             :origin "mcp"
+                             :name "echo"
+                             :id "mcp-tool-1"
+                             :arguments {:message "hello from mcp"}}]
+       [chat-id "system" {:type "progress" :state "running" :text "Calling tool"}])
 
       ;; Tool called result — echo returns the same message
       (match-content chat-id "assistant" {:type "toolCalled"
@@ -237,12 +239,14 @@
                                           :id "mcp-add-tool-1"
                                           :arguments {:name "multiply"}
                                           :manualApproval false})
-      (match-content chat-id "assistant" {:type "toolCallRunning"
-                                          :origin "mcp"
-                                          :name "add-tool"
-                                          :id "mcp-add-tool-1"
-                                          :arguments {:name "multiply"}})
-      (match-content chat-id "system" {:type "progress" :state "running" :text "Calling tool"})
+      ;; toolCallRunning and progress may arrive in either order on Windows
+      (match-contents-unordered
+       [chat-id "assistant" {:type "toolCallRunning"
+                             :origin "mcp"
+                             :name "add-tool"
+                             :id "mcp-add-tool-1"
+                             :arguments {:name "multiply"}}]
+       [chat-id "system" {:type "progress" :state "running" :text "Calling tool"}])
 
       ;; Tool result
       (match-content chat-id "assistant" {:type "toolCalled"

integration-test/integration/helper.clj

@@ -71,6 +71,20 @@
         :content content}
        (eca/client-awaits-server-notification :chat/contentReceived))))
 
+(defn match-contents-unordered
+  "Consume the next N chat/contentReceived notifications and verify that
+  each SPEC is matched by exactly one of them, regardless of arrival
+  order.  Each spec is a triple [chat-id role content]."
+  [& specs]
+  (let [n       (count specs)
+        actuals (mapv (fn [_] (eca/client-awaits-server-notification :chat/contentReceived))
+                      (range n))]
+    (doseq [[chat-id role content] specs]
+      (is (some #(match? {:chatId chat-id :role role :content content} %) actuals)
+          (str "Expected a notification with role=" role
+               " content=" content
+               " but none of the " n " received matched")))))
+
 (defn match-rewrite-content [rewrite-id content]
   (is (match?
        {:rewriteId rewrite-id