@emseepea/testing 0.11.1 → 0.11.3

package/README.md

@@ -88,8 +88,27 @@ try {
 }
 ```
 
+`running.close()` is idempotent. It closes every client created by
+`running.connect()`, then closes the server or child process. You do not need to
+call `client.close()` separately.
+
+In Vitest, register cleanup with `onTestFinished`:
+
+```js
+import { startEmseepea } from "@emseepea/testing";
+import { it, onTestFinished } from "vitest";
+
+it("serves the expected tools", async () => {
+  const running = await startEmseepea(await createApp());
+  onTestFinished(() => running.close());
+
+  const client = await running.connect();
+  // assertions
+});
+```
+
 Passing a test context with an `after` hook, as in the first example, registers
-that same idempotent `close()` operation automatically.
+the same `close()` operation automatically.
 
 Set `protocolVersion` on `startEmseepea` or `startMcpServer` to test one of the
 server's documented protocol revisions. Omitting it keeps the `2026-07-28`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@emseepea/testing",
-  "version": "0.11.1",
+  "version": "0.11.3",
   "description": "MCP integration and semantic testing helpers",
   "license": "MIT",
   "repository": {
@@ -41,7 +41,7 @@
     "test:built": "node --test test/*.test.mjs"
   },
   "dependencies": {
-    "@emseepea/server": "0.11.1",
+    "@emseepea/server": "0.12.0",
     "@modelcontextprotocol/client": "2.0.0"
   },
   "engines": {