wasm-mcp 0.1.1 → 0.2.0

package/CHANGELOG.md

@@ -16,6 +16,25 @@ PATCH releases are noted here briefly; the pinned SHAs live in
 [`vendor/PINNED.txt`](vendor/PINNED.txt) and are reported by the
 `spec_version` tool.
 
+## 0.2.0
+
+### Added
+
+- `instruction_get` now returns per-instruction **trap conditions**: a
+  `traps` array (each `{ condition, name }`, with the spec's canonical
+  trap name) plus a `can_trap` boolean. Empty for instructions that
+  never trap (e.g. `i32.add`). Covers the finite trapping set —
+  integer `div`/`rem`, non-saturating float→int `trunc` (not
+  `trunc_sat`), memory loads/stores + bulk ops, table ops,
+  `call_indirect`, `unreachable`, and the single-condition reference
+  instructions. Derived at build time from the pinned spec; trap names
+  verified against the spec's own `test/core/*.wast` `assert_trap`
+  messages.
+- `instruction_list` gains a `can_trap` filter, and its rows now carry
+  `can_trap`.
+
+Pin unchanged.
+
 ## 0.1.0 — initial release
 
 ### Added

package/README.md

@@ -1,6 +1,6 @@
 # wasm-mcp
 
-Unofficial Model Context Protocol server for the
+Model Context Protocol server for the
 [WebAssembly core specification](https://webassembly.github.io/spec/core/).
 SHA-pinned, read-only, deterministic — safe to host as a public
 unauthenticated endpoint.
@@ -12,8 +12,9 @@ unauthenticated endpoint.
 
 - `spec_version` — the pinned upstream commit and package version.
 - `instruction_get` — opcode bytes, category, introducing version,
-  stack type signature, and validation + execution prose anchors /
-  URLs, by mnemonic (`i32.add`) or binary opcode (`0x6a`).
+  stack type signature, validation + execution prose anchors / URLs,
+  and trap conditions (`traps` + `can_trap`), by mnemonic (`i32.add`)
+  or binary opcode (`0x6a`).
 - `instruction_list` — enumerate, filterable by category (numeric,
   vector, reference, parametric, variable, table, memory, control,
   ref, i31, struct, array, extern), introducing version, or prefix.
@@ -102,11 +103,15 @@ Maintainers:
   (OIDC) — no `NPM_TOKEN`. Configure it once on npmjs.com (wasm-mcp →
   Settings → Trusted Publisher → GitHub Actions: org `xyzzylabs`, repo
   `wasm-mcp`, workflow `release.yml`).
-- **Worker deploy** needs `CLOUDFLARE_API_TOKEN` + `CLOUDFLARE_ACCOUNT_ID`.
+- **Worker deploy** needs `CLOUDFLARE_API_TOKEN` + `CLOUDFLARE_ACCOUNT_ID`,
+  stored as **environment** secrets on the `cloudflare` GitHub
+  Environment (not repo-wide) with a `main` + `v*` deployment rule —
+  see [Securing the deploy credentials](https://github.com/xyzzylabs/wasm-mcp/blob/main/docs/deployment.md#securing-the-deploy-credentials).
 - For the refresh workflow's tag push to trigger release + deploy,
-  add a `RELEASE_TOKEN` PAT (`contents: write` + `workflows`) —
+  add a `WORKFLOW_PAT` PAT (`contents: write` + `workflows`) —
   without it, refresh still re-pins and tags, but you run release /
-  deploy manually.
+  deploy manually. (Same secret name tc39-mcp uses, so one PAT — or an
+  `xyzzylabs` org secret — can serve both repos.)
 
 ## License