@remcp/runtime 0.2.61 → 0.2.63

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+## 0.2.63 — 2026-09-20
+
+- Lockstep MCP Apps production-surface release with the ReMCP client/server at `0.2.63`; device runtime tool behavior is unchanged from `0.2.62`.
+
+## 0.2.62 — 2026-09-20
+
+- Lockstep skill-routing metadata release with the ReMCP client at `0.2.62`; runtime tool behavior is unchanged from `0.2.61`.
+
 ## 0.2.61 — 2026-09-20
 
 - Lockstep plugin/web branding release with the ReMCP client at `0.2.61`; runtime tool behavior is unchanged from `0.2.60`.

package/README.md

@@ -67,7 +67,14 @@ system tools such as qpdf/poppler when present. PDF text reading uses the built-
 `sharp`, or `exceljs`.
 
 `--print-tools` prints the exact JSON contract (schemas and annotations) the runtime advertises, and
-`src/catalog.mjs` is the single source of truth for it.
+`src/catalog.mjs` plus `src/extended/catalog.mjs` are the source of truth for the 83-tool release surface.
+A running device can advertise a smaller capability-aware subset; the runtime declares
+`tools.listChanged`, emits `notifications/tools/list_changed` when dynamic capabilities change, and the
+agent forwards the refreshed tool names to the hosted relay. Browser/CDP tools are the primary dynamic
+example: they are enabled only while the runtime can use a supported loopback browser endpoint.
+
+The complete hosted 91-tool reference (83 device + 8 account/fleet) is generated from the production
+catalog at https://remcp.site/docs#tools and in the public repository as `docs/TOOLS.md`.
 
 ## No approval staircase
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@remcp/runtime",
-  "version": "0.2.61",
+  "version": "0.2.63",
   "description": "First-party ReMCP local device runtime: filesystem, terminal, computer-use, browser, diagnostics and document tools over MCP.",
   "type": "module",
   "license": "MIT",