Wasm corpus: surface evaluator runner errors in CI summaries

Prior CI examples:

• https://github.com/zig-utils/zig-js/actions/runs/29693769324/job/88210905193
• https://github.com/zig-utils/zig-js/actions/runs/29693769324/job/88210905788
• https://github.com/zig-utils/zig-js/actions/runs/29693769324/job/88210905194

Parent: #268 Related: #264, #265, #273, #287 Roadmap: #142, #134

The Core 2, SIMD, and Threads smoke jobs reported only aggregate runner-error counts. Inventories contained each evaluator stderr detail but lived only in RUNNER_TEMP, so the retained log could not diagnose an all-runner failure.

Commit 89199ae3 prints at most three unique runner details per affected file, truncates each to 2,000 characters, and leaves inventory records and aggregate accounting unchanged.

Acceptance:

• Print a bounded set of unique runner-error details beside each affected file summary.
• Keep inventories and pass/fail accounting compatible.
• Avoid duplicating identical errors once per command.
• Pass the parser/orchestrator unit suite: 12/12.
• Use replacement CI detail to identify the underlying Linux evaluator failure; the eager memory64-only prelude import is fixed separately by #320.

Follow-up 4ef6a881 makes wasm-spec-eval report the actual thrown JavaScript error name and message without invoking user code. The evaluator build passes, and a direct witness now prints evaluation failed: Throw: TypeError: diagnostic witness. The next Linux smoke will expose the underlying profile exception.

Replacement run 29697212135 surfaced the concrete shared cause: TypeError: WebAssembly memory64 is disabled before every corpus command. #320 now tracks the root fix and replacement-smoke gate; #319 bounded durable diagnostics are complete on main through 4ef6a881.