@poncho-ai/harness 0.60.0 → 0.60.1

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @poncho-ai/harness@0.60.0 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
+> @poncho-ai/harness@0.60.1 build /home/runner/work/poncho-ai/poncho-ai/packages/harness
 > node scripts/embed-docs.js && tsup src/index.ts --format esm --dts
 
 [embed-docs] Generated poncho-docs.ts with 4 topics
@@ -8,9 +8,9 @@
 CLI tsup v8.5.1
 CLI Target: es2022
 ESM Build start
+ESM dist/index.js            574.16 KB
 ESM dist/isolate-F2PPSUL6.js 53.82 KB
-ESM dist/index.js            574.06 KB
-ESM ⚡️ Build success in 251ms
+ESM ⚡️ Build success in 245ms
 DTS Build start
-DTS ⚡️ Build success in 7890ms
-DTS dist/index.d.ts 105.18 KB
+DTS ⚡️ Build success in 7563ms
+DTS dist/index.d.ts 105.62 KB

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @poncho-ai/harness
 
+## 0.60.1
+
+### Patch Changes
+
+- [`47d92ba`](https://github.com/cesr/poncho-ai/commit/47d92ba6e0001147423ffda39f9dbeb29b5ca359) Thanks [@cesr](https://github.com/cesr)! - Forward `volatileContext` and `telemetryAttributes` through `continueFromToolResult`. The per-conversation capture already covers same-process continuations, but a checkpoint resumed after a process restart would silently lose the embedder's volatile blocks; resume callers can now pass them explicitly.
+
 ## 0.60.0
 
 ### Minor Changes

package/dist/index.d.ts

@@ -1635,6 +1635,13 @@ declare class AgentHarness {
          *  otherwise the continuation falls back to the agent definition's
          *  (possibly concurrently-mutated) frontmatter model. */
         model?: string;
+        /** Same as `RunInput.volatileContext`. Pass it explicitly on resume —
+         *  the per-conversation capture covers same-process continuations, but
+         *  a checkpoint resumed after a restart would otherwise lose the
+         *  embedder's volatile blocks. */
+        volatileContext?: string;
+        /** Same as `RunInput.telemetryAttributes`, for the continuation run. */
+        telemetryAttributes?: Record<string, string>;
     }): AsyncGenerator<AgentEvent>;
     runToCompletion(input: RunInput): Promise<HarnessRunOutput>;
 }

package/dist/index.js

@@ -12229,7 +12229,9 @@ ${this.skillFingerprint}`;
       parameters: input.parameters,
       abortSignal: input.abortSignal,
       suppressTelemetry: input.suppressTelemetry,
-      model: input.model
+      model: input.model,
+      volatileContext: input.volatileContext,
+      telemetryAttributes: input.telemetryAttributes
     });
   }
   async runToCompletion(input) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poncho-ai/harness",
-  "version": "0.60.0",
+  "version": "0.60.1",
   "description": "Agent execution runtime - conversation loop, tool dispatch, streaming",
   "repository": {
     "type": "git",

package/src/harness.ts

@@ -4109,6 +4109,13 @@ Code is wrapped in an async IIFE — use \`return\` to return a value to the too
      *  otherwise the continuation falls back to the agent definition's
      *  (possibly concurrently-mutated) frontmatter model. */
     model?: string;
+    /** Same as `RunInput.volatileContext`. Pass it explicitly on resume —
+     *  the per-conversation capture covers same-process continuations, but
+     *  a checkpoint resumed after a restart would otherwise lose the
+     *  embedder's volatile blocks. */
+    volatileContext?: string;
+    /** Same as `RunInput.telemetryAttributes`, for the continuation run. */
+    telemetryAttributes?: Record<string, string>;
   }): AsyncGenerator<AgentEvent> {
     const messages = [...input.messages];
     const lastMsg = messages[messages.length - 1];
@@ -4169,6 +4176,8 @@ Code is wrapped in an async IIFE — use \`return\` to return a value to the too
       abortSignal: input.abortSignal,
       suppressTelemetry: input.suppressTelemetry,
       model: input.model,
+      volatileContext: input.volatileContext,
+      telemetryAttributes: input.telemetryAttributes,
     });
   }