Rotifer v0.8.5: Ecosystem alignment — one version number across every tool

The Rotifer project released v0.8.5 of @rotifer/playground on npm, aligning the CLI, MCP Server, VS Code extension (on both VS Code Marketplace and Open VSX) and rotifer.dev docs to a single shared version number. The release adds no new features but fixes previously divergent version reporting across entry points, documents the `rotifer wrap --from-clawhub` migration path, and makes the CLI notify users when a newer version is available.

Written up on 2026-10-19. v0.8.5 shipped on 2026-04-08 with a changelog entry but no blog post at the time. v0.8.5 adds no new features. It fixes a different kind of problem: the project's entry points each reported a different version. Before this release, the CLI, the MCP Server, the VS Code extension, and the rotifer.dev docs each showed their own version, and the install snippets pointed in different directions. A simple question was hard to answer: "Are the things I installed all from the same release?" @rotifer/playground v0.8.5 is available on npm. From v0.8.5 on, these four entry points point to the same version: npm install -g @rotifer/playground CLI npx @rotifer/mcp-server MCP Server Plus the VS Code extension in sync on both VS Code Marketplace and Open VSX and the docs and install instructions on rotifer.dev. The commands you read in the docs and the tools you install are the same release. rotifer wrap --from-clawhub wraps a ClawHub Skill as a Gene in one command. It already worked earlier in the v0.8.x cycle but had no complete public documentation. v0.8.5 puts the migration path and its guide into the rotifer.dev docs. When a newer version is out, the CLI tells you, so you don't have to check npm yourself. Extension metadata on VS Code Marketplace and Open VSX now carries the same version number, so one marketplace no longer lags behind the other. Much of the trust in a developer tool comes from the docs matching what you actually installed. When version numbers disagree, users start wondering whether the install guide is stale and which docs to read when something breaks. v0.8.5 lines the entry points up, and every later release moves forward from that one line. See the changelog https://rotifer.dev/docs/changelog/ for the full list. If you are starting with Rotifer today, install the latest version: npm install -g @rotifer/playground@latest This article was originally published on rotifer.dev https://rotifer.dev/blog/v0.8.5-ecosystem-alignment . Follow the project on GitHub https://github.com/rotifer-protocol/rotifer-playground or install the CLI: npm i -g @rotifer/playground .