Under the hood
Useful3 Signal2
Permission and dialog prompts can no longer act on stale theme or permission settings.
What's wrong with this entry?
Anonymous. No account, no email.
What
The code that routes tool-permission and user-dialog requests became two objects kept for the session rather than callbacks rebuilt on every render, so it can no longer act on a stale view of the theme, tool registry or permission settings. The same responses are still sent, including the "User aborted" deny and the deny on unmount.
Evidence
Permission dispatcher unmounted
Strings lifted out of the shipped bundle, so the claim above can be checked against them.