GamePKG 0.1.11 — Separate game processes and windows

Play now opens each game in its own process and window, named for the game. The GamePKG library remains available, and closing the library leaves running games open. Both native and explicit Wasm playback use the separate player.

The player owns its renderer and audio. Native game code retains its restricted worker process. Closing the game normally finishes progress saving; the library refreshes play history when the player exits. Remembered ROM selections and explicit native/Wasm target choices are passed through the launcher.

Validated locally: 195 Rust tests, formatting and Clippy, separate process/window IDs, actual keyboard gameplay and achievement persistence, continued gameplay after the library process closes, normal OS window close with saved play time, remembered per-game ROMs, Vulkan shader/texture pixels, an extracted release build/play, and Windows CLI startup. Linux and Windows archives include matching checksums and dependency notices/source. No private ROMs or signing keys are included.

Direct native game compilation remains Linux-only. Windows retains explicit Wasm build/play with its configured Linux compiler exchange.