@yaklabs-ai/plugin-sdk 0.45.0 → 0.47.0

package/dist/vendored-mcp.js

@@ -76,12 +76,15 @@ var REST_CAPTURE_RE = /^:([A-Za-z_][A-Za-z0-9_]*)\*$/;
 var CONSTRAINED_CAPTURE_RE = /^([A-Za-z_][A-Za-z0-9_]*)(?:\((.*)\))?(\.[A-Za-z0-9]+)?$/;
 var MAX_CAPTURE_CONSTRAINT_LENGTH = 64;
 function compileUriClaim(claim) {
+  return compileClaim(claim);
+}
+function compileClaim(claim) {
   if (claim.kind === "scheme") {
     const scheme = normalizeProtocol(claim.scheme);
     return {
       claim,
       match(input) {
-        const actual = SCHEME_RE.exec(input.trim())?.[1]?.toLowerCase();
+        const actual = typeof input === "string" ? SCHEME_RE.exec(input.trim())?.[1]?.toLowerCase() : input.scheme;
         if (actual !== scheme)
           return void 0;
         return { claimKind: claim.kind };
@@ -91,8 +94,7 @@ function compileUriClaim(claim) {
   const pattern = compileRoutePattern(claim.pattern);
   const normalizeTo = claim.normalizeTo === void 0 ? void 0 : compileTemplate(claim.normalizeTo);
   const sourceUrl = claim.kind === "uriPattern" && claim.sourceUrl !== void 0 ? compileTemplate(claim.sourceUrl) : void 0;
-  const matchAt = (target, selector) => {
-    const parsed = parsePatternInput(target);
+  const matchAt = (parsed, selector) => {
     if (parsed === void 0)
       return void 0;
     const captures = matchRoute(pattern, parsed);
@@ -118,14 +120,14 @@ function compileUriClaim(claim) {
     claim,
     match(input) {
       if (claim.kind === "uriPattern") {
-        const { selector, rest } = parseUriConnectionSelector(input);
+        const { selector, rest } = typeof input === "string" ? parseUriConnectionSelector(input) : input.connection;
         if (selector !== void 0) {
-          const match = matchAt(rest, selector);
+          const match = matchAt(typeof input === "string" ? parsePatternInput(rest) : input.selected, selector);
           if (match !== void 0)
             return match;
         }
       }
-      return matchAt(input, void 0);
+      return matchAt(typeof input === "string" ? parsePatternInput(input) : input.raw, void 0);
     }
   };
 }
@@ -323,7 +325,16 @@ var TRANSFORMS = {
   slackTimestamp: (value) => {
     const match = /^p(\d+)(\d{6})$/.exec(value);
     return match === null ? void 0 : `${match[1]}.${match[2]}`;
-  }
+  },
+  beforeColon: (value) => {
+    const end = value.indexOf(":");
+    return end > 0 ? value.slice(0, end) : void 0;
+  },
+  beforeTilde: (value) => {
+    const end = value.lastIndexOf("~");
+    return end > 0 ? value.slice(0, end) : void 0;
+  },
+  encoded: encodeURIComponent
 };
 function isTransform(name) {
   return Object.prototype.hasOwnProperty.call(TRANSFORMS, name);
@@ -394,7 +405,7 @@ function fillTemplate(parts, captures, restCaptures) {
     const transformed = TRANSFORMS[part.transform](raw);
     if (transformed === void 0)
       return void 0;
-    out += escapeForPosition(transformed, part.position);
+    out += part.transform === "encoded" ? transformed : escapeForPosition(transformed, part.position);
   }
   return out;
 }

package/dist/whiteboard.d.ts

@@ -72,9 +72,6 @@ export declare const WhiteboardTypeInfo: z.ZodObject<{
     displayName: z.ZodString;
     schemaVersion: z.ZodNumber;
     available: z.ZodBoolean;
-    presentation: z.ZodOptional<z.ZodObject<{
-        app: z.ZodString;
-    }, z.core.$strict>>;
 }, z.core.$strict>;
 
 export declare type WhiteboardTypeInfo = Readonly<z.infer<typeof WhiteboardTypeInfo>>;

package/dist/whiteboard.js

@@ -160,11 +160,7 @@ var WhiteboardTypeInfo = z4.strictObject({
   typeId: GlobalContributionId,
   displayName: NonEmptyString,
   schemaVersion: z4.number().int().positive(),
-  available: z4.boolean(),
-  /** A plugin-owned readonly presentation; absent types use the host fallback. */
-  presentation: z4.strictObject({
-    app: GlobalContributionId
-  }).optional()
+  available: z4.boolean()
 });
 export {
   JsonValue,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@yaklabs-ai/plugin-sdk",
-  "version": "0.45.0",
+  "version": "0.47.0",
   "description": "The Kay plugin SDK — types and helpers for authoring a Kay directory plugin.",
   "author": "YakLabs",
   "type": "module",
@@ -33,6 +33,10 @@
       "types": "./dist/disclosure.d.ts",
       "default": "./dist/disclosure.js"
     },
+    "./artifact-provenance": {
+      "types": "./dist/artifact-provenance.d.ts",
+      "default": "./dist/artifact-provenance.js"
+    },
     "./signals": {
       "types": "./dist/signals.d.ts",
       "default": "./dist/signals.js"

package/skills/directory-plugin-authoring/SKILL.md

@@ -43,8 +43,8 @@ pnpm create-plugin --id com.example.widgets
 Run from the root of a Bonsai checkout. It writes a working plugin (manifest, entrypoint, tsconfig,
 README) that already typechecks and loads; `--tier starter` adds a URI module, a bundled skill,
 and a standalone `node --test` test to copy from. Add `--ui` (either tier) when the plugin needs a
-page: it writes `ui.tsx`, declares the `kay.ui` entrypoint, and generates the UI typecheck config
-described below. `--ui` also needs `pnpm --filter @bonsai/ui build` once per checkout; the scaffold
+page: it writes `ui.tsx`, declares it under the manifest's `apps`, and generates the UI typecheck
+config described below. `--ui` also needs `pnpm --filter @bonsai/ui build` once per checkout; the scaffold
 stops and says so when that build is missing.
 
 Never hand-build a plugin as a tsc-compiled package and copy the output into `~/.kay/plugins/`.
@@ -122,14 +122,15 @@ a plugin you install yourself.
 
 A plugin with a UI has three targets. Each declared daemon target is a bundle root, so its
 entrypoint may import other files in the plugin; `kay.agent` runs in the daemon per session and
-`kay.app` runs in the daemon once. `kay.ui` runs in the renderer through its own UI bundle, which is a single
-self-contained module: unlike the daemon targets, `ui.tsx` cannot import sibling files. A
-plugin UI contributes through `api.slots` (`registerPage`, `registerSidebarItem`,
-`registerPaneAction`, and the rest of `buildSlots` in
-`packages/kay-renderer/src/renderer/src/extension-loader/build-extension-api.ts`). A page gets its own
+`kay.app` runs in the daemon once. A page runs in the renderer: declare it under `apps` in
+`targets.kay.ui.contributes`, with `entrypoint.module` naming your source and `entrypoint.export`
+the component. Bonsai compiles it when it loads the plugin, so there is no build step: relative
+imports work within the plugin's folder, and Tailwind classes work with no setup against Bonsai's
+theme. A page imports only `react` and `@bonsai/plugin-ui-sdk`; a `kay.ui` `entrypoint` with an
+`activate` function is for what a declaration cannot do yet, not for pages. A page gets its own
 activity-rail button when the manifest declares it: `railEntries` under `targets.kay.ui.contributes`,
-with `id`, `title` and `page`, and optionally `icon`, `shortcut`, `order` and `section`. That
-declaration works with no `ui.tsx` at all. To give the entry a sidebar, add `panel: { body }` naming
+with `id`, `title` and `page` (`<namespace>.<app localId>`), and optionally `icon`, `shortcut`,
+`order` and `section`. To give the entry a sidebar, add `panel: { body }` naming
 an app in the same manifest with `contextOnly: true`. The sidebar is always there once declared, so
 the app shows its own empty state. To give a notification rule's toast a "Show changes" preview, add
 a `toastPreviews` entry under `targets.kay.ui.contributes` with `rule` (the rule's `localId`), `body`
@@ -143,11 +144,11 @@ on a small white tile). Set `icon` on a rail entry to show a single-colour glyph
 the plugin (`"./assets/rail.svg"`). Only its shape is used, painted in the rail's colour, so colours
 in the file are ignored, and it must be transparent where nothing should draw. A missing file is a
 load diagnostic and the entry falls back to the plugin icon. The page the entry opens wears the same
-icon unless `registerPage`'s `icon` says otherwise. Full
+icon. Full
 precedence: `packages/kay-frontend-sdk/ARCHITECTURE.md`, "Plugin icon".
 
-`ui.tsx` has no `node_modules` of its own. The renderer bundles it and rewrites its `react` and
-`@bonsai/*` imports to the host's `__KAY_UI_RUNTIME__` singletons, so the agent `tsconfig.json`
+`ui.tsx` has no `node_modules` of its own. Bonsai compiles it and rewrites its `react` and
+`@bonsai/plugin-ui-sdk` imports to the host's `__KAY_UI_RUNTIME__` singletons, so the agent `tsconfig.json`
 cannot cover it, and a plugin whose UI nothing typechecks has shipped three wrong API shapes at
 once. `pnpm create-plugin --ui` generates `tsconfig.ui.json` for exactly this: its `paths` are
 derived from the bundler's own shim set (`uiRuntimeShimModules` in `@bonsai/ui-app-bundler`), each
@@ -155,15 +156,13 @@ specifier mapped to the type entry the renderer binds it to, and `npm run typech
 configs. Do not hand-write the map; when the bundler's set changes, the scaffold's test fails and
 the generated config follows.
 
-Two facts about that config worth knowing when you read errors from it:
+That config typechecks `ui.tsx` as a browser module: `Bundler` resolution, automatic JSX, DOM libs,
+no Node globals. The agent config keeps `**/*.ts`, so the two programs never overlap. Add a new page
+file to its `include`.
 
-- The bare `@bonsai/frontend-sdk` is typed against the SDK's `ui-runtime` facade, because that is
-  what the renderer binds it to. The facade carries the SDK's whole type surface, so
-  `KayUiExtensionApi` and every descriptor type import fine; a **value** only the package's main
-  entry exports fails to compile there (TS1362, "exported using export type"), which is the
-  compiler telling you the running extension would receive `undefined`.
-- It typechecks `ui.tsx` alone, as a browser module: `Bundler` resolution, automatic JSX, DOM
-  libs, no Node globals. The agent config keeps `**/*.ts`, so the two programs never overlap.
+`pnpm plugin:check` also compiles a page declared as source, so a broken import or a refused
+`@bonsai/*` package shows up there as `kay-ui-app-compile-failed`. If a class with a variant seems
+to do nothing, see "How a plugin page gets Tailwind" in `docs/frontend-styling.md`.
 
 For a plugin scaffolded before `--ui` existed, scaffold a throwaway `--ui` plugin from the same
 checkout and copy its `tsconfig.ui.json` and the second `typecheck` command into yours; `--force`