@orkestrel/workflow 0.0.2 → 0.0.4

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.
package/README.md CHANGED
@@ -7,8 +7,8 @@ per-phase `Runner`, `Abort`, `Timeout`, `Budget`, and a cooperative
7
7
  cross-environment `Scheduler`) rather than re-implementing its own
8
8
  concurrency / retry / abort machinery. Each task's `run` is a plain
9
9
  behavior-name string resolved once into a `handler`; wiring a task to a tool
10
- or an agent is an opt-in `createToolFunction` / `createAgentFunction`
11
- adapter composed into the caller's own `functions` registry.
10
+ or an agent is an opt-in adapter shipped by the separate `@orkestrel/tool`
11
+ package, composed into the caller's own `functions` registry.
12
12
 
13
13
  ## Install
14
14
 
@@ -26,9 +26,9 @@ npm install @orkestrel/workflow
26
26
  ## Status
27
27
 
28
28
  Pre-release (`0.0.1`): the definition contract, the live entity tree, the
29
- pure-engine runner (with a `run`-string / `handler` model, the opt-in
30
- `createToolFunction` / `createAgentFunction` adapters, and the
31
- depth/cycle-bounded agent-native recursion), the durable `WorkflowStore`
29
+ pure-engine runner (a `run`-string / `handler` model the opt-in tool/agent
30
+ adapters and the depth/cycle-bounded agent-native recursion now ship in the
31
+ separate `@orkestrel/tool` package), the durable `WorkflowStore`
32
32
  (in-memory + driver-pluggable), and the cooperative `Scheduler` (the
33
33
  cross-environment default plus the browser and Node environment backends)
34
34
  are all implemented and tested, but the public API is still unstable and