Valerio 248da0abc4 fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing ... The published bin was named `webclaw-mcp`, which npx shadows with any existing `webclaw-mcp` on PATH (Homebrew/cargo/create-webclaw) — so `npx @webclaw/mcp` silently ran a stale binary instead of the launcher, for exactly our existing CLI users. Rename the bin to the unique `webclaw-mcp-launcher`; `npx @webclaw/mcp` still resolves the single bin. Verified end-to-end: with a stale webclaw-mcp on PATH, npx now runs the launcher and returns 14 tools. - bin: webclaw-mcp -> webclaw-mcp-launcher; version 0.6.15 -> 0.6.16 - mark webclaw-mcp.mjs executable - release.yml: version the launcher INDEPENDENTLY of the core release (a launcher-only fix must ship without a core bump) — publish the next patch above the current npm version and pin RELEASE_TAG to the release tag - server.json: sync to 0.6.16 Published + deprecated 0.6.15 (bin collision); 0.6.16 is the first good release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-22 08:53:29 +02:00
..
create-webclaw	fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing	2026-07-22 08:53:29 +02:00
webclaw-mcp	fix(mcp): rename @webclaw/mcp bin to avoid npx PATH shadowing	2026-07-22 08:53:29 +02:00