@ethisyscore/extension-runtime 1.122.0 → 1.124.0

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

@@ -1,4 +1,4 @@
-import { U as UploadDocumentMeta, d as BridgePushThemeEnvelope, c as BridgePushLocaleEnvelope, b as BridgePushDensityEnvelope, a as BridgePushA11yEnvelope, B as BridgeNavPushEnvelope } from './bridge-envelopes-DAuew-fU.cjs';
+import { U as UploadDocumentMeta, d as BridgePushThemeEnvelope, c as BridgePushLocaleEnvelope, b as BridgePushDensityEnvelope, a as BridgePushA11yEnvelope, B as BridgeNavPushEnvelope } from './bridge-envelopes-M5a42rAy.js';
 
 /**
  * Version-skew detection for host-side MCP calls.
@@ -163,12 +163,27 @@ type McpHttpRequest = {
      *
      * Implementations POST to `mcp/modules/{moduleKey}/operations/{operationKey}/invoke` with
      * `{ argumentsJson, fallbackToolName }`, which answers the same shape the tool route does.
+     * When `fallbackArgs` is present they add `fallbackArgumentsJson` alongside; a host that
+     * omits it leaves the fallback rung with the canonical arguments, which is what every
+     * call did before the field existed.
      */
     kind: "invokeOperation";
     moduleKey: string;
     operationKey: string;
     fallbackToolName: string;
     args: unknown;
+    /**
+     * Arguments used ONLY if `fallbackToolName` answers, because an in-house fallback tool
+     * need not declare the canonical field names - `hr:get-employee-absences` wants
+     * `employeeIds` where the canonical operation says `personIds`. The browser twin of
+     * `ModuleFallback`'s second argument on the backend.
+     *
+     * Additive and optional: `undefined` means "send the canonical arguments to the fallback
+     * too". It carries no authority and cannot change which tool runs - the tool NAME is
+     * still `fallbackToolName`, which the host checks against the calling extension's
+     * installed manifest before the fallback rung runs.
+     */
+    fallbackArgs?: unknown;
     capabilityToken: string;
     signal?: AbortSignal;
 } | McpUploadRequest;

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

@@ -1,4 +1,4 @@
-import { U as UploadDocumentMeta, d as BridgePushThemeEnvelope, c as BridgePushLocaleEnvelope, b as BridgePushDensityEnvelope, a as BridgePushA11yEnvelope, B as BridgeNavPushEnvelope } from './bridge-envelopes-DAuew-fU.js';
+import { U as UploadDocumentMeta, d as BridgePushThemeEnvelope, c as BridgePushLocaleEnvelope, b as BridgePushDensityEnvelope, a as BridgePushA11yEnvelope, B as BridgeNavPushEnvelope } from './bridge-envelopes-M5a42rAy.cjs';
 
 /**
  * Version-skew detection for host-side MCP calls.
@@ -163,12 +163,27 @@ type McpHttpRequest = {
      *
      * Implementations POST to `mcp/modules/{moduleKey}/operations/{operationKey}/invoke` with
      * `{ argumentsJson, fallbackToolName }`, which answers the same shape the tool route does.
+     * When `fallbackArgs` is present they add `fallbackArgumentsJson` alongside; a host that
+     * omits it leaves the fallback rung with the canonical arguments, which is what every
+     * call did before the field existed.
      */
     kind: "invokeOperation";
     moduleKey: string;
     operationKey: string;
     fallbackToolName: string;
     args: unknown;
+    /**
+     * Arguments used ONLY if `fallbackToolName` answers, because an in-house fallback tool
+     * need not declare the canonical field names - `hr:get-employee-absences` wants
+     * `employeeIds` where the canonical operation says `personIds`. The browser twin of
+     * `ModuleFallback`'s second argument on the backend.
+     *
+     * Additive and optional: `undefined` means "send the canonical arguments to the fallback
+     * too". It carries no authority and cannot change which tool runs - the tool NAME is
+     * still `fallbackToolName`, which the host checks against the calling extension's
+     * installed manifest before the fallback rung runs.
+     */
+    fallbackArgs?: unknown;
     capabilityToken: string;
     signal?: AbortSignal;
 } | McpUploadRequest;

package/package.json

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