@ethisyscore/extension-runtime 1.117.0 → 1.118.0

package/dist/{transport-Cjpb_qPo.d.cts → transport-DDPhdaXn.d.cts}

@@ -151,6 +151,26 @@ type McpHttpRequest = {
     uri: string;
     capabilityToken: string;
     signal?: AbortSignal;
+} | {
+    /**
+     * Invoke a canonical OPERATION by module address, letting the host resolve which
+     * application answers it from the operator's provider selection.
+     *
+     * A surface cannot reach another extension's tool: the router refuses a surface
+     * capability token for cross-extension tools (EXT_MCP_008). Naming the operation instead
+     * makes the operator's selection the thing that decides, and `fallbackToolName` is what
+     * answers while nobody has chosen - so a converted call site is a no-op until someone does.
+     *
+     * Implementations POST to `mcp/modules/{moduleKey}/operations/{operationKey}/invoke` with
+     * `{ argumentsJson, fallbackToolName }`, which answers the same shape the tool route does.
+     */
+    kind: "invokeOperation";
+    moduleKey: string;
+    operationKey: string;
+    fallbackToolName: string;
+    args: unknown;
+    capabilityToken: string;
+    signal?: AbortSignal;
 } | McpUploadRequest;
 /**
  * Host-side document-upload request (a `kind` of {@link McpHttpRequest}).
@@ -486,6 +506,14 @@ declare class WorkerRemoteDomTransport {
      * surface with no response AND no further chance of being told to remount).
      */
     private reportVersionSkew;
+    /**
+     * The module-address twin of {@link handleInvokeTool}. Identical in every respect a reader
+     * should care about - same token mint, same disposed-before-token short circuit, same
+     * token-never-crosses-the-port rule - and deliberately NOT folded into one method with a
+     * branch: the two differ only in the request kind they build, and a shared method would put
+     * that branch inside the one place where getting the token handling wrong is unrecoverable.
+     */
+    private handleInvokeOperation;
     private handleInvokeTool;
     private handleGetResource;
     private handleUploadDocument;

package/dist/{transport-B9mwIXYs.d.ts → transport-pNTjXJ3R.d.ts}

@@ -151,6 +151,26 @@ type McpHttpRequest = {
     uri: string;
     capabilityToken: string;
     signal?: AbortSignal;
+} | {
+    /**
+     * Invoke a canonical OPERATION by module address, letting the host resolve which
+     * application answers it from the operator's provider selection.
+     *
+     * A surface cannot reach another extension's tool: the router refuses a surface
+     * capability token for cross-extension tools (EXT_MCP_008). Naming the operation instead
+     * makes the operator's selection the thing that decides, and `fallbackToolName` is what
+     * answers while nobody has chosen - so a converted call site is a no-op until someone does.
+     *
+     * Implementations POST to `mcp/modules/{moduleKey}/operations/{operationKey}/invoke` with
+     * `{ argumentsJson, fallbackToolName }`, which answers the same shape the tool route does.
+     */
+    kind: "invokeOperation";
+    moduleKey: string;
+    operationKey: string;
+    fallbackToolName: string;
+    args: unknown;
+    capabilityToken: string;
+    signal?: AbortSignal;
 } | McpUploadRequest;
 /**
  * Host-side document-upload request (a `kind` of {@link McpHttpRequest}).
@@ -486,6 +506,14 @@ declare class WorkerRemoteDomTransport {
      * surface with no response AND no further chance of being told to remount).
      */
     private reportVersionSkew;
+    /**
+     * The module-address twin of {@link handleInvokeTool}. Identical in every respect a reader
+     * should care about - same token mint, same disposed-before-token short circuit, same
+     * token-never-crosses-the-port rule - and deliberately NOT folded into one method with a
+     * branch: the two differ only in the request kind they build, and a shared method would put
+     * that branch inside the one place where getting the token handling wrong is unrecoverable.
+     */
+    private handleInvokeOperation;
     private handleInvokeTool;
     private handleGetResource;
     private handleUploadDocument;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ethisyscore/extension-runtime",
-  "version": "1.117.0",
+  "version": "1.118.0",
   "description": "Host + plugin runtime for EthisysCore Contract A (host-rendered) and Contract B (worker remote-runtime) extensions.",
   "type": "module",
   "main": "./dist/index.cjs",