test(webapp): give the Worker settlement poll room and poll gently

The bridge-integrity test polled its DOM integrity scan every 5ms (~200×/s)
while waiting up to 5s for the Worker's release-exact solve. On a loaded CI
runner that scan storm starved the very Worker message-handling it awaited,
so the release-exact settlement counter did not advance in time and the poll
timed out — while the integrity assertions it guards were never in question.
Poll gently (100/250/500ms) and allow 15s for the Worker round-trip, with a
60s test budget. No change to what the test verifies.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014K2K5q7x9kmnkG3qpFQhwT

Author: FelixTJDietrich

standalone/webapp/tests/e2e/edge-line-jump-integrity.spec.ts

@@ -282,6 +282,11 @@ test.describe("Line-jump geometry integrity", () => {
   test("bridges stay attached during Worker preview and at settlement handoff", async ({
     page,
   }) => {
+    // This exercises the Worker preview + release-exact settlement path on a
+    // 30-node fixture; the Worker round-trip can exceed the default budget on a
+    // loaded CI runner, so give it room (the integrity assertions below are what
+    // matter, not how fast the Worker returns).
+    test.setTimeout(60_000)
     const fixture = load("perf-routing-30-nodes.json")
     await openLocalWithPerf(page, fixture)
     await page.waitForFunction(
@@ -330,7 +335,9 @@ test.describe("Line-jump geometry integrity", () => {
             perf.routingPreviewCount > 0
           )
         },
-        { intervals: [5], timeout: 5_000 }
+        // Poll gently: a 5ms interval re-ran the full DOM integrity scan ~200×/s
+        // and starved the very Worker message-handling it was waiting on.
+        { intervals: [100, 250, 500], timeout: 15_000 }
       )
       .toBe(true)
     // The perf write happens in the solver's layout effect. Inspect painted
@@ -372,7 +379,9 @@ test.describe("Line-jump geometry integrity", () => {
           }
           return false
         },
-        { intervals: [5], timeout: 5_000 }
+        // Poll gently: a 5ms interval re-ran the full DOM integrity scan ~200×/s
+        // and starved the very Worker message-handling it was waiting on.
+        { intervals: [100, 250, 500], timeout: 15_000 }
       )
       .toBe(true)