Plugin uninstall does not fully clean up across all scopes

Summary

When a plugin is installed at multiple scopes during testing (local + user), /plugin uninstall only removes one scope. The enabledPlugins entry remains in other settings files, causing the plugin to appear as still installed.

Steps to Reproduce

1. /plugin install plugin-name@marketplace — select "Install for you (user scope)"
2. /plugin install plugin-name@marketplace — select "Install for you, in this repo only (local scope)"
3. /plugin uninstall plugin-name@marketplace — removes from one scope
4. Plugin still appears as installed (entry remains in the other settings file)

Expected Behavior

Either:

• /plugin uninstall removes the plugin from all scopes where it is installed
• Or /plugin uninstall prompts the user to select which scope(s) to uninstall from (similar to the install prompt)
• No orphaned enabledPlugins entries should remain after uninstall

Current Workaround

Users must manually edit ~/.claude/settings.json or .claude/settings.local.json to remove the leftover enabledPlugins entry.

Environment

• Windows 11 Pro
• Claude Code CLI