Plugin list shows plugins from all project scopes, not just the current project

Description

When viewing installed plugins in Claude Code, plugins that are enabled in other projects' .claude/settings.json files appear in the plugin list — even when the current project does not have them enabled. There is no indication of which scope each plugin belongs to.

Steps to Reproduce

1. Enable a plugin (e.g. my-plugin) in Project A's .claude/settings.json
2. Enable the same plugin in Project B's .claude/settings.json
3. Open Project A in Claude Code and view the installed plugins

Observed Behavior

The plugin appears multiple times in the list — once for each project scope where it is enabled — with no label indicating which project/scope each entry belongs to. This makes it look like the plugin is installed multiple times or that foreign plugins are active in the current project.

Expected Behavior

The plugin list should either:

• Only show plugins active in the current context (global scope + current project scope), or
• Clearly label each entry with the scope it belongs to (e.g. "Project: hypeguard-flutter-onsite-app")

Context

• Using per-project plugin scoping via .claude/settings.json \enabledPlugins\ field
• The same plugin enabled across 5 different projects results in 5 entries in the UI with no distinguishing information