2 Commits

Author	SHA1	Message	Date
funman300	2cf728210e	feat(e2e): add window.__FERROUS_DEBUG__ bridge to /play for automation ... play.html now loads solitaire_wasm.js alongside the Bevy canvas and exposes the same window.__FERROUS_DEBUG__ object as /play-classic. The bridge runs an independent SolitaireGame (WASM logic layer) seeded from ?seed= / ?draw3= URL params; Bevy renders the visual game in parallel without coupling. Methods exposed: seed, state, legalMoves, moveHistory, snapshot, applyLegalMove, applyMove, draw, undo, serialize, fromSaved, newGame, failureReport, replayPayload, runAutoplay — matching the /play-classic contract so the shared Playwright harness targets either route without modification. cycle_metrics.js: add --route play-classic|play flag (default play-classic). Routes to /${route}?seed=N. The resume-overlay clear step is skipped for /play since the Bevy build uses localStorage-backed WasmStorage, not a #resume-overlay element. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-02 13:41:07 -07:00
funman300	835a48fe9d	feat(web): add solitaire_web Bevy WASM build targeting play.html canvas ... Adds a new `solitaire_web` crate that compiles the full `solitaire_engine` to `wasm32-unknown-unknown` and renders to a `<canvas id="bevy-canvas">` element in `play.html` — the same ECS code path as desktop and Android. Changes to enable the WASM target: - .cargo/config.toml: add wasm32-unknown-unknown rustflags for getrandom - Workspace Cargo.toml: add solitaire_web member - solitaire_data/Cargo.toml: gate tokio/reqwest/dirs/keyring to non-wasm - solitaire_data/src: add wasm32 branch to data_dir() (returns None); cfg-gate sync_client network types, auth_tokens, matomo_client - solitaire_engine/Cargo.toml: gate tokio/reqwest/kira/arboard/dirs/zip to non-wasm (mio/cpal/arboard don't compile for wasm32-unknown-unknown) - solitaire_engine/src/lib.rs: cfg-gate module declarations and re-exports for analytics, audio, sync, sync_setup, avatar, leaderboard plugins - solitaire_engine/src/core_game_plugin.rs: cfg-gate plugin registrations that require TokioRuntime (audio, sync, analytics, leaderboard, avatar) - solitaire_engine/src/resources.rs: cfg-gate TokioRuntimeResource - solitaire_engine/src/game_plugin.rs: cfg-gate std::fs::remove_file (x10) - solitaire_engine/src/theme/mod.rs: cfg-gate importer module (uses dirs+zip) - solitaire_engine/src/settings_plugin.rs: cfg-gate theme ZIP import UI - solitaire_engine/src/assets/sources.rs: cfg-gate FileAssetReader/user_theme_dir - solitaire_engine/src/auto_complete_plugin.rs: cfg-gate audio system - solitaire_engine/src/daily_challenge_plugin.rs: cfg-gate server fetch - solitaire_engine/src/hud_plugin.rs: cfg-gate AvatarResource import - solitaire_engine/src/profile_plugin.rs: cfg-gate AvatarResource import - solitaire_server/web/play.html: minimal HTML canvas shell - solitaire_web/: new crate (Cargo.toml + src/lib.rs) - build_wasm.sh: add Bevy WASM build step (cargo + wasm-bindgen + wasm-opt) All tests pass; clippy --workspace -- -D warnings clean; native build (solitaire_engine, solitaire_app) unaffected. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-01 13:46:45 -07:00