[BUG] Official plugins cannot be enabled in multiple projects via CLI

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

## Bug Description
Official plugins from claude-plugins-official (context7, feature-dev) cannot be enabled in a second project via the CLI. Once enabled in one project, they disappear from the "Discover" list in other projects.

## Steps to Reproduce

1. Enable context7@claude-plugins-official in Project A via /plugin
2. Navigate to Project B
3. Run /plugin → Discover tab
4. context7 and feature-dev are not listed as available to enable

## Additional Issues

• Attempting to uninstall with --scope local fails: "Plugin is not installed in local scope"
• Attempting to uninstall with --scope user fails: "Plugin not found in installed plugins"
• The UI shows "Scope: local" and "Status: Enabled" contradicting the error messages

## Expected Behavior
Official plugins should be independently enableable in any project via the CLI, regardless of their status in other projects.

## Environment

• Claude Code v2.1.1
• macOS

## Workaround
Manually creating .claude/settings.local.json in each project works, but the CLI should handle this properly.

What Should Happen?

Official plugins should be independently enableable in any project via the CLI, regardless of their status in other projects.

Error Messages/Logs

Steps to Reproduce

1. Enable context7@claude-plugins-official in Project A via /plugin
2. Navigate to Project B
3. Run /plugin → Discover tab
4. context7 and feature-dev are not listed as available to enable

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

v2.1.1

Platform

AWS Bedrock

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_