@voyant-travel/workflows-orchestrator 0.107.11 → 0.108.0

package/README.md

@@ -3,8 +3,8 @@
 Reference orchestrator for Voyant Workflows. Drives runs through the
 tenant step handler over the v1 wire protocol. Transport- and
 storage-agnostic: compose with a `RunRecordStore` of your choice
-(in-memory for tests, Postgres-backed for production, DO-backed via
-[`@voyant-travel/workflows-orchestrator-cloudflare`](../workflows-orchestrator-cloudflare)).
+(in-memory for tests, Postgres-backed for production through
+[`@voyant-travel/workflows-orchestrator-node`](../workflows-orchestrator-node)).
 
 See [`docs/runtime-protocol.md`](../../docs/runtime-protocol.md) §2 +
 §5 for the contract this implements.
@@ -20,8 +20,8 @@ import {
 import { handleStepRequest } from "@voyant-travel/workflows/handler";
 
 // A StepHandler calls into the tenant's workflow code. In-process
-// here via `handleStepRequest`; over HTTP in production via
-// @voyant-travel/workflows-orchestrator-cloudflare's dispatch-namespace adapter.
+// here via `handleStepRequest`; production Node deployments normally
+// use the node runtime package.
 const handler: StepHandler = async (req) => handleStepRequest(req);
 
 const store = createInMemoryRunStore();
@@ -71,6 +71,5 @@ The authoring SDK (`@voyant-travel/workflows`) describes workflows and
 provides the in-process executor. The orchestrator consumes that
 SDK's wire protocol — it doesn't care how the tenant runs the body,
 only about the request/response shape. Separating them keeps the
-orchestrator transport-neutral (in-process, HTTP, Durable Objects,
-future adapters) and makes it easy to test the full loop without
-any network or Cloudflare dependency.
+orchestrator transport-neutral and makes it easy to test the full loop
+without any network dependency.

package/dist/driver-inmemory.js

@@ -291,10 +291,10 @@ export function createInMemoryDriver(opts = {}) {
                     concurrency.releaseRun(out.record);
                 }
             },
-            // streamRun is not implemented for InMemory in PR1. Dashboards that
+            // streamRun is not implemented for InMemory. Dashboards that
             // probe `driver.admin.streamRun` get `undefined` and fall back to
-            // their non-streaming view. Mode 2 + Mode 1 implement this in later
-            // PRs against their respective journal sources.
+            // their non-streaming view. Node/Postgres and legacy Cloudflare
+            // drivers can provide their own journal streams.
         };
         return {
             registerManifest,

package/dist/event-router.js

@@ -2,11 +2,11 @@
 // filters match and produce the per-match descriptors drivers feed into
 // `trigger()`.
 //
-// Drivers (InMemory, Mode 2 / Postgres, Mode 1 / CF edge) wrap this in
+// Drivers (InMemory, Node/Postgres, legacy Cloudflare Worker/DO) wrap this in
 // their own `ingestEvent` impl: they fetch the manifest from their store,
 // call `routeEvent(...)`, then invoke `trigger()` per match.
 //
-// Architecture: docs/architecture/workflows-runtime-architecture.md §15.
+// Architecture: docs/architecture/workflows-runtime-architecture.md.
 import { evaluatePredicate, projectInput, } from "@voyant-travel/workflows/events";
 // ---- Public API ----
 /**

package/dist/testing/driver-compliance.d.ts

@@ -22,22 +22,23 @@ export declare function buildTestManifest(versionId?: string): WorkflowManifest;
 /**
  * Opt-in capability flags for drivers that don't share a process with
  * step bodies. Default to `true` because in-process drivers (InMemory,
- * Mode 2) satisfy every contract. Out-of-process drivers (Mode 1 / CF
- * edge — orchestrator and tenant live in separate Worker isolates) opt
- * out of in-process-only assertions like `ctx.services` threading.
+ * Node/Postgres) satisfy every contract. Out-of-process drivers (legacy
+ * Cloudflare Worker/DO deployments, where orchestrator and tenant live in
+ * separate Worker isolates) opt out of in-process-only assertions like
+ * `ctx.services` threading.
  */
 export interface DriverComplianceCapabilities {
     /**
      * When true, the framework's `ModuleContainer` is plumbed to step
-     * bodies via `ctx.services`. False for Mode 1, where the orchestrator
-     * and tenant are separate Workers and a per-tenant container would
-     * have to ship across a serialization boundary.
+     * bodies via `ctx.services`. False for legacy Cloudflare deployments,
+     * where the orchestrator and tenant are separate Workers and a per-tenant
+     * container would have to ship across a serialization boundary.
      */
     servicesThreading?: boolean;
     /**
      * When true, `admin.listRuns(...)` returns runs the driver knows about.
-     * False for self-host Mode 1, which has no native cross-run query
-     * layer (per architecture doc §8.3) — `listRuns` exists but returns
+     * False for legacy Cloudflare deployments, which have no native cross-run
+     * query layer — `listRuns` exists but returns
      * an empty page; voyant-cloud provides an index in its repo.
      */
     crossRunQueries?: boolean;
@@ -49,7 +50,7 @@ export interface DriverComplianceCapabilities {
     autoDatetimeWakeups?: boolean;
     /**
      * When true, workflow-level `WorkflowConfig.concurrency` is enforced
-     * for in-process workflow definitions. False for Mode 1 / Cloudflare
+     * for in-process workflow definitions. False for legacy Cloudflare
      * until it grows a cross-run coordination DO.
      */
     workflowConcurrency?: boolean;

package/dist/testing/driver-compliance.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"driver-compliance.d.ts","sourceRoot":"","sources":["../../src/testing/driver-compliance.ts"],"names":[],"mappings":"AAqBA,OAAO,KAAK,EACV,aAAa,EACb,iBAAiB,EACjB,eAAe,EAChB,MAAM,iCAAiC,CAAA;AAExC,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,mCAAmC,CAAA;AAKzE;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,GAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAM,GAAG,eAAe,CAa1F;AAED;;;;GAIG;AACH,wBAAgB,eAAe,CAC7B,QAAQ,GAAE,eAAuC,GAChD,iBAAiB,GAAG;IAAE,IAAI,EAAE,KAAK,CAAC,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC,CAAA;CAAE,CAOhE;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,CAAC,SAAS,SAAe,GAAG,gBAAgB,CAc5E;AA4BD;;;;;;GAMG;AACH,MAAM,WAAW,4BAA4B;IAC3C;;;;;OAKG;IACH,iBAAiB,CAAC,EAAE,OAAO,CAAA;IAC3B;;;;;OAKG;IACH,eAAe,CAAC,EAAE,OAAO,CAAA;IACzB;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAA;IAC7B;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAA;CAC9B;AAID,wBAAgB,wBAAwB,CACtC,IAAI,EAAE,MAAM,EACZ,WAAW,EAAE,MAAM,aAAa,EAChC,YAAY,GAAE,4BAAiC,GAC9C,IAAI,CAqnBN"}
+{"version":3,"file":"driver-compliance.d.ts","sourceRoot":"","sources":["../../src/testing/driver-compliance.ts"],"names":[],"mappings":"AAqBA,OAAO,KAAK,EACV,aAAa,EACb,iBAAiB,EACjB,eAAe,EAChB,MAAM,iCAAiC,CAAA;AAExC,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,mCAAmC,CAAA;AAKzE;;;;GAIG;AACH,wBAAgB,mBAAmB,CAAC,OAAO,GAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAM,GAAG,eAAe,CAa1F;AAED;;;;GAIG;AACH,wBAAgB,eAAe,CAC7B,QAAQ,GAAE,eAAuC,GAChD,iBAAiB,GAAG;IAAE,IAAI,EAAE,KAAK,CAAC,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC,CAAC,CAAC,CAAA;CAAE,CAOhE;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,CAAC,SAAS,SAAe,GAAG,gBAAgB,CAc5E;AA4BD;;;;;;;GAOG;AACH,MAAM,WAAW,4BAA4B;IAC3C;;;;;OAKG;IACH,iBAAiB,CAAC,EAAE,OAAO,CAAA;IAC3B;;;;;OAKG;IACH,eAAe,CAAC,EAAE,OAAO,CAAA;IACzB;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAA;IAC7B;;;;OAIG;IACH,mBAAmB,CAAC,EAAE,OAAO,CAAA;CAC9B;AAID,wBAAgB,wBAAwB,CACtC,IAAI,EAAE,MAAM,EACZ,WAAW,EAAE,MAAM,aAAa,EAChC,YAAY,GAAE,4BAAiC,GAC9C,IAAI,CAqnBN"}

package/dist/testing/driver-compliance.js

@@ -2,7 +2,7 @@
 //
 // `runDriverComplianceSuite(name, makeDriver)` is parameterized over a
 // driver factory. It runs identical assertions against every implementation
-// we ship: InMemory, Mode 2 / Postgres, Mode 1 / CF edge.
+// we ship: InMemory, Node/Postgres, and legacy Cloudflare Worker/DO.
 //
 // Importable from a regular `.ts` file so downstream packages
 // (`@voyant-travel/workflows-orchestrator-node`, `-cloudflare`) can run the
@@ -16,7 +16,7 @@
 // idempotency dedup, ingestEvent's manifest-not-registered + no-filters
 // paths, ctx.services, basic admin reads, shutdown.
 //
-// Architecture: docs/architecture/workflows-runtime-architecture.md §6.4.
+// Architecture: docs/architecture/workflows-runtime-architecture.md.
 import { __resetRegistry, workflow } from "@voyant-travel/workflows";
 import { beforeEach, describe, expect, test, vi } from "vitest";
 import { WorkflowConcurrencyRejectedError } from "../concurrency.js";
@@ -84,7 +84,7 @@ function testReleaseCapabilities() {
     };
 }
 // Per-test counter so workflow ids stay unique across tests in a suite —
-// some persistent stores (Mode 2's Postgres) carry state between tests in
+// some persistent stores (Node/Postgres) carry state between tests in
 // the same run, and a duplicate id would HMR-warn at minimum and
 // pollute results at worst.
 let suiteCounter = 0;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@voyant-travel/workflows-orchestrator",
-  "version": "0.107.11",
+  "version": "0.108.0",
   "description": "Reference orchestrator core for Voyant Workflows — drives runs through the tenant step handler over the v1 wire protocol.",
   "license": "Apache-2.0",
   "repository": {
@@ -30,7 +30,7 @@
     "NOTICE"
   ],
   "dependencies": {
-    "@voyant-travel/workflows": "^0.107.11"
+    "@voyant-travel/workflows": "^0.108.0"
   },
   "devDependencies": {
     "@types/node": "^20.12.0",

package/src/driver-inmemory.ts

@@ -387,10 +387,10 @@ export function createInMemoryDriver(opts: InMemoryDriverOptions = {}): DriverFa
         }
       },
 
-      // streamRun is not implemented for InMemory in PR1. Dashboards that
+      // streamRun is not implemented for InMemory. Dashboards that
       // probe `driver.admin.streamRun` get `undefined` and fall back to
-      // their non-streaming view. Mode 2 + Mode 1 implement this in later
-      // PRs against their respective journal sources.
+      // their non-streaming view. Node/Postgres and legacy Cloudflare
+      // drivers can provide their own journal streams.
     }
 
     return {

package/src/event-router.ts

@@ -2,11 +2,11 @@
 // filters match and produce the per-match descriptors drivers feed into
 // `trigger()`.
 //
-// Drivers (InMemory, Mode 2 / Postgres, Mode 1 / CF edge) wrap this in
+// Drivers (InMemory, Node/Postgres, legacy Cloudflare Worker/DO) wrap this in
 // their own `ingestEvent` impl: they fetch the manifest from their store,
 // call `routeEvent(...)`, then invoke `trigger()` per match.
 //
-// Architecture: docs/architecture/workflows-runtime-architecture.md §15.
+// Architecture: docs/architecture/workflows-runtime-architecture.md.
 
 import {
   evaluatePredicate,

package/src/testing/driver-compliance.ts

@@ -2,7 +2,7 @@
 //
 // `runDriverComplianceSuite(name, makeDriver)` is parameterized over a
 // driver factory. It runs identical assertions against every implementation
-// we ship: InMemory, Mode 2 / Postgres, Mode 1 / CF edge.
+// we ship: InMemory, Node/Postgres, and legacy Cloudflare Worker/DO.
 //
 // Importable from a regular `.ts` file so downstream packages
 // (`@voyant-travel/workflows-orchestrator-node`, `-cloudflare`) can run the
@@ -16,7 +16,7 @@
 // idempotency dedup, ingestEvent's manifest-not-registered + no-filters
 // paths, ctx.services, basic admin reads, shutdown.
 //
-// Architecture: docs/architecture/workflows-runtime-architecture.md §6.4.
+// Architecture: docs/architecture/workflows-runtime-architecture.md.
 
 import { __resetRegistry, workflow } from "@voyant-travel/workflows"
 import type {
@@ -100,7 +100,7 @@ function testReleaseCapabilities(): WorkflowManifest["capabilities"] {
 }
 
 // Per-test counter so workflow ids stay unique across tests in a suite —
-// some persistent stores (Mode 2's Postgres) carry state between tests in
+// some persistent stores (Node/Postgres) carry state between tests in
 // the same run, and a duplicate id would HMR-warn at minimum and
 // pollute results at worst.
 let suiteCounter = 0
@@ -115,22 +115,23 @@ const DATETIME_WAKEUP_TEST_TIMEOUT_MS = 5_000
 /**
  * Opt-in capability flags for drivers that don't share a process with
  * step bodies. Default to `true` because in-process drivers (InMemory,
- * Mode 2) satisfy every contract. Out-of-process drivers (Mode 1 / CF
- * edge — orchestrator and tenant live in separate Worker isolates) opt
- * out of in-process-only assertions like `ctx.services` threading.
+ * Node/Postgres) satisfy every contract. Out-of-process drivers (legacy
+ * Cloudflare Worker/DO deployments, where orchestrator and tenant live in
+ * separate Worker isolates) opt out of in-process-only assertions like
+ * `ctx.services` threading.
  */
 export interface DriverComplianceCapabilities {
   /**
    * When true, the framework's `ModuleContainer` is plumbed to step
-   * bodies via `ctx.services`. False for Mode 1, where the orchestrator
-   * and tenant are separate Workers and a per-tenant container would
-   * have to ship across a serialization boundary.
+   * bodies via `ctx.services`. False for legacy Cloudflare deployments,
+   * where the orchestrator and tenant are separate Workers and a per-tenant
+   * container would have to ship across a serialization boundary.
    */
   servicesThreading?: boolean
   /**
    * When true, `admin.listRuns(...)` returns runs the driver knows about.
-   * False for self-host Mode 1, which has no native cross-run query
-   * layer (per architecture doc §8.3) — `listRuns` exists but returns
+   * False for legacy Cloudflare deployments, which have no native cross-run
+   * query layer — `listRuns` exists but returns
    * an empty page; voyant-cloud provides an index in its repo.
    */
   crossRunQueries?: boolean
@@ -142,7 +143,7 @@ export interface DriverComplianceCapabilities {
   autoDatetimeWakeups?: boolean
   /**
    * When true, workflow-level `WorkflowConfig.concurrency` is enforced
-   * for in-process workflow definitions. False for Mode 1 / Cloudflare
+   * for in-process workflow definitions. False for legacy Cloudflare
    * until it grows a cross-run coordination DO.
    */
   workflowConcurrency?: boolean