docs: name the MCP packages tool by its bare name (#3207)

The stdio MCP surface advertises tools by their bare function name
(`packages`), not a `wheels_`-prefixed form — live-verified via
`wheels mcp wheels --once tools/list`. The packages guide was the last
v4-0-0 doc still calling it `wheels_packages`; the guide table, the
mcp() help text, and CLAUDE.md were already corrected on develop.

Signed-off-by: Peter Amiri <petera@pai.com>
Co-authored-by: Peter Amiri <petera@pai.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: 3 people

web/sites/guides/src/content/docs/v4-0-0/digging-deeper/packages.mdx

@@ -317,7 +317,7 @@ The install/update surface is covered by the commands shown earlier under [The a
 - `wheels packages add <name>@<version>` — pin a specific version; omit for the latest compatible.
 - `wheels packages add <name> --force` — overwrite an existing `vendor/<name>/`.
 
-The canonical verb is `add`. On the shell surface, `wheels packages install foo` is intercepted by LuCLI's built-in extension installer before it reaches the Wheels package handler, so it silently no-ops (the same trap that renamed `wheels browser install` to `wheels browser setup`). On v4.0.0 the same `install` argument also no-ops via the stdio MCP server (`wheels_packages`) and other in-process callers; the transparent `install` → `add` alias on MCP / in-process paths landed in v4.0.1 — see the v4.0.1 snapshot docs. Use `add` for compatibility across all 4.x releases.
+The canonical verb is `add`. On the shell surface, `wheels packages install foo` is intercepted by LuCLI's built-in extension installer before it reaches the Wheels package handler, so it silently no-ops (the same trap that renamed `wheels browser install` to `wheels browser setup`). On v4.0.0 the same `install` argument also no-ops via the stdio MCP server (the `packages` tool) and other in-process callers; the transparent `install` → `add` alias on MCP / in-process paths landed in v4.0.1 — see the v4.0.1 snapshot docs. Use `add` for compatibility across all 4.x releases.
 - `wheels packages update --all --yes` — bulk-update every installed package, no prompt.
 - `wheels packages registry refresh | info` — manage the 24-hour registry cache.