Integrate WASM Compilation Target for Browser Play

[Mkalbani]

Description

Configure the quest-rust project to compile to WebAssembly so the game can run in a browser environment without any server-side execution. This dramatically expands reach — players who do not want to install a Rust binary can play directly in the browser. The WASM build should expose a clean JavaScript API wrapping the core session, puzzle, scoring, and hint modules, with the TUI layer replaced by a JS-driven frontend.

Acceptance Criteria

• wasm-bindgen and wasm-pack are added and configured in Cargo.toml with a [lib] target
• A wasm feature flag gates WASM-specific code paths to avoid breaking the native build
• wasm-pack build --target web produces a valid pkg/ output with .wasm and JS bindings
• Exported JS functions cover: startSession(puzzleId), submitAnswer(answer), revealHint(), getScore(), endSession()
• std::time is replaced with web-sys time APIs under the wasm feature flag
• File I/O in the persistence module is replaced with localStorage access under the wasm feature flag
• A minimal index.html demo in web/ loads the WASM module and runs a complete puzzle session in the browser
• CI builds both cargo build (native) and wasm-pack build to prevent regressions on either target

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[Truphile]

Hi team, I’d love to take this on!

I am a software engineer experienced in Rust/WASM compilation pipelines, cross-target compilation gating, and browser-native performance optimization. I am ready to transition the core execution layer into a browser-runtime module.

I will deliver:

Cross-Target Compilation Layer (Cargo.toml): Introduce wasm-bindgen and wasm-pack configurations with a clear [lib] target. I will isolate WASM code paths behind a dedicated feature flag to guarantee the native TUI binary engine continues to compile without regressions.

JavaScript Interop Bindings: Expose high-level JS hooks wrapping the primary session loop (startSession, submitAnswer, revealHint, getScore, endSession), passing structured session metrics gracefully across the boundary.

Browser Sandbox Shims: Conditionalize environmental system calls under the WASM flag: replacing std::time clocks with web-sys::window().performance().now() and shifting disk-bound state persistence over to web_sys::Storage (localStorage).

CI Integration & Static Demo: Provide a lightweight index.html integration proof within the web/ directory to demonstrate cross-platform execution, and append target compilation steps to our CI pipeline to continuously enforce compilation safety across both environments.

Ready for assignment to drop a clean, cross-compiled PR immediately!

[Codekill33]

Hello, I'd like to work on this issue. I'll add WebAssembly support with wasm-bindgen and wasm-pack, expose the required JavaScript API, implement browser-specific storage and timing, add a demo page, and update CI to build both native and WASM targets. Kindly assign this issue to me. Thank you

ETA ~ 12 hours

[DevSolex]

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

[xJeffx23]

Hi team! 👋

My name is Jefferson. I have experience with Rust, WebAssembly concepts, JavaScript interoperability, modular application architecture, and CI workflows, along with previous open-source contributions.

I'd like to work on this issue by configuring the project for WebAssembly, introducing feature-gated platform-specific implementations, exposing a clean JavaScript API with wasm-bindgen, adapting the persistence and timing layers for the browser, adding a minimal browser demo, and ensuring both native and WASM builds are validated in CI.

I'd love the opportunity to contribute to this project. Thank you!

[grantfox-oss]

🦊 GrantFox — @Codekill33 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #49)
2. Your PR will be reviewed by the MindFlowInteractive maintainers

Good luck! Track your progress on GrantFox.