test: wait for the client to give up on a name that never resolves

How long a machine takes to say a name does not resolve is its own, and the
page was idle before the answer came on one runner, so the snapshot was taken
of "Hey." alone. The test now waits for the message that ends the sequence it
records.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UjuMAuk9o6UazjHzcAQCTA

Author: alexander-akait

test/e2e/web-socket-server-url.test.js

@@ -7,6 +7,7 @@ import Server from "../../lib/Server.js";
 import config from "../fixtures/client-config/webpack.config.js";
 import runBrowser from "../helpers/run-browser.js";
 import sessionSubscribe from "../helpers/session-subscribe.js";
+import waitFor from "../helpers/wait-for.js";
 import portsMap from "../ports-map.js";
 
 const [port1, port2] = portsMap["web-socket-server-url"];
@@ -2199,6 +2200,16 @@ describe("web socket server URL", () => {
           waitUntil: "networkidle0",
         });
 
+        // The name never resolves, and how long a machine takes to say so is
+        // its own: the page is idle before the answer comes. What the client
+        // says once it has given up on the first attempt is the end of what
+        // there is to record.
+        await waitFor(() =>
+          consoleMessages.some((message) =>
+            message.text().includes("Trying to reconnect"),
+          ),
+        );
+
         t.assert.snapshot(consoleMessages.map((message) => message.text()));
         t.assert.snapshot(
           pageErrors.map((pageError) =>