Under the hood
No documentation found
New plugin UI plumbing routes ui.message and press/input/select events to a desktop app surface
What
Two new internal functions dispatch plugin-authored UI events, including ui.message and press/input/select events, to a message target marked as surface: "desktop". Before dispatching, they check whether the relevant UI component (Q4.isDrawn) is actually drawn, and log a message noting 'nothing ran' when it isn't.
Why
This appears to add the plumbing needed for plugin-driven UI events to reach a desktop client interface, separate from the terminal-based UI, though what desktop surface consumes these events isn't detailed in the evidence.
Names in the bundleui.messageui.pressui.inputui.select
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What specific desktop client or surface consumes these dispatched events isn't detailed in the evidence.