Plugin uninstall keeps files other plugins still use and reports what it removed

What

Removing plugins is more careful about files and settings that other installed plugins still need. This applies both to uninstalling one plugin and to removing all plugins from a marketplace, which is a catalog plugins are installed from. It also reports more clearly what it did.

• Removing a marketplace's plugins now returns installPathsStillInUse. This is the list of install folders that plugins from other marketplaces still depend on, and those folders are left in place.
• When Claude Code cannot tell which plugins are installed, a plugin's shared data is treated as still in use and is not deleted.
• Removing dependencies that were installed automatically now goes through a separate planning step first. That step decides whether the data folder is deleted and which installed plugins still count.
• Deleting a plugin's data folder no longer forces removal. The result is now removed, absent if the folder was already gone, or failed, with the message "Failed to delete plugin data dir".
• Uninstall results now include dataDirKept, directoryNameNote, optionsRemoved and dataFolderUser, which say whether the plugin's data folder was left in place and give related details.
• A scope is the level a plugin is installed at, such as your user or a project. If the plugin is not installed at the scope you asked for, uninstall tries another scope before it fails.
• The enabledPlugins setting is rewritten only when it actually has a matching entry. An entry that another installed plugin shares is not cleared.

Why

Uninstalling one plugin should no longer delete files or settings that another installed plugin still relies on. Cleanup can also now tell a folder that was already gone apart from one it could not delete.