[DOCS] Plugin installation troubleshooting missing `range-conflict` dependency guidance

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugin-marketplaces

Section/Topic

Plugin installation failures troubleshooting, plus the plugin install command docs for dependency conflict behavior

Current Documentation

The docs currently say:

Symptoms: Marketplace appears but plugin installation fails Solutions: Verify plugin source URLs are accessible Check that plugin directories contain required files For GitHub sources, ensure repositories are public or you have access Test plugin sources manually by cloning/downloading

And the install flow documentation says:

Once you've added marketplaces, you can install plugins directly (installs to user scope by default):

Install a plugin from available marketplaces.

There is no documentation explaining dependency version conflicts with already-installed plugins, and no mention of the range-conflict result.

What's Wrong or Missing?

Changelog v2.1.113 says: Fixed plugin install succeeding when a dependency version conflicts with an already-installed plugin — now reports range-conflict.

That is a user-visible plugin installation outcome, but the current docs only describe generic install syntax and generic installation failures. They do not explain:

• that plugin installation can fail because a dependency's required version conflicts with an already-installed plugin
• that Claude Code now reports this case as range-conflict instead of succeeding
• how users or marketplace authors should resolve the conflict and retry installation

Without this, users can hit a new documented-by-behavior failure mode with no troubleshooting guidance.

Suggested Improvement

Add a specific troubleshooting item for dependency version conflicts under plugin-marketplaces and cross-reference it from the plugin install command docs.

Suggested content:

• define when range-conflict occurs during plugin installation
• clarify that the conflict can come from an already-installed plugin dependency
• explain the expected remediation steps: identify the conflicting installed plugin/version, update or remove the conflicting plugin, or install a compatible plugin version, then retry
• note that dependency installs triggered during /plugin install can surface this error

An example error snippet would make the failure mode easier to recognize.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/plugin-marketplaces | Plugin installation troubleshooting |
| https://code.claude.com/docs/en/discover-plugins | End-user plugin installation workflow |
| https://code.claude.com/docs/en/plugins-reference | claude plugin install CLI reference |

Total scope: 3 pages affected

Source: Changelog v2.1.113

Exact changelog entry: Fixed plugin install succeeding when a dependency version conflicts with an already-installed plugin — now reports range-conflict