fix(wineCtx): Prevent TypeError from non-atomic game.runtime access

[sentry]

Summary

This PR addresses issue RUST-G, fixing a TypeError: undefined is not an object (evaluating 'game.runtime.runtime') originating in the wineCtx function. The error was caused by a reactivity race condition in a Svelte 5 reactive context, where game.runtime could re-evaluate to undefined between non-atomic accesses.

Changes

• Cached the result of game?.runtime into a local variable (r) within the wineCtx function.
• Modified wineCtx to use the cached r for both the null-check (!r) and the subsequent property access (r.runtime), ensuring atomic access.

Testing

• cargo test -p corkscrew passes
• npx svelte-check --threshold error passes
• Manually tested with cargo tauri dev (if UI changes)

Notes

The root cause was a reactivity race condition specific to how Svelte 5 handles reactive objects (Proxies). Accessing game.runtime twice non-atomically allowed the runtime property to become undefined between the initial check and subsequent use, leading to the TypeError.

Fixes RUST-G

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.