@yaklabs-ai/plugin-protocol 0.54.2 → 0.55.0

package/README.md

@@ -11,7 +11,7 @@ flow.
 ```json
 {
   "dependencies": {
-    "@bonsai/plugin-protocol": "npm:@yaklabs-ai/plugin-protocol@^0.54.2"
+    "@bonsai/plugin-protocol": "npm:@yaklabs-ai/plugin-protocol@^0.55.0"
   }
 }
 ```

package/THIRD-PARTY-INVENTORY.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "package": "@yaklabs-ai/plugin-protocol",
-  "version": "0.54.2",
+  "version": "0.55.0",
   "target": "npm",
   "firstPartyLicense": "MIT",
   "bundled": [

package/dist/index.d.ts

@@ -4921,8 +4921,11 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * optional `attachments`: each file's name, media type, size and the address its bytes are read
  * from, never the bytes. Gmail lists a mail's attachments there, so Flows can file them. Additive:
  * a plugin that publishes attachments declares ^0.54.2.
+ *
+ * 0.55.0 carries managed MCP calls over resource writes in both daemon and plugin-host code.
+ * Existing agent and background MCP call shapes remain supported.
  */
-export declare const KAY_PLUGIN_SDK_VERSION: "0.54.2";
+export declare const KAY_PLUGIN_SDK_VERSION: "0.55.0";
 
 export declare const KAY_PLUGIN_TARGET_NAMES: readonly ["kay.agent", "kay.app", "kay.ui"];
 

package/dist/index.js

@@ -260,8 +260,9 @@ var JsonSchema = z4.record(z4.string(), JsonValue);
 var KAY_PLUGIN_MANIFEST_SIZE_CAP_BYTES = 1024 * 1024;
 var KAY_PLUGIN_PROTOCOL_VERSION = "kay.plugin.v1";
 var KAY_PLUGIN_PROTOCOL_PACKAGE_NAME = "@bonsai/plugin-protocol";
-var KAY_PLUGIN_SDK_VERSION = "0.54.2";
+var KAY_PLUGIN_SDK_VERSION = "0.55.0";
 var KAY_PLUGIN_COMPATIBLE_SDK_VERSIONS = [
+  "0.54.2",
   "0.54.1",
   "0.54.0",
   "0.53.0",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yaklabs-ai/plugin-protocol",
-  "version": "0.54.2",
+  "version": "0.55.0",
   "description": "The Kay plugin manifest schema (`kay.plugin.v1`) — parse and validate a kay-plugin.json.",
   "author": "YakLabs",
   "type": "module",