@touchcastllc/napster-companion-api-dev 1.0.0-alpha.68 → 1.0.0-alpha.69

package/lib/services/edge-mcp/edge-mcp-bridge.d.ts

@@ -1,33 +1,17 @@
 import type { EdgeMcpApi, FunctionCallEvent, SendCommand } from "./edge-mcp-types";
 export interface EdgeMcpBridgeOptions {
     /**
-     * The SDK's `sendCommand` method, bound to the live instance so the
-     * bridge can emit `send_message` (for state relays) and
-     * `function_call_output` (for invoke results).
+     * The SDK's `sendCommand`, bound to the live instance so the bridge can emit
+     * `send_message` (state relays) and `function_call_output` (invoke results).
      */
     sendCommand: SendCommand;
-    /**
-     * When true, the bridge logs attach status, every dispatched function
-     * call, and every state push relay to the developer console. Match the
-     * SDK's own `debug` flag.
-     *
-     * Default: `false`.
-     */
+    /** Mirror the SDK's `debug` flag. Default: `false`. */
     debug?: boolean;
-    /**
-     * How long `attach()` waits for a producer publication before giving up.
-     * The SDK is not blocked beyond this duration even when no Edge MCP
-     * exists in the page.
-     *
-     * Default: `1500` (ms).
-     */
+    /** How long `attach()` waits for an Edge MCP to publish. Default: `1500` ms. */
     attachTimeoutMs?: number;
     /**
-     * When true, Edge MCP state pushes are forwarded to the agent as
-     * `role: 'system'` messages. Set false if the consuming application
-     * wants to control state delivery itself.
-     *
-     * Default: `true`.
+     * Forward Edge MCP state pushes to the agent as `role: 'system'` messages.
+     * Set false to control state delivery yourself. Default: `true`.
      */
     relayStatePushes?: boolean;
 }
@@ -38,57 +22,35 @@ export declare class EdgeMcpBridge {
     private readonly options;
     constructor(options: EdgeMcpBridgeOptions);
     /**
-     * Discover an Edge MCP instance in the page and subscribe to state
-     * changes. Returns the discovered api ref, or `null` if no Edge MCP
-     * publishes within the timeout.
-     *
-     * Safe to await from the SDK's `init()` path. Failure is silent — the
-     * SDK continues to run exactly as it would without Edge MCP present.
+     * Discover an Edge MCP in the page and subscribe to its state changes.
+     * Returns the api ref, or `null` if none publishes within the timeout.
+     * Safe to fire from `init()` — failure is silent and non-fatal.
      */
     attach(): Promise<EdgeMcpApi | null>;
     /** True if `attach()` succeeded and the bridge has a live api ref. */
     get isAttached(): boolean;
-    /**
-     * Direct access to the attached Edge MCP api ref, for callers that need
-     * to read `listCapabilities()` themselves (for example, to build the
-     * `invokeCapability` function definition for `set_settings.functions`).
-     *
-     * Returns `null` if not attached.
-     */
+    /** The attached Edge MCP api ref, or `null` if not attached. */
     getApi(): EdgeMcpApi | null;
     /**
-     * Dispatch an incoming function call from the agent. The SDK's
-     * data-channel message handler is responsible for normalizing the
-     * upstream event shape into `FunctionCallEvent` before calling this.
-     *
-     * Only the Edge MCP wrapper function (see
-     * `INVOKE_CAPABILITY_FUNCTION_NAMES`) is handled. Anything else is silently
-     * ignored so the bridge can coexist with other tool paths (vendor-registered
-     * tools, customer's own `onFunctionCall`, etc.).
-     *
-     * Always responds via `function_call_output` — success, validation
-     * failure, and unexpected error all produce a structured result the
-     * agent can read and narrate back to the user.
+     * Dispatch a normalized agent function call. Handles it only when the name
+     * matches a capability the attached Edge MCP currently exposes. The name can
+     * arrive as the top-level `event.name` (direct call, args in
+     * `event.arguments`) or nested in a wrapper tool's `tool_name` (args under
+     * `arguments`/`args`). Anything else is ignored so the bridge coexists with
+     * other tool paths. Matched calls always reply via `function_call_output`.
      */
     dispatchFunctionCall(event: FunctionCallEvent): Promise<void>;
-    /**
-     * Tear down subscriptions and drop the Edge MCP api ref. Call from the
-     * SDK's `destroy()` path. Idempotent.
-     */
+    /** Tear down subscriptions and drop the api ref. Idempotent. */
     dispose(): void;
     /**
      * Forward an Edge MCP state push to the agent as a system message.
-     *
-     * `role: 'system'` injects context without rendering to the user.
-     * `trigger_response: false` keeps the avatar from speaking on every
-     * state change. `delay: true` waits for the agent to finish its current
-     * speech before delivering, so it doesn't interrupt mid-sentence.
+     * `trigger_response: false` keeps the avatar from speaking on every change;
+     * `delay: true` waits for it to finish its current speech first.
      */
     private relayStateChange;
     /**
-     * Emit a `function_call_output` command carrying the bridge's result for
-     * a given `call_id`. The `output` field is a JSON-encoded string per the
-     * Realtime protocol convention.
+     * Emit a `function_call_output` for a `call_id`. `output` is JSON-encoded per
+     * the Realtime protocol convention.
      */
     private sendOutput;
     private log;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@touchcastllc/napster-companion-api-dev",
-  "version": "1.0.0-alpha.68",
+  "version": "1.0.0-alpha.69",
   "keywords": [
     "napster",
     "companion-api",