Under the hood
Hover styling supports named scopes, and passing a class instance as props is now rejected
What
In the terminal UI's layout components (Box, Text, Button), hover styling rules can now target a named scope group instead of only ever applying to the nearest matching container. Separately, passing a class instance (rather than a plain object) as props now triggers a rejection with the message "is not a plain object (a class instance)", checked before hover styling is validated.
Why
The named scopes give the UI more flexibility in how hover effects are grouped and targeted. The new rejection catches a category of invalid input earlier, before it can cause confusing downstream errors.