fix(e2e): give the desktop run room on a Windows runner

Ubuntu passed the whole spec in 2m33s. Windows was still merging when the
180-second wait expired, having got as far as "Filtering images: kept 13
of 18" and stopped there. Nothing was wrong: the WebAssembly build is
single-threaded on purpose and a GitHub Windows runner is two slow cores.

Raised to ten minutes, and mocha's own timeout past that so a slow run
fails with the app's last reported state rather than mocha killing the
test first and reporting only that time ran out.

Also stopped the state report crying wolf. It flagged any `role="dialog"`
as blocking the run, but the progress modal is one -- so it announced
"BLOCKED-BY-DIALOG" on every healthy run, which is worse than saying
nothing, because the one time it matters nobody believes it. It now looks
for a dialog that actually offers a decision.

Worth recording that the diagnostic earned its keep on its first CI run:
the failure named the last four pipeline steps and their timestamps, so
"stalled after filtering" was legible from the log without reproducing
anything.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: adulbrich

e2e-tests/test/specs/app.e2e.ts

@@ -248,7 +248,11 @@ async function waitForOutputs(outputDir: string): Promise<void> {
             .length >= 2
         );
       },
-      { interval: 1000, timeout: 180_000, timeoutMsg: "no outputs" }
+      // Ten minutes. The WebAssembly build is single-threaded on purpose and a
+      // GitHub Windows runner is two slow cores: Ubuntu finished the whole
+      // spec in 2m33s while Windows was still merging at the old 180s cap.
+      // This is a hang detector, not a performance budget.
+      { interval: 1000, timeout: 600_000, timeoutMsg: "no outputs" }
     );
   } catch (error) {
     throw new Error(
@@ -275,9 +279,19 @@ async function readPipelineState(): Promise<string> {
       )
       .slice(-8)
       .join(" || ");
-    const dialog = document.querySelector('[role="dialog"]');
-    const blocking = dialog
-      ? ` BLOCKED-BY-DIALOG:${(dialog.textContent ?? "").slice(0, 120)}`
+    // Only a dialog offering a decision is blocking. The progress modal is a
+    // `role="dialog"` too, so reporting every dialog cried wolf on every
+    // healthy run -- which is worse than saying nothing, because the one time
+    // it matters nobody believes it.
+    const waiting = Array.from(
+      document.querySelectorAll('[role="dialog"]')
+    ).find((dialog) =>
+      Array.from(dialog.querySelectorAll("button")).some((button) =>
+        /generate (anyway|all)|go back/i.test(button.textContent ?? "")
+      )
+    );
+    const blocking = waiting
+      ? ` WAITING-ON-DIALOG:${(waiting.textContent ?? "").slice(0, 120)}`
       : "";
     return `tauri=${tauri} workers=${workers} shown=${shown || "(nothing)"}${blocking}`;
   });

e2e-tests/wdio.conf.js

@@ -54,7 +54,10 @@ export const config = {
   framework: "mocha",
   maxInstances: 1,
   mochaOpts: {
-    timeout: 240_000,
+    // Comfortably longer than the pipeline's own wait, so a slow run fails
+    // with "no outputs, the app was showing ..." rather than mocha killing the
+    // test first and reporting only that time ran out.
+    timeout: 900_000,
     ui: "bdd",
   },