feat(examples)!: port to the v8 split API and demonstrate signals, queries, errors, and schedules

Port the order-processing example to the TypedClient/ContractClient split
(TypedClient.create({ client }).get() + .for(contract), synchronous
getHandle, qualifyFailure) and extend it across the advertised surface:
an approval signal + payload-less defineSignal() cancellation, an
argument-less defineQuery({ output }) status query, a PaymentDeclined
typed contract error travelling activity -> workflow -> client (matched
with P.tag), and a schedule-driven activity-less cleanupExpiredOrders
workflow with the ScheduleAlreadyExistsError create-if-absent idiom.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: btravers

examples/README.md

@@ -6,15 +6,15 @@
 
 ### [order-processing-contract](./order-processing-contract)
 
-Shared contract package — domain schemas and the workflow/activity definitions imported by both the worker and the client
+Shared contract package — domain schemas plus the workflow, activity, signal, query, and typed-error definitions imported by both the worker and the client (composition-first with the `define*` helpers)
 
 ### [order-processing-worker](./order-processing-worker)
 
-Worker with Clean Architecture; activities return `AsyncResult` from unthrown
+Worker with Clean Architecture; activities return `AsyncResult` from unthrown, the workflow handles signals/queries via `context.defineSignal`/`defineQuery`, and a schedule-driven cleanup workflow shows the activity-less workflow shape
 
 ### [order-processing-client](./order-processing-client)
 
-Standalone client demonstrating interaction with the shared contract
+Standalone client demonstrating the `TypedClient.create({ client }).for(contract)` split: typed signals (with and without payload), an argument-less query, a typed `PaymentDeclined` contract error matched with `P.tag`, and a recurring schedule with the create-if-absent idiom
 
 **Note**: The client example works with the worker implementation seamlessly through the shared contract (`orderProcessingContract`).
 

examples/order-processing-client/README.md

@@ -6,11 +6,19 @@ This sample demonstrates that a single client can interact with any worker imple
 
 ## Overview
 
-This client package demonstrates that:
-
-- The `order-processing-worker` implements the **unified contract**
-- The client works with the worker implementation through the shared contract
-- Workers handle errors internally using the Result/Future pattern with ApplicationFailure
+This client package demonstrates:
+
+- The `TypedClient.create({ client })` (connection-scoped root) +
+  `.for(contract)` (contract-scoped client) split
+- Typed signals through the workflow handle — `approveOrder` with a validated
+  payload, and the payload-less `cancelRequested` sent with no arguments
+- An argument-less query (`getOrderStatus`) reading live workflow state
+- The synchronous `getHandle`, returning a `Result` whose only Err is
+  `WorkflowNotInContractError`
+- A typed contract error (`PaymentDeclined`) rehydrated from a failed
+  execution and matched exhaustively with unthrown's `match` + `P.tag`
+- A recurring cleanup schedule via `schedule.create(...)`, with the
+  `ScheduleAlreadyExistsError` branch implementing the create-if-absent idiom
 
 ## Running the Sample
 
@@ -47,17 +55,15 @@ pnpm dev
 
 ## Testing
 
-The client includes integration tests that verify:
-
-- Workflow execution through the contract
-- Proper input validation via contract schema
-- Correct output types matching contract schema
-- Workflow history and metadata access
-
-Run tests:
+Integration tests live in the worker package
+(`../order-processing-worker/src/integration.spec.ts`) and cover the same
+surface this client demonstrates — start/execute, the approval signal + status
+query, the payload-less cancellation signal, input validation, and the typed
+`PaymentDeclined` contract error:
 
 ```bash
-pnpm test
+cd ../order-processing-worker
+pnpm test:integration # requires Docker (testcontainers)
 ```
 
 ## What to Notice
@@ -73,15 +79,21 @@ pnpm test
 
 The unified contract (`orderProcessingContract`) defines:
 
-- Global activities: `log`, `sendNotification`
+- Global activities: `sendNotification`, `purgeExpiredOrders`
 - Workflow: `processOrder`
-  - Activities: `processPayment`, `reserveInventory`, `releaseInventory`, `createShipment`, `refundPayment`
+  - Activities: `processPayment` (with the `PaymentDeclined` typed error), `reserveInventory`, `releaseInventory`, `createShipment`, `refundPayment`
+  - Signals: `approveOrder` (payload), `cancelRequested` (payload-less)
+  - Query: `getOrderStatus` (argument-less)
+  - Errors: `PaymentDeclined`
+- Workflow: `cleanupExpiredOrders` (activity-less; started by the schedule)
 
 ### Worker Implementation
 
 The worker (`examples/order-processing-worker`) uses `@temporal-contract/worker` with:
 
-- Activities using the Result/Future pattern with ApplicationFailure
+- Activities returning unthrown `AsyncResult` values (never throwing), with
+  `ApplicationFailure` for technical faults and typed constructors for
+  contract errors
 - Clean Architecture with dependency injection
 - Standalone TypeScript application