fix(web): regenerate stale WASM artifacts against current master

The committed `solitaire_server/web/pkg/` artifacts (canvas.* and
solitaire_wasm.*) were last built 2026-06-02 (8b262af) and predate the entire
card_game/klondike migration (#82–#90) plus the v4→v5 save-schema change. The
deployed WASM therefore no longer matched the current source, the JS API glue,
or the HTML (play.html changed in 2cf7282) — which is why the web build was
broken even though the wasm crates compile cleanly on `wasm32-unknown-unknown`.

Rebuilt all four artifacts via build_wasm.sh (wasm-pack 0.14.0,
wasm-bindgen CLI 0.2.120 matching the crate). The regenerated solitaire_wasm.js
and canvas.js glue confirm the API drift (the replay move currency became
KlondikeInstruction in #89).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

solitaire_server/web/pkg/solitaire_wasm.js

@@ -244,11 +244,11 @@ export class SolitaireGame {
         return this;
     }
     /**
-     * Returns replay moves encoded in the `solitaire_data::Replay` wire format.
+     * Returns replay moves encoded in the `solitaire_data::Replay` wire format
+     * — a list of upstream [`KlondikeInstruction`]s.
      *
-     * This derives move counts from the deterministic instruction history and
-     * validates that the resulting move stream replays cleanly from the current
-     * game's seed/draw mode.
+     * This is the deterministic instruction history; together with `seed()`
+     * and the draw mode it replays cleanly via `apply_instruction`.
      * @returns {any}
      */
     replay_moves() {