v2.2.1 — Fold Sci-Hub install into setup-sources

Simplification

The dedicated /knowledge-vault:setup-scihub command is removed. Sci-Hub now installs through the same /knowledge-vault:setup-sources flow as every other recommended MCP — selecting it triggers a Sci-Hub-specific sub-procedure (disclaimer + explicit consent + uv tool install + claude mcp add scihub -s project + per-vault marker file).

Why

Having one MCP with its own dedicated install command was inconsistent with how Zotero, arXiv, Consensus, Paper Search, and Unpaywall are all configured. setup-sources is the canonical entry point for MCP setup; Sci-Hub belongs there too.

What stays the same

All the safeguards from v2.2.0 are preserved:

• Explicit yes required after the disclaimer.
• Project-scope MCP registration (-s project) — Sci-Hub never enabled user-globally.
• Per-vault marker file .vault/.scihub-enabled as the opt-in gate.
• Disable: rm .vault/.scihub-enabled && claude mcp remove scihub.

What changes

	v2.2.0	v2.2.1
Install command	/knowledge-vault:setup-scihub	/knowledge-vault:setup-sources (select Sci-Hub)
enrich-references trailing tip	"run /knowledge-vault:setup-scihub"	"run /knowledge-vault:setup-sources and select Sci-Hub"
README Supported servers row	Setup column = /knowledge-vault:setup-scihub	Setup column = run /knowledge-vault:setup-sources
Number of slash commands	+1 (setup-scihub)	unchanged from v2.1.x

Migration

If you already enabled Sci-Hub via v2.2.0's /knowledge-vault:setup-scihub, nothing breaks — the MCP is still registered and the marker file still exists. You just won't be able to re-run setup-scihub (it's gone). Re-running would be redundant anyway since the marker check skips already-enabled vaults.