What
Plugins can now be enabled or disabled at specific scopes (user, project, local), with validation for managed plugins.
Details
- Enabling/disabling a plugin now persists the setting at the appropriate scope
- Managed plugins (from enterprise policy) cannot be enabled or disabled — only updated
- If a
--scopeargument is provided but doesn't match the plugin's actual scope, a helpful error message is shown - Success messages include the plugin name and scope:
"Successfully enabled plugin: X (scope: user)"
Evidence
Plugin scope management (search for "Managed plugins cannot be" and "is installed at")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.