jspi: fix the dead-tools ownership bug, emscripten-6 fallout, and green the full suite on Playwright 1.62

Live-app fix (Place Footprints / routing dead in Chrome): submodule
bumps carry the coroutine ownership fix (kicad 012d95ecb4) and the
handler-exception survival fix (wxwidgets 1b5f0e31f4).

Emscripten-6 fallout:
- occ/ngspice worker wrappers: mainScriptUrlOrBlob was removed
  upstream; pthread children re-run the wrapper blob, so an em-pthread
  realm now importScripts the glue and gets out of the way (before:
  recursive service boots, pool never fills, silent 180s boot hangs —
  every occ spec and ngspice bg_run).
- Makefile.wasm: -sASYNCIFY frankenlinks on the no-wx coroutine repro
  targets ported to -sJSPI (the JSPI-only libcontext crashed at first
  yield under them); mainloop/gl repro pages drive their tick through a
  promising export (emscripten_set_main_loop callbacks cannot suspend);
  retired inject-dyncall-shims lines removed (targets were unbuildable
  since Phase 8); $stringToNewUTF8 force-included (the EM_ASM value
  bridge aborted the runtime on the first decoded exception).
- fiber-park levers: neither embind shape can drive suspending levers
  (plain throws on strict-JSPI Firefox; emscripten::async() re-executes
  its invoker on settle) — kept sync for manual Chromium probing, spec
  coverage moved to the jspi-coroutine harness (18 cases).

Suite work:
- Playwright 1.61.1 -> 1.62.1 (Firefox 153: JSPI on by default).
- fiber-resume-park.spec retired -> coroutine-lifecycle.spec: census
  gate over boot / board load / chooser open / cancel (deterministically
  red on the pre-fix build).
- Blind asyncify-era pins re-keyed: quasimodal-strand + wait-beacons
  beacon regexes, footprint-chooser-close liveness -> wx parking-timer
  heartbeat (scheduler counters idle flat on Firefox).
- occ/ngspice test providers: 60s boot timeout + worker error
  surfacing (a worker death used to be a silent 180s timeout).
- Harness pages: stale 9.99 config dir -> 10.0 (library_manager wxCHECK
  noise, chooser had no libraries).
- gal-webgl harness: missing artifacts rebuilt (boost/glm extracted to
  the host sysroot), PgmOrNull stub added for the rebased GAL.
- jspi-scheduler: clean-shutdown console line restored (app-quit
  contract), quarantine never yanks SP from a live window.

Gates: test:e2e 699 passed / 0 failed (wx-chromium, kicad-firefox,
kicad-chromium, jspi-firefox, coroutine-firefox); web ff/cr/mobile 71
passed; lint:ci-coverage 166, lint:determinism 163, screenshots
manifest 492 current, corpus 7/7, tools:contract green. Offline
screenshot baselines show expected mass drift from the engine bump —
re-baseline (screenshots:noise -> promote) is a follow-up.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016X9eh1s5sTx1o9Em9KBuwR

tests/kicad/quasimodal-strand.spec.ts

@@ -298,21 +298,22 @@ test.describe("quasi-modal strand (doc 19)", () => {
     expect(await dialogCount(page)).toBeGreaterThan(0);
     await okButtonCenter(page);
 
-    // RE-PINNED AT THE FLIP (docs/features/async/22 §10, 2026-08-08). The
-    // overlap this staging proved (a timer park on top of an open-ended park)
-    // required an in-place park for the timer to land on; post-flip every
-    // party is a scheduler context and D5 removed the main loop's in-place
-    // park, so the window is structurally impossible. The staging now pins
-    // the post-migration invariant: the dialog opens, the timer fires and its
-    // park survives (asserted above), and NO concurrent-park window is
-    // observable.
+    // RE-PINNED AT THE FLIP (docs/features/async/22 §10, 2026-08-08), and
+    // RE-KEYED for JSPI (2026-08-13): the `[wx-asyncify] concurrent-park|…`
+    // beacons retired with the asyncify scheduler, which made the old filter
+    // vacuous. The post-migration invariant is the same — the dialog opens,
+    // the timer fires and its park survives (asserted above) — and the
+    // observable JSPI failure modes of an overlap are ghost/refused
+    // transitions, a stuck-window force-clear, or a job-tick trap.
     const overlapBeacons = testLogger.consoleLogs.filter((l) =>
-      /\[wx-asyncify\] (concurrent-park|aliased-wake-live|overlapped-wake)/.test(l),
+      /\[libctx-jspi\] ghost\/refused transition|\[wx-scheduler\] (force-clearing stuck window|job tick error)/.test(
+        l,
+      ),
     );
     console.log(`[STRAND] staging overlap beacons: ${overlapBeacons.length}`);
     expect(
       overlapBeacons.length,
-      "no concurrent-park window is observable post-flip",
+      "no ghost/stuck-window/job-tick anomaly is observable post-flip",
     ).toBe(0);
   });