A plugin hook that fails to load no longer keeps failing on every later attempt.
What's wrong with this entry?
When loading a plugin's hook module throws, the cached registration is cleared before the error is rethrown, so a later attempt starts clean instead of replaying the failure. Hook enablement also gained an admin guard input next to the existing checks for hooks disabled, managed-only and all-disabled.
- The admin guard value is part of the fingerprint used to decide when plugin state has changed.
- Built-in hook notifications are now installed through the worker platform, and the old in-process scanner that inspected plugin hook module source was removed.
guardHeldByAdmin: V_t(),
Strings lifted out of the shipped bundle, so the claim above can be checked against them.