"still awaits a navigation when waitForStableDom is false" is flaky

still awaits a navigation when waitForStableDom is false (4344.1574ms)
  AssertionError [ERR_ASSERTION]: Expected the navigation to be awaited and reported, got: Script ran on page and returned:

  undefined

      at file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/tools/script.test.js:61:24
      at async file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/utils.js:123:9
      at async file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/utils.js:75:21
      at async withBrowser (file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/utils.js:66:13)
      at async withMcpContext (file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/utils.js:106:5)
      at async TestContext.<anonymous> (file:///D:/a/chrome-devtools-mcp/chrome-devtools-mcp/build/tests/tools/script.test.js:48:13)
      at async Test.run (node:internal/test_runner/test:1389:7)
      at async Suite.processPendingSubtests (node:internal/test_runner/test:960:7) {
    generatedMessage: false,
    code: 'ERR_ASSERTION',
    actual: false,
    expected: true,
    operator: '==',
    diff: 'simple'
  }

Example: https://github.com/ChromeDevTools/chrome-devtools-mcp/actions/runs/32607056301/job/97113574754?pr=2607

Usually on windows and macos. Root cause is not clear and need to be investigated.

Start with the failing test "still awaits a navigation when waitForStableDom is false" in build/tests/tools/script.test.js and the surrounding helpers in build/tests/utils.js. Reproduce it in CI or on Windows and macOS, then determine why the navigation is not awaited; done means the test reliably reports the navigation without platform-specific flakiness.