@procedures/client 0.37.0 → 0.39.0

package/CHANGELOG.md

@@ -1,5 +1,48 @@
 # @procedures/client
 
+## 0.39.0
+
+### Minor Changes
+
+- 55d1e4d: Each face refuses a request above its size limit with the code `PAYLOAD_TOO_LARGE` (roadmap CLI-85). The transport contract suite found the faces that did not.
+  
+  - `@procedures/client`: the HTTP handler answers a body above `bodyLimit` with the code `PAYLOAD_TOO_LARGE` and the status 413. Before, the code was `INVALID_REQUEST`. A caller that compares the code of a 413 with `INVALID_REQUEST` must compare it with `PAYLOAD_TOO_LARGE`. This change of behavior is a minor change.
+  - `@procedures/client`: when a server closes a WebSocket with the close code 1009 (a message above its limit), each pending call of `WebSocketTransport` fails with the code `PAYLOAD_TOO_LARGE` and `retryable: false`. Before, the error had no code.
+  - `@procedures/client`: the new entry point `@procedures/client/testing` has the transport contract suite: `describeTransportContract(face, runner)`, `clientCaller()`, `mcpCaller()` and the collection storage `LogStorage`. A face of the procedures server in another package or in an app runs the same cases as the faces of the client. The suite imports no test runner: give it `{ describe, it, afterEach, expect }` of Vitest. This new entry point is a minor change.
+  - `@procedures/mcp-server`: the Streamable HTTP endpoint reads the body of a request in a session with `maxBodyBytes`. A body above the limit gets the status 413 with the code `PAYLOAD_TOO_LARGE`. Before, the SDK refused it without a code.
+  
+  Migration:
+  
+  - A caller that reads the code of a 413 from the HTTP handler compares it with `PAYLOAD_TOO_LARGE`, not `INVALID_REQUEST`.
+  - A caller of `WebSocketTransport` that retries each failed call stops at `retryable: false`. A call above the limit of the server fails the same way each time.
+  - The site, MiniMongo, Graph and jarvis: no step, unless one of them compares the code of a refused large request with `INVALID_REQUEST`.
+
+## 0.38.0
+
+### Patch Changes
+
+- c6fba49: The keys of procedure paths go through the codec of `@procedures/client` (roadmap CLI-84, decision D36). A path without `.` and `%` in a segment keeps the same key, so only such segments see a change.
+  
+  MINOR (breaking, pre-1.0): for a segment with `.` or `%`, two keys that callers can see change. If it is not clear whether a change is breaking, the release treats it as breaking.
+  
+  - `@procedures/cli-kit`: the key of a `format` hook is `pathToKey(path)`. A caller sets this key. For the path `["a", "b.c"]`, the key was `a.b.c`, and it is now `a.b%2Ec`.
+  - `@procedures/lib`: the `key` of each procedure of the ecosystem scan is `pathToKey(path)`. The scan gives this key over the wire. For the path `["a", "b.c"]`, the key was `a.b.c`, and it is now `a.b%2Ec`.
+  
+  The other changes are fixes:
+  
+  - `pathToKey()` accepts a `readonly string[]`.
+  - `@procedures/llm`: a procedure tool reads its key with `keyToPath()`, so `a%2Eb.c` names the path `["a.b", "c"]`.
+  - `@procedures/mcp`: the cache key of a tool is `pathToKey(path)`. Before, `["a.b", "c"]` and `["a", "b", "c"]` had the same cache key. The cache is in the process, so no stored data changes.
+  - `@procedures/mcp-server`: the message about two procedures with one tool name gives the keys of the paths.
+  
+  No stored key and no topic changes. The storage keys and the topics already used the codec (roadmap CLI-75).
+  
+  Migration:
+  
+  - A caller of `cli-kit` with a `format` hook for a path with a dotted segment writes the key in the encoded form, for example `a.b%2Ec`.
+  - A reader of the ecosystem scan that splits a `key` on `.` uses `keyToPath(key)`.
+  - The site, MiniMongo, Graph and jarvis: no step, if their procedure paths have no segment with `.` or `%`.
+
 ## 0.37.0
 
 No changes in this release.