v0.4.1
A bug-fix and polish release.
Fixed
- Spec aliases now resolve instead of 404-ing. Tools accept the
long spec names agents commonly pass —ecma262/ecma402(plus
ECMA-262,es,intl) — and normalize them to the canonical
262/402before building the snapshot key. Previously
spec: "ecma262"produced a confusingMissing parsed spec object in R2: spec-ecma262-…error; an unrecognized spec now returns a
clearUnknown spec …message. - Clean stdio stream from the documented dev launch config. The
.mcp.jsonwiring that runs the server from local source now passes
npm run --silent mcp, so npm's lifecycle banner can't leak onto
stdout and corrupt the JSON-RPC stream a stdio MCP client reads.
Changed
- Reworded the project disclaimer from "unofficial / community
project" to "independent project — not an official Ecma International
or TC39 publication," across the README, docs landing page,
agent-facing instructions, and theserver.jsonregistry
description.