v0.3.1 — the installed plugin could not start

Fixes the plugin shipped hours ago in 0.3.0. Installing it succeeded and then claude mcp list reported the server as Connection closed.

Claude Code installs an npm-sourced plugin by extracting the tarball, and does not run npm install in the cache directory — so there is no node_modules beside the extracted dist. Running the entry point in place died on ERR_MODULE_NOT_FOUND for @modelcontextprotocol/sdk, which the MCP transport surfaces only as a closed connection, naming nothing.

The server now launches through npx, which fetches the package with its dependencies and runs the declared bin. The version is pinned, and the release script rewrites that pin alongside the manifest version — an unpinned npx would fetch whatever is newest when the server spawns, which is a different build than the manifest describes and undoes the point of syncing them.

Why 0.3.0 shipped broken, since it is the more useful part: it was verified with claude --plugin-dir ., which loaded the plugin and registered all four tools cleanly. That passes against a checkout because a checkout has node_modules. The working configuration and the broken one are indistinguishable under --plugin-dir, and only installing it for real tells them apart. The test that replaces that check now asserts the launch method rather than the load.

/plugin marketplace add priyanshuN/triago
/plugin install triago@triago

Already installed? /plugin update triago@triago.

No schema, card-format or API change.