fix(wasm): non-suspending clipboard predicate; kicad baselines for the DOM port

- wxwidgets -> 25281178d2: wxClipboard::IsSupported answered via a 2 s
  Asyncify suspend on KiCad's idle path; overlapping suspensions
  corrupted Asyncify.currData ('indirect call to null'/'signature
  mismatch' storms after every document load — bug 2 of features/async).
  It now answers synchronously. The storms and 2 s UI stalls are gone.
- 58 kicad screenshot baselines regenerated from the green run (the old
  set was canvas-only and died with the canvas port).
- visual-notes: bug 29 + the known-red list — the 10 file-loading kicad
  specs (load-pcb, collab bridges, eeschema-ui keyboard/dialog) remain
  red on the unfixed asyncify substrate (bug 3, per-context currData
  authority). Bisect-verified pre-existing: binaries built from the
  pre-consolidation wx tree fault identically. Greening them is the
  async feature's exit criterion, deliberately out of scope here.

Gates: wx e2e 292/0/1 skipped; kicad 32 passed / 10 known-red / 2
skipped (parity +1 with pre-consolidation, minus the timeout storms).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/features/wx-dom-port/visual-notes.md

@@ -214,3 +214,24 @@ pre-consolidation tree, which failed identically):
       page.mouse. The minimal-app comprehensive spec drives the wxChoice
       through its native <select> (browsers own that popup; it cannot be
       coordinate-clicked).
+  29. wxClipboard::IsSupported suspended for up to 2 s per call
+      (EM_ASYNC_JS readText raced vs timeout) on KiCad's idle path;
+      overlapping suspensions clobber Asyncify.currData → "indirect call
+      to null"/"signature mismatch" storms after a document loads (bug 2
+      of features/async on main; fix was designed in May, landed now).
+      The predicate answers from the cache, else "Clipboard API
+      available".
+
+### Known-red kicad specs (asyncify scope, NOT this feature)
+
+The 10 file-loading kicad specs (load-pcb, pcbnew-collab, eeschema-collab,
+eeschema-ui Backspace/Delete/text-dialog) sit on the unfixed asyncify
+substrate: a single corrupting fault still fires at document load (fiber
+swap crossing the parked main loop — bug 3 / per-context currData
+authority in features/async designs A/B) and breaks subsequent keyboard
+and collab-commit processing. Bisect-verified pre-existing: eeschema
+binaries built from BOTH the pre-consolidation and post-consolidation wx
+trees fault identically; binary timing decides whether the race is lost,
+so any rebuild can flip these specs. They were red before this
+consolidation (the "31 passed" gates) and stay red after it; greening
+them is the async feature's exit criterion.