v2.3.2

Fixed

• Fixed @mcp-b/chrome-devtools-mcp@latest publishing with an unbundled build/src/third_party/index.js, which caused clean npx launches to fail with ERR_MODULE_NOT_FOUND for core-js and other bundled dependencies.
• Added a prepublishOnly gate for @mcp-b/chrome-devtools-mcp so publish runs npm run bundle and package verification before npm accepts the tarball.
• Hardened npm package verification to inspect the packed tarball, reject unresolved ../../node_modules imports in bundled entrypoints, install the tarball in an isolated temp project, import both bundled third-party entrypoints, and load CLI help.

Verification

• Published @mcp-b/chrome-devtools-mcp@2.3.2 to npm and moved latest to 2.3.2.
• Verified a fresh install can import build/src/third_party/index.js and build/src/third_party/devtools-formatter-worker.js.
• Verified npx -y -p @mcp-b/chrome-devtools-mcp@latest chrome-devtools-mcp --help starts without ERR_MODULE_NOT_FOUND.

Related: #209, #164