[BUG]/plugin Disable/Enable toggle targets wrong settings key when plugin manifest name differs from marketplace directory name

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?

The astronomer-data plugin (from the claude-plugins-official marketplace) is installed under the marketplace directory data-engineering, but its
.claude-plugin/plugin.json declares:

{
"name": "astronomer-data",
"version": "0.1.0",
...
}

The plugin is tracked in ~/.claude/plugins/installed_plugins.json and ~/.claude/settings.json under the directory-derived key
data-engineering@claude-plugins-official, e.g.:

"enabledPlugins": {
"data-engineering@claude-plugins-official": true
}
But the /plugin UI displays/operates on it as astronomer-data@claude-plugins-official — i.e. it's using the manifest's name field instead of the actual registry key.

What Should Happen?

It should be possibleto disable the plugin normaly

Error Messages/Logs

Steps to Reproduce

1. Install/enable the astronomer-data (data-engineering) plugin from claude-plugins-official.
2. Open /plugin → select the plugin (shown as "astronomer-data", Status: Enabled). 3. Click "Disable".

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.185 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

<img width="2108" height="996" alt="Image" src="https://github.com/user-attachments/assets/8cea03a0-2174-4219-b570-9b9f18ed891b" />