Fix: timer created inside wait/pause/ask/menu callback never fires

[alexwarren]

Summary

• A user reported a game (using a wait { SetTimeout(8) { wait { Ask(...) } } } pattern) that works on the Quest 5 desktop player but hangs forever on WebPlayer and WasmPlayer after the initial "Continue" prompt.
• Root cause: FinishWait, FinishPause, SetQuestionResponse, and SetMenuResponse in WorldModel never called SendNextTimerRequest() after running their callback script, unlike every other turn-ending path (SendCommand, Tick, SendEventCore, BeginInternalAsync). WebPlayer/WasmPlayer rely on the RequestNextTimerTick event to know when to next poll the engine for elapsed timers — a timer created during one of these callbacks (e.g. via the SetTimeout core function) was never scheduled, so it silently never ran. The desktop player isn't affected because it polls its own clock instead of relying on this push event.
• Fix: call SendNextTimerRequest() at the end of all four methods, matching the existing pattern elsewhere in the file.

Test plan

• Added Wait_CallbackCreatesTimer_RequestsNextTimerTick regression test (tests/EngineTests/CallbackTests.cs) plus a testwaittimer fixture command, asserting the host is notified via RequestNextTimerTick after a wait callback creates a timer.
• Verified the new test fails without the fix and passes with it.
• dotnet test — all 318 tests across every test project pass.
• Full solution build succeeds.

🤖 Generated with Claude Code