@stigmer/mcp-server 3.12.8 → 3.13.0

package/domains/client.d.ts

@@ -37,7 +37,7 @@ export declare function resolveToken(extra: RequestAuth | undefined, fallback: s
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */

package/domains/client.js

@@ -37,7 +37,7 @@ export function resolveToken(extra, fallback) {
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stigmer/mcp-server",
-  "version": "3.12.8",
+  "version": "3.13.0",
   "description": "Model Context Protocol server for the Stigmer platform — exposes Stigmer agents, skills, MCP servers, and workflows as MCP tools and resources",
   "license": "Apache-2.0",
   "type": "module",
@@ -35,8 +35,8 @@
     "@connectrpc/connect": "^2.0.0",
     "@connectrpc/connect-node": "^2.1.1",
     "@modelcontextprotocol/sdk": "^1.26.0",
-    "@stigmer/protos": "3.12.8",
-    "@stigmer/sdk": "3.12.8",
+    "@stigmer/protos": "3.13.0",
+    "@stigmer/sdk": "3.13.0",
     "yaml": "^2.8.2",
     "zod": "^3.25.0"
   }

package/src/domains/client.ts

@@ -58,7 +58,7 @@ export function resolveToken(extra: RequestAuth | undefined, fallback: string):
  * caller dialing stigmer-server directly: the cloud Java server accepts only
  * `application/grpc` (it answers gRPC-web with HTTP 415 `Content-Type ... is
  * not supported`, which the tool layer would relay to the model as an opaque
- * "Content-Type error"), and the OSS Go server serves native gRPC on the same
+ * "Content-Type error"), and the OSS server serves native gRPC on the same
  * listener. This matches the runner's own backend client — the other
  * in-cluster Node caller — which likewise uses native gRPC over HTTP/2.
  */

package/src/domains/memory/memory.integration.test.ts

@@ -59,8 +59,13 @@ const openSessions = new Set<ServerHttp2Session>();
 /** The next stubbed created record; tests set this. */
 let createResponse: () => Memory;
 
-/** Requests the stub captured (object property for closure narrowing). */
-const captured: { create?: Memory } = {};
+// Requests the stub captured. An array, deliberately: resetting an optional
+// property to undefined narrows its type to `undefined` for the rest of the
+// flow (tsc does not un-narrow across the intervening callTool call), which
+// makes every later `req?.x` a property access on `never` under
+// `npm run typecheck` — the job that, unlike tsconfig.build.json, includes
+// tests. Clearing and reading an array never narrows.
+const capturedCreates: Memory[] = [];
 
 interface ToolResult {
   content: Array<{ type: string; text?: string }>;
@@ -91,7 +96,7 @@ beforeAll(async () => {
   const routes = (router: ConnectRouter) => {
     router.service(MemoryCommandController, {
       create: (req) => {
-        captured.create = req;
+        capturedCreates.push(req);
         return createResponse();
       },
     });
@@ -154,12 +159,12 @@ describe("memory roster (DD-005 D1)", () => {
 describe("argument + capture context → request mapping (DD-005 D2)", () => {
   it("maps the fact and the startup context; subject never travels", async () => {
     createResponse = () => proposedRecord("Prefers concise answers.");
-    captured.create = undefined;
+    capturedCreates.length = 0;
 
     const result = await remember({ fact: "Prefers concise answers." });
 
     expect(result.isError).toBeFalsy();
-    const req = captured.create;
+    const req = capturedCreates.at(-1);
     expect(req?.metadata?.org).toBe("acme");
     expect(req?.metadata?.name).toBe(""); // id-addressed; the server defaults the name
     expect(req?.spec?.content).toBe("Prefers concise answers.");