v0.1.3 — the package can actually start now

Fixes the bug that made every previous release unusable

@rikaidev/yomi has never been able to start when installed from npm. 0.1.0, 0.1.1 and 0.1.2 all died instantly:

Error [ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING]: Stripping types is
currently unsupported for files under node_modules, for ".../src/mcp/server.ts"

The package shipped TypeScript sources, and Node deliberately refuses to strip types under node_modules. The MCP server crashed on startup, so clients showed no tools — which looked like "Yomi won't install" and got misdiagnosed as a Cowork / Windows / MSIX / bun problem. It was none of those.

If you tried Yomi before and it silently did nothing: that was this bug, not you.

What changed

• The tarball now ships compiled JavaScript (dist/), not TypeScript sources
• serverInfo.version reports the real version (was hardcoded 0.1.0)

Why it survived three releases

Yomi was only ever run from a repo checkout — where type-stripping applies, and where bun runs .ts natively anyway. The documented path, npx @rikaidev/yomi, was never once executed. CI "smoke-tested" --help, the one command that prints a literal string without importing any application code, and it ran against the last published version rather than the commit under test.

Gates so it cannot happen again

CI now packs the tarball from each commit, installs it into a clean project, rejects any tarball containing src/, starts it as a real MCP stdio server, and asserts an initialize handshake — on Linux, macOS and Windows. Publishing refuses to ship a tarball that cannot complete that handshake.