parity: 16 tests CRASH in the first full run since July 4 (tui/ink, fastify, cluster, gc-unsafe-zones, wasm, mysql)

[proggeramlug]

Companion to the parity dark-debt audit: 16 tests crash (signal/timeout — hard defects, not output nits) in the first complete parity run since 2026-07-04 (run 31964093732, merged 8-shard report):

• perry-tui/ink-compat family (7): test_perry_tui_inkcompat_{counter,useapp,useeffect,usefocus,usememo,useref}, test_issue_358_perry_tui_phase2_counter (Compile ink (React-based TUI framework) end-to-end via perry.compilePackages #348 area)
• fastify family (4): test_fastify_integration, test_issue_1240_fastify_request_json, test_issue_1293_fastify_request_json_as_any, test_issue_915_jwt_sign_after_async_route
• cluster: cluster_4962
• TUI demo: demo_claude_code_tui
• GC: test_issue_1425_gc_unsafe_zones — a GC-unsafe-zone witness crashing is worth an early look
• MySQL: test_issue_414_mysql_query_params
• WASM: test_wasm_add

Six weeks of merges are in the window (suite dark since 2026-07-04; see the audit issue for why). Each family needs a bisect; the GC and wasm ones are likely the highest-signal. Crash-class entries in known_failures.json cite THIS issue so they cannot be mistaken for cosmetic output gaps.