@automatalabs/workflows 0.37.0 → 0.37.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +12 -3
  2. package/package.json +4 -4
package/README.md CHANGED
@@ -296,8 +296,15 @@ checkpoint unless the author opts in. `WorkflowManagerOptions` lets you set a de
296
296
  `loadSavedWorkflow` resolver (enables nested `workflow('name')`), a custom `persistence`
297
297
  implementation, and per-agent timeout/retry defaults.
298
298
 
299
- Every terminal result may also carry `fallbacks` (a compatibility audit surface for non-resolution
300
- subsystems or third-party runners) and `checkpointsTaken` (one
299
+ Usage-limit and auth resumes are continuation-aware by default on both `resumeFromRunId` and
300
+ same-ID `resume()` / `resumeInBackground()`: when the interrupted root call's index, identity hash,
301
+ full execution-input fingerprint, backend identity, cwd, and reopen support still agree, the manager
302
+ reattaches its recorded ACP session and continues the unfinished turn. Worktree calls, changed or
303
+ legacy inputs, missing cwd, and every uncertain/rejected reopen run fresh. This is internal manager →
304
+ engine plumbing; the public SDK accepts no continuation option.
305
+
306
+ Every terminal result may also carry `fallbacks` (including `kind: "continuation"` notices that
307
+ record a reattached `resume`/`load` method or an exact skip reason) and `checkpointsTaken` (one
301
308
  resolved checkpoint per call with the journaled decision and `live` / `headless-default` /
302
309
  `journal-replay` / `injected` source). They are absent when empty, persist for cold reads, never
303
310
  enter replay hashes, and are not part of `WorkflowRunStatus` inspection.
@@ -389,7 +396,9 @@ runner names.
389
396
  Every live ACP-backed `agent()` call records a non-secret re-attach handle in
390
397
  `run.agentSessions`. Set `agent(..., { keepSession: true })` to skip release-time `session/close`,
391
398
  then use the runner's `loadSession()` or `resumeSession()` host API with that record. Session
392
- handles are additive and are also preserved in journals; they do not change the deterministic
399
+ handles are additive and are also preserved in journals; pause-class failures skip `session/close`
400
+ automatically, and eligible managed resumes consume the recorded handle internally. A continued
401
+ result carries a diagnostic journal marker, but neither the handle nor marker changes deterministic
393
402
  resume identity.
394
403
 
395
404
  ### d) Bring your own backend — implement the `AgentRunner` seam
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@automatalabs/workflows",
3
- "version": "0.37.0",
3
+ "version": "0.37.1",
4
4
  "license": "Apache-2.0",
5
5
  "engines": {
6
6
  "node": ">=22"
@@ -31,9 +31,9 @@
31
31
  },
32
32
  "dependencies": {
33
33
  "typebox": "1.3.2",
34
- "@automatalabs/shared-types": "0.23.0",
35
- "@automatalabs/acp-agents": "0.28.1",
36
- "@automatalabs/workflow-engine": "0.25.0"
34
+ "@automatalabs/shared-types": "0.24.0",
35
+ "@automatalabs/workflow-engine": "0.26.0",
36
+ "@automatalabs/acp-agents": "0.29.0"
37
37
  },
38
38
  "scripts": {
39
39
  "build": "tsc -b",