Under the hood
Engine events during a query are now deferred to a frame boundary instead of applied immediately
What
In the main query-turn handler, incoming engine events used to be applied straight away. They are now routed through a frame notifier that defers applying them until a frame boundary is reached.
Why
Deferring event application this way changes the timing of when state and UI updates take effect during a turn, though the finding doesn't specify the visible effect.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What user-visible difference this timing change produces is not stated.