Wait for the application, not the clock, in the strict QA set

The probe exposes settled() and the first-frame outcome; scripts/qa/ready.mjs
waits for drawn frames with the camera at rest and for a pick at the click
position, with a deadline and its reason in the error. The strict scenarios
use these instead of fixed pauses and loading-screen polling, and the
hidden-switch scenario checks how the loading screen was lifted instead of
how long it took.

Each switch scenario now records a draw ledger per engine and runs a
contract monitor; both write to the scenario's evidence file only, with an
empty allowlist until browser runs show what differs on purpose.

scripts/qa-navara-cockpit-clouds.mjs

@@ -71,13 +71,28 @@ const save = (name, pixels) => saveCapture(outDir, name, pixels);
 // Clouds grey the frame: the blue sky and the map's coloured lines go.
 const saturation = (pixels) => stats(pixels).saturation;
 
-// A few seconds of continuous frames: the clouds converge over frames.
+// The temporal cloud pass converges over drawn frames.
 async function converged(page, name) {
   await page.evaluate(async () => {
     const { engine } = window.__godsEyeView;
     engine.render.setContinuous(true);
-    await new Promise((resolve) => setTimeout(resolve, 3000));
-    engine.render.setContinuous(false);
+    try {
+      await new Promise((resolve, reject) => {
+        let frames = 0;
+        const timer = setTimeout(() => {
+          remove();
+          reject(new Error('Cloud convergence frames did not arrive'));
+        }, 30000);
+        const remove = engine.frames.postRender.addEventListener(() => {
+          if (++frames < 120) return;
+          remove();
+          clearTimeout(timer);
+          resolve();
+        });
+      });
+    } finally {
+      engine.render.setContinuous(false);
+    }
   });
   const pixels = await capture(page);
   save(name, pixels);