ai-workflows 2.0.2 → 2.1.3

package/.turbo/turbo-build.log

@@ -1,5 +1,4 @@
-
-
-> ai-workflows@2.0.1 build /Users/nathanclevenger/projects/primitives.org.ai/packages/ai-workflows
-> tsc
-
+
+> ai-workflows@2.1.3 build /Users/nathanclevenger/projects/primitives.org.ai/packages/ai-workflows
+> tsc
+

package/.turbo/turbo-test.log

@@ -0,0 +1,169 @@
+
+> ai-workflows@2.1.1 test /Users/nathanclevenger/projects/primitives.org.ai/packages/ai-workflows
+> vitest
+
+
+ DEV  v2.1.9 /Users/nathanclevenger/projects/primitives.org.ai/packages/ai-workflows
+
+ ✓ test/context.test.ts (11 tests) 5ms
+ ✓ test/on.test.ts (8 tests) 3ms
+ ✓ test/every.test.ts (39 tests) 6ms
+ ✓ test/types-event-handler.test.ts (10 tests) 3ms
+stdout | test/types-event-handler.test.ts > EventHandler generic order - TDD RED > Type inference consistency > should support EventHandler<void, InputType> for fire-and-forget handlers
+Processing John (john@example.com)
+
+ ✓ test/cascade-context.test.ts (29 tests) 7ms
+stdout | test/types-proxy-autocomplete.test.ts > OnProxy/EveryProxy autocomplete - TDD RED > $.send type safety > should type-check send call with data
+[workflow] Welcome email sent 
+[workflow] Welcome email sent 
+
+ ✓ test/types-proxy-autocomplete.test.ts (18 tests) 4ms
+ ✓ test/dependency-graph.test.ts (41 tests) 7ms
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should deliver events to registered handlers
+[workflow] Starting with 1 event handlers and 0 schedules
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should allow chained event sending from handlers
+[workflow] Starting with 2 event handlers and 0 schedules
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should track events in state history
+[workflow] Starting with 1 event handlers and 0 schedules
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should trigger schedule handlers
+[workflow] Starting with 0 event handlers and 1 schedules
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should trigger schedule handlers
+[workflow] Stopping
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should stop schedule handlers on stop
+[workflow] Starting with 0 event handlers and 1 schedules
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should stop schedule handlers on stop
+[workflow] Stopping
+
+stdout | test/workflow.test.ts > Workflow - unified $ API > Workflow() > should support $.set and $.get for context data
+[workflow] Starting with 2 event handlers and 0 schedules
+
+(node:43941) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 2)
+(Use `node --trace-warnings ...` to show where the warning was created)
+ ✓ test/workflow.test.ts (20 tests) 10ms
+(node:43941) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 5)
+(node:43941) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 6)
+stderr | test/send.test.ts > send - event emission > send > should continue with other handlers if one throws
+Error in handler for Customer.created: Error: Handler 1 failed
+    at /Users/nathanclevenger/projects/primitives.org.ai/packages/ai-workflows/test/send.test.ts:104:50
+    at file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:146:14
+    at file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:533:11
+    at runWithTimeout (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:39:7)
+    at runTest (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1056:17)
+    at runSuite (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1205:15)
+    at runSuite (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1205:15)
+    at runSuite (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1205:15)
+    at runFiles (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1262:5)
+    at startTests (file:///Users/nathanclevenger/projects/primitives.org.ai/node_modules/.pnpm/@vitest+runner@2.1.9/node_modules/@vitest/runner/dist/index.js:1271:3)
+
+ ✓ test/send.test.ts (9 tests) 18ms
+(node:43941) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 10)
+ ✓ test/barrier-join.test.ts (29 tests) 19ms
+
+⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯
+
+Vitest caught 4 unhandled errors during the test run.
+This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.
+
+⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
+BarrierTimeoutError: Barrier timeout after 1000ms: 0/1 participants arrived
+ ❯ src/barrier.ts:302:16
+    300|     const timeoutPromise = new Promise<never>((_, reject) => {
+    301|       setTimeout(() => {
+    302|         reject(new BarrierTimeoutError(timeout, 0, promises.length))
+       |                ^
+    303|       }, timeout)
+    304|     })
+ ❯ callTimer ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2300:25
+ ❯ doTickInner ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2886:30
+ ❯ doTick ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2967:21
+ ❯ Immediate.<anonymous> ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2987:30
+ ❯ processImmediate node:internal/timers:485:21
+
+⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+Serialized Error: { timeout: 1000, arrived: +0 }
+This error originated in "test/barrier-join.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
+The latest test that might've caused the error is "should support timeout option". It might mean one of the following:
+- The error was thrown, while Vitest was running this test.
+- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
+
+⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
+BarrierTimeoutError: Barrier timeout after 1000ms: 0/2 participants arrived
+ ❯ src/barrier.ts:397:18
+    395|         } else {
+    396|           resolved = true
+    397|           reject(new BarrierTimeoutError(timeout, completed.length, n))
+       |                  ^
+    398|         }
+    399|       }, timeout)
+ ❯ callTimer ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2300:25
+ ❯ doTickInner ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2886:30
+ ❯ doTick ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2967:21
+ ❯ Immediate.<anonymous> ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2987:30
+ ❯ processImmediate node:internal/timers:485:21
+
+⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+Serialized Error: { timeout: 1000, arrived: +0 }
+This error originated in "test/barrier-join.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
+The latest test that might've caused the error is "should support timeout". It might mean one of the following:
+- The error was thrown, while Vitest was running this test.
+- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
+
+⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
+BarrierTimeoutError: Barrier timeout after 1000ms: 1/3 participants arrived
+ ❯ src/barrier.ts:194:27
+    192|         this._timeoutId = setTimeout(() => {
+    193|           if (this._waitReject) {
+    194|             const error = new BarrierTimeoutError(
+       |                           ^
+    195|               this._options.timeout!,
+    196|               this._arrived.length,
+ ❯ callTimer ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2300:25
+ ❯ doTickInner ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2886:30
+ ❯ doTick ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2967:21
+ ❯ Immediate.<anonymous> ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2987:30
+ ❯ processImmediate node:internal/timers:485:21
+
+⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+Serialized Error: { timeout: 1000, arrived: 1 }
+This error originated in "test/barrier-join.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
+The latest test that might've caused the error is "should support timeout on wait()". It might mean one of the following:
+- The error was thrown, while Vitest was running this test.
+- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
+
+⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
+BarrierTimeoutError: Barrier timeout after 1000ms: 1/3 participants arrived
+ ❯ src/barrier.ts:194:27
+    192|         this._timeoutId = setTimeout(() => {
+    193|           if (this._waitReject) {
+    194|             const error = new BarrierTimeoutError(
+       |                           ^
+    195|               this._options.timeout!,
+    196|               this._arrived.length,
+ ❯ callTimer ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2300:25
+ ❯ doTickInner ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2886:30
+ ❯ doTick ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2967:21
+ ❯ Immediate.<anonymous> ../../node_modules/.pnpm/vitest@2.1.9_@types+node@24.10.1_lightningcss@1.30.2_terser@5.16.9/node_modules/vitest/dist/chunks/vi.DgezovHB.js:2987:30
+ ❯ processImmediate node:internal/timers:485:21
+
+⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+Serialized Error: { timeout: 1000, arrived: 1 }
+This error originated in "test/barrier-join.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.
+The latest test that might've caused the error is "should include timeout details". It might mean one of the following:
+- The error was thrown, while Vitest was running this test.
+- If the error occurred after the test had been completed, this was the last documented test before it was thrown.
+⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
+
+ Test Files  10 passed (10)
+      Tests  214 passed (214)
+     Errors  4 errors
+   Start at  06:45:30
+   Duration  357ms (transform 361ms, setup 0ms, collect 657ms, tests 83ms, environment 1ms, prepare 624ms)
+
+ FAIL  Tests failed. Watching for file changes...
+       press h to show help, press q to quit

package/CHANGELOG.md

@@ -1,5 +1,34 @@
 # ai-workflows
 
+## 2.1.3
+
+### Patch Changes
+
+- Documentation and testing improvements
+  - Add deterministic AI testing suite with self-validating patterns
+  - Apply StoryBrand narrative to all package READMEs
+  - Update TESTING.md with four principles of deterministic AI testing
+  - Fix duplicate examples package name conflict
+
+## 2.1.1
+
+### Patch Changes
+
+- 6beb531: Add TDD RED phase tests for type system unification
+  - ai-functions: Add tests for AIFunction<Output, Input> generic order flip
+  - ai-workflows: Add tests for EventHandler<TOutput, TInput> order and OnProxy/EveryProxy autocomplete
+  - ai-database: Existing package - no changes in this release
+  - @primitives/types: New shared types package with failing tests for RED phase
+
+  These tests document the expected behavior for the GREEN phase implementation where generic type parameters will be reordered to put Output first (matching Promise<T> convention).
+
+## 2.0.3
+
+### Patch Changes
+
+- Updated dependencies
+  - rpc.do@0.2.0
+
 ## 2.0.2
 
 ## 2.0.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 .org.ai
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.