Under the hood
Plugin rendering now tracks hover across plugin boundaries, not just draw ownership
What
When a plugin's render hook returns a UI component that was actually drawn by another plugin, and that component has a hover property, the rendering engine now records a hover-scope binding tying the hover state to that other plugin. Previously this situation was only checked to validate which plugin was allowed to draw the component, without tracking hover across the boundary.
Why
This lets hover state work correctly when one plugin reuses or wraps a component drawn by another plugin, rather than only enforcing draw ownership.