@yaklabs-ai/plugin-sdk 0.53.0 → 0.54.1

package/README.md

@@ -13,7 +13,7 @@ it under the name your plugin code actually imports:
 ```json
 {
   "dependencies": {
-    "@bonsai/plugin-sdk": "npm:@yaklabs-ai/plugin-sdk@^0.53.0"
+    "@bonsai/plugin-sdk": "npm:@yaklabs-ai/plugin-sdk@^0.54.1"
   }
 }
 ```
@@ -62,7 +62,7 @@ Every tool the entrypoint registers is declared in the manifest too:
   "description": "Greets people by name.",
   "version": "0.1.0",
   "namespace": "widgets",
-  "compatibility": { "sdk": "^0.53.0" },
+  "compatibility": { "sdk": "^0.54.1" },
   "targets": {
     "kay": {
       "agent": {
@@ -134,24 +134,26 @@ naming both versions, instead of loading it and finding no `activate`.
 
 ## Entrypoints
 
-| Import                                  | What it gives you                                                                        |
-| --------------------------------------- | ---------------------------------------------------------------------------------------- |
-| `@bonsai/plugin-sdk/kay-agent`          | Tools, URI modules, search providers, auth — the per-session agent surface               |
-| `@bonsai/plugin-sdk/kay-app`            | App-lifetime surface: storage, endpoints, app-scoped URI modules                         |
-| `@bonsai/plugin-sdk/uri`                | Sessionless resource caller types, revision digest and unavailable fallback, from 0.49.0 |
-| `@bonsai/plugin-sdk/endpoints`          | Sessionless cross-plugin endpoint caller and outcome types, from 0.50.0                  |
-| `@bonsai/plugin-sdk/kay-agent/testing`  | `invokeToolForTest`, `fauxAuthContext` — for your own `node --test` runs                 |
-| `@bonsai/plugin-sdk/disclosure`         | The conformance audit Bonsai gates your plugin with — run it before you ship             |
-| `@bonsai/plugin-sdk/time`               | `Temporal` (Bonsai's own instance) and the time-zone helpers, from 0.13.6                |
-| `@bonsai/plugin-sdk/transcript`         | The active-branch walk; the turn walk and run records from 0.13.6                        |
-| `@bonsai/plugin-sdk/transcript-review`  | The review fold: a session's spans, tool-call attempts and records, from 0.13.7          |
-| `@bonsai/plugin-sdk/agent-conversation` | How a session's agent-to-agent traffic groups into conversations, from 0.13.7            |
-| `@bonsai/plugin-sdk/app-data`           | The app-data size caps, on an entry with no other import, from 0.13.7                    |
-| `@bonsai/plugin-sdk/vendored-mcp`       | The kit for a plugin built on a vendor's hosted MCP server, from 0.13.7                  |
-| `@bonsai/plugin-sdk/system-one`         | The types and error class for `api.systemOne` / `app.systemOne`, from 0.13.8             |
-| `@bonsai/plugin-sdk/zod`                | `z` (the host's in the daemon), on an entry with no other import, from 0.13.9            |
-
-A plugin that imports these subpaths declares the current supported SDK range (`^0.53.0`).
+| Import                                  | What it gives you                                                                                             |
+| --------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| `@bonsai/plugin-sdk/kay-agent`          | Tools, URI modules, search providers, auth — the per-session agent surface                                    |
+| `@bonsai/plugin-sdk/kay-app`            | App-lifetime surface: storage, endpoints, app-scoped URI modules                                              |
+| `@bonsai/plugin-sdk/uri`                | Sessionless resource caller types, revision digest and unavailable fallback, from 0.49.0                      |
+| `@bonsai/plugin-sdk/endpoints`          | Sessionless cross-plugin endpoint caller and outcome types, from 0.50.0; `projectDirectories` endpoint shapes |
+| `@bonsai/plugin-sdk/kay-agent/testing`  | `invokeToolForTest`, `fauxAuthContext` — for your own `node --test` runs                                      |
+| `@bonsai/plugin-sdk/disclosure`         | The conformance audit Bonsai gates your plugin with — run it before you ship                                  |
+| `@bonsai/plugin-sdk/time`               | `Temporal` (Bonsai's own instance) and the time-zone helpers, from 0.13.6                                     |
+| `@bonsai/plugin-sdk/transcript`         | Active-branch and turn walks, message origin, preceding messages, and skill evidence folds                    |
+| `@bonsai/plugin-sdk/transcript-review`  | The review fold: a session's spans, tool-call attempts and records, from 0.13.7                               |
+| `@bonsai/plugin-sdk/agent-conversation` | How a session's agent-to-agent traffic groups into conversations, from 0.13.7                                 |
+| `@bonsai/plugin-sdk/text-diff`          | Word-level draft comparison and Unicode-safe text clipping                                                    |
+| `@bonsai/plugin-sdk/fs`                 | File I/O, shared keyed work ordering and committed-change notices                                             |
+| `@bonsai/plugin-sdk/app-data`           | The app-data size caps, on an entry with no other import, from 0.13.7                                         |
+| `@bonsai/plugin-sdk/vendored-mcp`       | The kit for a plugin built on a vendor's hosted MCP server, from 0.13.7                                       |
+| `@bonsai/plugin-sdk/system-one`         | The types and error class for `api.systemOne` / `app.systemOne`, from 0.13.8                                  |
+| `@bonsai/plugin-sdk/zod`                | `z` (the host's in the daemon), on an entry with no other import, from 0.13.9                                 |
+
+A plugin that imports these subpaths declares the current supported SDK range (`^0.54.1`).
 The rows record when each subpath appeared, not retained runtime compatibility. `vendored-mcp` builds the plugin's URI module (its link cards and help); hosting the
 vendor's MCP server itself is a separate host decision: Bonsai hosts it once a person approves
 the plugin's `mcp.host-server` grant for that server's name and URL. A server that needs an OAuth
@@ -159,7 +161,7 @@ sign-in names one of the plugin's auth services in `authService`; that service m
 one `delegated` scheme, which Bonsai uses to sign the person in to the server. Bonsai declares that
 scheme at runtime; the plugin's code must not declare it again. From 0.16.2 a plugin's code can also
 call the server's tools through `api.vendoredMcp.port(<server>)`, typed by this subpath's
-`VendoredMcpPort` and `VendoredMcpOutcome` (declare `^0.53.0`).
+`VendoredMcpPort` and `VendoredMcpOutcome` (declare `^0.54.1`).
 
 From 0.13.10 the manifest schema carries two facts Bonsai reads for its own plugins only; another
 plugin's are ignored, with a load diagnostic. An `external-cli` auth scheme's `cli` says how Bonsai
@@ -241,7 +243,7 @@ Provider schemas remain authoritative; declaring a dependency grants no authorit
 through `app.uri`, parse returned Markdown in the consuming plugin, and retain the read's
 revision (or `contentDigest` from `/uri`) for edits. The old `memory.read` and `memory.write`
 grants do not authorize the replacement scheme-and-verb calls. Contracts before 0.49.0 are
-refused; migrate and declare `^0.53.0`. The current host also serves the 0.49.0 resource contract.
+refused; migrate and declare `^0.54.1`. The current host also serves the 0.49.0 resource contract.
 
 ## What this package is, and is not, at runtime
 
@@ -306,3 +308,14 @@ relative imports. Multi-file entrypoints are supported, and TypeScript syntax
 that native stripping cannot execute, such as enums, namespaces, constructor
 parameter properties, and decorators, is compiled into the bundle. The host
 SDK remains external and is supplied by the running Bonsai app.
+
+## Plugin workers
+
+SDK 0.54.1 lets either backend target run a declared module in a fresh child process.
+Declare `workers: [{ localId: "analyze", module: "./src/analyze.ts" }]` at the manifest's top
+level, export `run(input)` from that module, and call
+`api.workers.run("analyze", input, { timeoutMs: 10_000 })` (or `app.workers.run`). Input and
+return values must be JSON. An optional `signal` cancels the call. The host terminates the child
+on cancellation, timeout or plugin disposal; limits and child failures reject with
+`PluginWorkerError`. Import the capability and error from `@bonsai/plugin-sdk/workers`.
+Calls identify only a worker declared by this plugin and cannot supply executable paths or code.

package/THIRD-PARTY-INVENTORY.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 1,
   "package": "@yaklabs-ai/plugin-sdk",
-  "version": "0.53.0",
+  "version": "0.54.1",
   "target": "npm",
   "firstPartyLicense": "MIT",
   "bundled": [

package/dist/canonical-transcript.d.ts

@@ -31,6 +31,19 @@ declare type AgentSessionEvent = Exclude<HerdHarnessEvent, {
 
 declare const Alpha: TAlpha;
 
+/**
+ * The ids of the blocks that start a new answer stretch. A person's mid-turn message
+ * (`steer_message`) always does. A background input does when the agent answered both before
+ * it and after it, so the reply it wakes never turns the earlier answer into a folded middle
+ * one. An input with no answer on one side cannot fold one, so it joins the stretch it lands
+ * in: a result absorbed mid-run, or a wake the agent left unanswered, starts nothing. When
+ * several inputs arrive between two answers, the first one starts the stretch.
+ *
+ * The turn's opening (the person's message that caused it) is not a block and is never listed;
+ * the first stretch starts there.
+ */
+export declare function answerStretchStarts(blocks: readonly CanonicalAgentBlock[]): ReadonlySet<string>;
+
 /** Compatibility settings for Anthropic Messages-compatible APIs. */
 declare interface AnthropicMessagesCompat extends Static<typeof AnthropicMessagesCompatSchema> {
 }
@@ -1343,6 +1356,16 @@ declare function DependentOptions(type: TDependent): TSchemaOptions;
  */
 declare type DetachedWorkResultChannel = "next_turn" | "steer";
 
+declare interface DetailsAudienceRow extends TranscriptTypeRowBase {
+    /** `undefined` when the details carry no discriminant this row can read. */
+    readonly audience: (details: unknown) => TranscriptAudience | undefined;
+    /**
+     * What a surface does with a message whose audience cannot be read: hide it, show a generic
+     * version, or show it as unrecognized.
+     */
+    readonly onUndecodable: "hide" | "generic" | "unrecognized";
+}
+
 declare interface DiagnosticErrorInfo {
     name?: string;
     message: string;
@@ -1647,6 +1670,10 @@ declare interface FinalOutputCapture {
     readonly sessionTitle?: string;
 }
 
+declare interface FixedAudienceRow extends TranscriptTypeRowBase {
+    readonly audience: TranscriptAudience;
+}
+
 /** Creates a Function type. */
 declare function _Function_<Parameters extends TSchema[], ReturnType extends TSchema>(parameters: [...Parameters], returnType: ReturnType, options?: TSchemaOptions): TFunction<Parameters, ReturnType>;
 
@@ -4535,6 +4562,15 @@ declare type StaticVoid = void;
 
 declare type StopReason = "pending" | "stop" | "length" | "toolUse" | "error" | "aborted" | "deferred";
 
+/**
+ * The settled helper and command results that open the stretch starting at `blocks[start]`: the
+ * results among the custom messages that arrived together there, before the agent's next step.
+ * A bar whose stretch opens with any shows its background result line in place of a work
+ * headline, so the headline writer labels no such bar. Empty for a stretch a person's message,
+ * a bare wake or an automation starts.
+ */
+export declare function stretchOpeningResults(blocks: readonly CanonicalAgentBlock[], start: number): readonly CanonicalCustomMessageBlock[];
+
 /** Matches a literal String with the given quotes */
 declare function String_2<Quotes extends string[], Input extends string>(quotes: [...Quotes], input: Input): TString<Quotes, Input>;
 
@@ -7229,6 +7265,36 @@ declare type TPropertyValues<Properties extends TProperties, Keys extends string
 
 declare type TPropertyValuesReduce<Properties extends TProperties, Keys extends string[], Result extends TSchema[] = []> = Keys extends [infer Left extends string, ...infer Right extends string[]] ? Left extends keyof Properties ? TPropertyValuesReduce<Properties, Right, [...Result, Properties[Left]]> : TPropertyValuesReduce<Properties, Right, Result> : Result;
 
+/** Every row, keyed by `customType`. */
+export declare const TRANSCRIPT_TYPE_TABLE: ReadonlyMap<string, TranscriptTypeRow>;
+
+/**
+ * Who a type is written for: the person reading the transcript, the model only, or the host
+ * alone (records the daemon or the kernel reads back and no surface shows).
+ */
+declare type TranscriptAudience = "person" | "model" | "host-only";
+
+/** The kind of information a row carries; `unrecognized` is content the app cannot classify. */
+declare type TranscriptKind = "said" | "work" | "ask" | "result" | "context" | "notice" | "unrecognized";
+
+/** The card a message answers: the `ui_render` call that drew it, and the element when known. */
+declare interface TranscriptTypeAnswer {
+    readonly toolCallId: string;
+    readonly elementId?: string;
+}
+
+declare type TranscriptTypeRow = FixedAudienceRow | DetailsAudienceRow;
+
+declare interface TranscriptTypeRowBase extends CustomMessagePlacementRow {
+    /** Every kind this type can carry; a type whose kind depends on its details lists each. */
+    readonly kinds: readonly [TranscriptKind, ...TranscriptKind[]];
+    /**
+     * Present on a type the card it answers draws (the answer, a sent-draft record), so it paints
+     * no row of its own whatever its audience.
+     */
+    readonly answers?: (details: unknown) => TranscriptTypeAnswer | undefined;
+}
+
 declare type TReadonly<Type extends TSchema = TSchema> = (Type & {
     '~readonly': true;
 });