@yaklabs-ai/plugin-protocol 0.13.1 → 0.13.3

package/README.md

@@ -11,7 +11,7 @@ flow.
 ```json
 {
   "dependencies": {
-    "@kay/plugin-protocol": "npm:@yaklabs-ai/plugin-protocol@^0.13.1"
+    "@bonsai/plugin-protocol": "npm:@yaklabs-ai/plugin-protocol@^0.13.3"
   }
 }
 ```
@@ -22,7 +22,7 @@ Validate your manifest in your own CI, against the real schema, instead of a
 hand-written approximation:
 
 ```js
-import { KayPluginManifestV1 } from "@kay/plugin-protocol";
+import { KayPluginManifestV1 } from "@bonsai/plugin-protocol";
 
 const parsed = KayPluginManifestV1.safeParse(
   JSON.parse(await readFile("kay-plugin.json", "utf8")),

package/THIRD-PARTY-INVENTORY.json

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

package/dist/index.d.ts

@@ -1413,7 +1413,7 @@ export declare type CliBinaryName = z.infer<typeof CliBinaryName>;
  *
  * `provider` (decision 007) selects where the binary comes from:
  *
- * - `"vendored"` (the default when omitted) — a binary from `@kay/vendored-cli`'s
+ * - `"vendored"` (the default when omitted) — a binary from `@bonsai/vendored-cli`'s
  *   catalog, pinned and checksum-verified. Credential injection is available, and
  *   gated on the binary actually being materialized in `vendoredToolsDir`
  *   (constraint 12, vendored-or-nothing).
@@ -1510,7 +1510,7 @@ export declare type CommandContribution = z.infer<typeof CommandContribution>;
  * no real tool accepts its wire shape.
  *
  * NO `promptTemplate` variant, deliberately (tracked as #1420): the wire type this composes into
- * (`@kay/agent-runtime-protocol`'s `AgentRuntimeCommandHandler`) still carries a `promptTemplate`
+ * (`@bonsai/agent-runtime-protocol`'s `AgentRuntimeCommandHandler`) still carries a `promptTemplate`
  * kind, but only the daemon's own
  * per-session discovery (a user-authored `commands/*.md` file, `AgentRuntimeCommandProvenance`
  * `"discovered"`) ever produces one — a plugin's compiled-in/directory `.md` has no equivalent
@@ -1973,9 +1973,9 @@ export declare const KAY_APP_DATA_SNAPSHOT_MAX_BYTES: number;
 export declare const KAY_EVENT_PUBLISHER_ID: "kay";
 
 /** Released SDK contracts still implemented by the host, alongside its current SDK. */
-export declare const KAY_PLUGIN_COMPATIBLE_SDK_VERSIONS: readonly ["0.8.0", "0.8.1", "0.8.2", "0.8.3", "0.8.4", "0.8.5", "0.9.0", "0.9.1", "0.10.0", "0.11.0", "0.11.1", "0.12.0", "0.12.1", "0.12.2", "0.12.3", "0.12.4", "0.12.5", "0.13.0"];
+export declare const KAY_PLUGIN_COMPATIBLE_SDK_VERSIONS: readonly ["0.8.0", "0.8.1", "0.8.2", "0.8.3", "0.8.4", "0.8.5", "0.9.0", "0.9.1", "0.10.0", "0.11.0", "0.11.1", "0.12.0", "0.12.1", "0.12.2", "0.12.3", "0.12.4", "0.12.5", "0.13.0", "0.13.1", "0.13.2"];
 
-export declare const KAY_PLUGIN_PROTOCOL_PACKAGE_NAME: "@kay/plugin-protocol";
+export declare const KAY_PLUGIN_PROTOCOL_PACKAGE_NAME: "@bonsai/plugin-protocol";
 
 export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
 
@@ -1984,14 +1984,14 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * `compatibility.sdk` range is matched against.
  *
  * ── Why this is the compatibility axis, and the app version is not ──────────
- * A plugin never bundles the SDK: the host injects its own `@kay/plugin-sdk`
+ * A plugin never bundles the SDK: the host injects its own `@bonsai/plugin-sdk`
  * dist at import time. So the SDK surface a plugin was written against is the
  * thing that can break under it, and the Bonsai app version is only correlated
  * with that — it moves for reasons a plugin cannot observe.
  *
  * ── Two lines, deliberately, not one ────────────────────────────────────────
  * This continues the published `@yaklabs-ai/plugin-sdk` line, currently in 0.x.
- * `KAY_UI_SDK_VERSION` in `@kay/protocol` is a SEPARATE line at its own number,
+ * `KAY_UI_SDK_VERSION` in `@bonsai/protocol` is a SEPARATE line at its own number,
  * and the two are never compared: a `kay.ui` app package declares against the
  * UI SDK, a plugin manifest declares `compatibility.sdk` against this one, and
  * no manifest field takes both. Unifying them would have to publish the plugin
@@ -2008,7 +2008,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * the minor the breaking slot, so a minor bump refuses
  * (`sdk-range-unsatisfied`) every plugin still declaring the previous one — a
  * fleet-wide break, never the price of one new entrypoint. 0.7.1 carried the
- * additive `@kay/plugin-sdk/phase-shift` surface that way, while `^0.7.0`
+ * additive `@bonsai/plugin-sdk/phase-shift` surface that way, while `^0.7.0`
  * plugins kept loading.
  *
  * 0.8.0 IS that fleet-wide break, deliberately, and it spends the one break on
@@ -2039,7 +2039,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * was not written to.
  *
  * 0.8.1 takes the PATCH slot under the addition rule above: `api.withJev`
- * (`@kay/plugin-sdk/jev`) — Jev typed-decision inference with a required
+ * (`@bonsai/plugin-sdk/jev`) — Jev typed-decision inference with a required
  * fallback — is one new member on an api a plugin RECEIVES. A `^0.8.0` plugin
  * keeps loading and keeps compiling; it simply never reaches for the member.
  * The member is non-optional for the same reason 0.8.0 made every brokered
@@ -2056,7 +2056,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * older host refuses it at load instead of failing at the call. 0.8.3's
  * `observe` also answers `invalid`, recording nothing, for a detector id,
  * version, question name, choice label, or source id outside the recorded-name
- * grammar (`invalidObservation` in `@kay/plugin-sdk/signals`): names a reader
+ * grammar (`invalidObservation` in `@bonsai/plugin-sdk/signals`): names a reader
  * could not later address, filter on, or copy back. A 0.8.2 host recorded such
  * names, so a plugin moving to 0.8.3 checks its names against that grammar.
  *
@@ -2115,7 +2115,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * failing.
  *
  * 0.12.0 replaces the vendor client `api.withJev` hands its callback. `use`
- * now receives Bonsai's own `JevClient` (`@kay/plugin-sdk/jev`): one method,
+ * now receives Bonsai's own `JevClient` (`@bonsai/plugin-sdk/jev`): one method,
  * `classify({state, questions})`, in Bonsai's question and answer vocabulary
  * (yes/no is `bool` answering `probability`; instructions and criteria are
  * text; the state is a JSON object), rejecting with a classified
@@ -2178,7 +2178,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * that calls it declares `^0.12.5`, so an older host refuses a directory or repository plugin at
  * load instead of the call failing.
  *
- * 0.13.0 adds `@kay/plugin-sdk/fs`, Bonsai's own `node:fs/promises`: the same functions, arguments,
+ * 0.13.0 adds `@bonsai/plugin-sdk/fs`, Bonsai's own `node:fs/promises`: the same functions, arguments,
  * return types and errors, with every call run on the host's user-files workers under a deadline
  * (`ERR_KAY_FS_DEADLINE` and siblings when the host gives up or does not try), plus
  * `writeFileAtomic` and `withTimeout`. With no host installed it is Node's own module. It adds
@@ -2186,7 +2186,7 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * session family's Whiteboard, and makes it a required member of `KayAgentPluginApi`. It removes
  * the `kay.agent` api's `filesystem` broker, the `filesystem.read` / `filesystem.write`
  * permissions it was gated by, the `{ root: "filesystem", selector }` URI backing and the URI
- * module `verbs` that went with it: plugins use `@kay/plugin-sdk/fs`, `userFiles` or
+ * module `verbs` that went with it: plugins use `@bonsai/plugin-sdk/fs`, `userFiles` or
  * `familyFolder` instead. No plugin used them. Stored grants naming the retired permissions are
  * ignored, not refused. For the api surface this is a clean break with no shim and deliberately
  * NOT a load refusal, like 0.12.0: every earlier release stays in the retention list, so a
@@ -2194,18 +2194,36 @@ export declare const KAY_PLUGIN_PROTOCOL_VERSION: "kay.plugin.v1";
  * manifest is different: a manifest that still declares URI-module `verbs` or
  * `filesystemBacking: { root: "filesystem" }` fails to parse and is refused at load (no plugin
  * declared either). A plugin that imports
- * `@kay/plugin-sdk/fs` or calls `familyFolder` declares `^0.13.0`, so an older host refuses a
+ * `@bonsai/plugin-sdk/fs` or calls `familyFolder` declares `^0.13.0`, so an older host refuses a
  * directory or repository plugin at load.
  *
- * 0.13.1 adds the signal engine to `@kay/plugin-sdk/signals`: `SignalDefinition`,
+ * 0.13.1 adds the signal engine to `@bonsai/plugin-sdk/signals`: `SignalDefinition`,
  * `createSignalEngine` and `signalAnswersPass` (a plugin declares its Jev signals as data and the
  * engine evaluates them, upstreams first, through `app.signals.observe`), plus `signalDigest`.
  * `observe` gains three optional input fields, `subject`, `after` and `reuse`, and an observation
  * and a read signal carry the stored `subject` and `upstreamId` back. Additive: a plugin compiled
  * against 0.13.0 never sends or reads them. A plugin that imports the engine declares `^0.13.1`,
  * so an older host refuses a directory or repository plugin at load.
+ *
+ * 0.13.2 adds `app.tools` (`KayAppTools`): `describe(sessionId, refs)` returns, for each tool name
+ * or address a live session can use, the text the agent sees for it, where it comes from, and
+ * whether it is one of Bonsai's own (`ownedByBonsai`). Checked per call against the new
+ * `tools.describe` claim. It also adds the manifest's top-level `ownedByBonsai` flag, honoured only
+ * for a plugin that ships with Bonsai. Additive: a plugin compiled against 0.13.1 never reads the
+ * member. A plugin that calls it declares `^0.13.2`, so an older host refuses a directory or
+ * repository plugin at load. The flag is new schema, so an older host refuses a manifest that sets
+ * it at parse, like 0.12.3's page open kind.
+ *
+ * 0.13.3 adds `app.usage` (`KayAppUsage`, `createUnavailableUsage`): `uriActivity({ prefix })`
+ * returns read and change activity for resources under one of the plugin's OWN registered URI
+ * schemes, checked per call (any other prefix answers `refused`). It also adds
+ * `KayAppAgentDefinition.maintains`, the URI schemes a registered agent definition's runs maintain;
+ * reads by such a run and its session family are not counted. Additive: a plugin compiled against
+ * 0.13.2 never reads the member or sets the field. A plugin that calls `app.usage` or declares
+ * `maintains` declares `^0.13.3`, so an older host refuses a directory or repository plugin at
+ * load; an older host's strict definition schema would refuse a definition that sets `maintains`.
  */
-export declare const KAY_PLUGIN_SDK_VERSION: "0.13.1";
+export declare const KAY_PLUGIN_SDK_VERSION: "0.13.3";
 
 export declare const KAY_PLUGIN_TARGET_NAMES: readonly ["kay.agent", "kay.app", "kay.ui"];
 
@@ -3329,6 +3347,7 @@ export declare const KayPluginManifestV1: z.ZodObject<{
         minKayVersion: z.ZodOptional<z.ZodString>;
         sdk: z.ZodOptional<z.ZodString>;
     }, z.core.$strict>>>;
+    ownedByBonsai: z.ZodOptional<z.ZodBoolean>;
     dependencies: z.ZodOptional<z.ZodObject<{
         plugins: z.ZodOptional<z.ZodArray<z.ZodString>>;
     }, z.core.$strict>>;
@@ -3731,7 +3750,7 @@ export declare function parseResolvedPluginContractV1(value: unknown): ResolvedP
 export declare function parseSemver(value: string): ParsedSemver | undefined;
 
 /** Every capability slug {@link PluginCapabilityClaimV1} can express, for exhaustive table checks. */
-export declare const PLUGIN_CAPABILITY_SLUGS: readonly ["sessions.run", "network.connect", "web-session.request", "web-session.download", "process.spawn", "corpus.read", "signals.read", "skills.read", "workspace.command", "sessions.create", "sessions.update", "models.complete", "jev.use", "automations.write", "automations.run", "workflows.define", "session-events.subscribe", "agents.run", "dynamic-context.register", "app-data.register", "account.assert", "account.update", "agents.permissions", "tool-interception.register", "interaction.surface", "config.declare-section", "auth.own-service", "auth.shared-identity", "cli.bind", "whiteboard.discover", "whiteboard.read", "whiteboard.create", "whiteboard.update", "whiteboard.remove"];
+export declare const PLUGIN_CAPABILITY_SLUGS: readonly ["sessions.run", "network.connect", "web-session.request", "web-session.download", "process.spawn", "corpus.read", "signals.read", "skills.read", "tools.describe", "workspace.command", "sessions.create", "sessions.update", "models.complete", "jev.use", "automations.write", "automations.run", "workflows.define", "session-events.subscribe", "agents.run", "dynamic-context.register", "app-data.register", "account.assert", "account.update", "agents.permissions", "tool-interception.register", "interaction.surface", "config.declare-section", "auth.own-service", "auth.shared-identity", "cli.bind", "whiteboard.discover", "whiteboard.read", "whiteboard.create", "whiteboard.update", "whiteboard.remove"];
 
 /** The root `<svg>` attribute a tile icon declares itself with. */
 export declare const PLUGIN_ICON_SHAPE_ATTRIBUTE = "data-icon-shape";
@@ -4159,6 +4178,10 @@ export declare const PluginCapabilityClaimV1: z.ZodDiscriminatedUnion<[z.ZodObje
     target: z.ZodLiteral<"kay.app">;
     slug: z.ZodLiteral<"skills.read">;
     envelope: z.ZodObject<{}, z.core.$strict>;
+}, z.core.$strict>, z.ZodObject<{
+    target: z.ZodLiteral<"kay.app">;
+    slug: z.ZodLiteral<"tools.describe">;
+    envelope: z.ZodObject<{}, z.core.$strict>;
 }, z.core.$strict>, z.ZodObject<{
     target: z.ZodLiteral<"kay.app">;
     slug: z.ZodLiteral<"workspace.command">;
@@ -4367,6 +4390,10 @@ export declare const PluginCapabilityDecisionV1: z.ZodDiscriminatedUnion<[z.ZodO
         target: z.ZodLiteral<"kay.app">;
         slug: z.ZodLiteral<"skills.read">;
         envelope: z.ZodObject<{}, z.core.$strict>;
+    }, z.core.$strict>, z.ZodObject<{
+        target: z.ZodLiteral<"kay.app">;
+        slug: z.ZodLiteral<"tools.describe">;
+        envelope: z.ZodObject<{}, z.core.$strict>;
     }, z.core.$strict>, z.ZodObject<{
         target: z.ZodLiteral<"kay.app">;
         slug: z.ZodLiteral<"workspace.command">;
@@ -4570,6 +4597,10 @@ export declare const PluginCapabilityDecisionV1: z.ZodDiscriminatedUnion<[z.ZodO
             target: z.ZodLiteral<"kay.app">;
             slug: z.ZodLiteral<"skills.read">;
             envelope: z.ZodObject<{}, z.core.$strict>;
+        }, z.core.$strict>, z.ZodObject<{
+            target: z.ZodLiteral<"kay.app">;
+            slug: z.ZodLiteral<"tools.describe">;
+            envelope: z.ZodObject<{}, z.core.$strict>;
         }, z.core.$strict>, z.ZodObject<{
             target: z.ZodLiteral<"kay.app">;
             slug: z.ZodLiteral<"workspace.command">;
@@ -4836,6 +4867,10 @@ export declare const PluginCapabilityRefusalV1: z.ZodObject<{
         target: z.ZodLiteral<"kay.app">;
         slug: z.ZodLiteral<"skills.read">;
         envelope: z.ZodObject<{}, z.core.$strict>;
+    }, z.core.$strict>, z.ZodObject<{
+        target: z.ZodLiteral<"kay.app">;
+        slug: z.ZodLiteral<"tools.describe">;
+        envelope: z.ZodObject<{}, z.core.$strict>;
     }, z.core.$strict>, z.ZodObject<{
         target: z.ZodLiteral<"kay.app">;
         slug: z.ZodLiteral<"workspace.command">;
@@ -7583,14 +7618,14 @@ export declare type ScopeRequirement = z.infer<typeof ScopeRequirement>;
  * this list. Two consequences worth knowing:
  *
  * - `sessions.create` and `sessions.run` are the two separately-granted plugin doors
- *   (`@kay/plugin-protocol`'s `permissions.ts`: `create` mints a persisted user-visible session,
+ *   (`@bonsai/plugin-protocol`'s `permissions.ts`: `create` mints a persisted user-visible session,
  *   `run` executes a hidden headless one). Each names ITSELF at the site that mints the session;
  *   neither is inferred from the surface string, which cannot tell them apart.
  * - `sessions.create` stamps a plugin creator only for a create that declares a plugin-surfaced
  *   `system` origin. The SDK `create` door passes no origin today, so its sessions read as the
  *   ordinary chats they are; the value is still the honest one for that door when it does.
  * - `agents.run` (G1, 2026-09) is the generic session-event run door
- *   (`app.agents.run(ref, input, cause, {fork?})`, `@kay/plugin-sdk`'s `kay-app/agents.ts`): a
+ *   (`app.agents.run(ref, input, cause, {fork?})`, `@bonsai/plugin-sdk`'s `kay-app/agents.ts`): a
  *   plugin's `app.sessionEvents.subscribe` handler spins up a bounded agent run in response to a
  *   published session event. `callerSessionId` carries the cause's `sourceSessionId` — the session
  *   whose event caused this run — and {@link SessionProvenanceRecord.causedByEvent} carries the
@@ -7772,7 +7807,7 @@ export declare type SessionHealthEntry = z.infer<typeof sessionHealthEntrySchema
  * treats that failure as a validate-and-drop, never a throw.
  *
  * The telemetry lane's own `runtime.usage.session_health.observed` payload
- * (`@kay/agent-runtime`, `kay/telemetry/schema.ts`) is a SEPARATE bounded
+ * (`@bonsai/agent-runtime`, `kay/telemetry/schema.ts`) is a SEPARATE bounded
  * projection of this record, not a copy: no entry ids, no timestamps, no
  * free text cross from here onto that event.
  */

package/dist/index.js

@@ -114,8 +114,8 @@ import { z as z2 } from "zod";
 // packages/plugin-protocol/dist/common.js
 import { z } from "zod";
 var KAY_PLUGIN_PROTOCOL_VERSION = "kay.plugin.v1";
-var KAY_PLUGIN_PROTOCOL_PACKAGE_NAME = "@kay/plugin-protocol";
-var KAY_PLUGIN_SDK_VERSION = "0.13.1";
+var KAY_PLUGIN_PROTOCOL_PACKAGE_NAME = "@bonsai/plugin-protocol";
+var KAY_PLUGIN_SDK_VERSION = "0.13.3";
 var KAY_PLUGIN_COMPATIBLE_SDK_VERSIONS = [
   "0.8.0",
   "0.8.1",
@@ -134,7 +134,9 @@ var KAY_PLUGIN_COMPATIBLE_SDK_VERSIONS = [
   "0.12.3",
   "0.12.4",
   "0.12.5",
-  "0.13.0"
+  "0.13.0",
+  "0.13.1",
+  "0.13.2"
 ];
 var KAY_PLUGIN_TARGET_NAMES = [
   "kay.agent",
@@ -306,7 +308,7 @@ var SessionCreator = z3.discriminatedUnion("kind", [
    * An automation binding that fired.
    *
    * `triggerKind` names what the binding matched on, and `uri-change` is in the list because a
-   * durable watcher is a real condition kind (`@kay/automations`'s `AutomationMatch`) with no
+   * durable watcher is a real condition kind (`@bonsai/automations`'s `AutomationMatch`) with no
    * spelling among the other four: it watches the world OUTSIDE the session, so it is neither a
    * schedule nor a session-fact occurrence. Added 2026-08-19, when the automation producers
    * landed and a watcher's report session had nothing honest to stamp.
@@ -352,7 +354,7 @@ var SessionCausedByEventShape = z3.strictObject({
   kind: z3.enum(["session-event", "backfill"]).optional(),
   /** Required when `kind` is `"session-event"` or absent; must be omitted when `kind` is `"backfill"`. */
   event: z3.strictObject({
-    /** {@link KayAppSessionEventType} in `@kay/plugin-sdk`, mirrored: a closed, extensible union. */
+    /** {@link KayAppSessionEventType} in `@bonsai/plugin-sdk`, mirrored: a closed, extensible union. */
     type: z3.enum([
       "turn-settled",
       "phase-shift",
@@ -1528,6 +1530,14 @@ var PluginCapabilityClaimV1 = z6.discriminatedUnion("slug", [
     slug: z6.literal("skills.read"),
     envelope: z6.strictObject({})
   }),
+  z6.strictObject({
+    // The text an agent sees for a tool or an address in a live session, where each comes from,
+    // and whether it is one of Bonsai's own. Read-only and never a call. An empty envelope because
+    // the grant itself is the visibility decision, as with `skills.read`.
+    target: z6.literal("kay.app"),
+    slug: z6.literal("tools.describe"),
+    envelope: z6.strictObject({})
+  }),
   z6.strictObject({
     target: z6.literal("kay.app"),
     slug: z6.literal("workspace.command"),
@@ -1671,6 +1681,7 @@ var PLUGIN_CAPABILITY_SLUGS = [
   "corpus.read",
   "signals.read",
   "skills.read",
+  "tools.describe",
   "workspace.command",
   "sessions.create",
   "sessions.update",
@@ -1777,6 +1788,7 @@ function sameClaim(a, b) {
     case "corpus.read":
     case "signals.read":
     case "skills.read":
+    case "tools.describe":
     case "workspace.command":
     case "models.complete":
     case "jev.use":
@@ -1841,6 +1853,7 @@ function envelopePairs(a, b) {
     case "corpus.read":
     case "signals.read":
     case "skills.read":
+    case "tools.describe":
     case "workspace.command":
     case "models.complete":
     case "jev.use":
@@ -2578,7 +2591,7 @@ var KayUiAppHostCapability = z7.enum([
   "automations.read",
   "automations.run",
   // Grants exactly `panes.place` (see `WORKSPACE_VERB_TIERS`/`KayWorkspaceCommand` in
-  // `@kay/agent-runtime-protocol`) through the `kay.ui` capability broker's `workspace.place`.
+  // `@bonsai/agent-runtime-protocol`) through the `kay.ui` capability broker's `workspace.place`.
   "workspace.place-pane",
   // Grants presentation into the native header of the pane hosting this app instance.
   "workspace.pane-header",
@@ -3096,6 +3109,13 @@ var KayPluginManifestV1 = z8.strictObject({
   auth: PluginAuthManifest.optional(),
   permissions: PluginPermissionManifest.optional(),
   compatibility: PluginCompatibilityManifest.optional(),
+  /**
+   * Whether this plugin is part of Bonsai's own workbench (memory, sessions, the workspace) rather
+   * than a connection to the user's outside world or a general-purpose tool. Its tools and URI
+   * schemes then report `ownedByBonsai`. Honoured only for a plugin that ships with Bonsai: the
+   * host reads any other plugin's flag as false. Absent ⇒ false.
+   */
+  ownedByBonsai: z8.boolean().optional(),
   /**
    * Explicit plugin-level dependencies — other plugins this plugin requires to be present in the
    * composed roster. At composition time the runtime checks each id against the accepted

package/package.json

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