@dudousxd/nestjs-durable 0.50.0 → 0.51.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dudousxd/nestjs-durable",
-  "version": "0.50.0",
+  "version": "0.51.0",
   "description": "Durable workflows for NestJS — module, decorators, discovery and boot recovery",
   "license": "MIT",
   "author": "Davide Carvalho",
@@ -68,10 +68,10 @@
     "@dudousxd/nestjs-diagnostics": "0.5.0",
     "@tanstack/intent": "0.4.0",
     "@dudousxd/durable-worker": "0.11.2",
-    "@dudousxd/nestjs-durable-core": "^0.82.0",
+    "@dudousxd/nestjs-durable-dashboard": "0.52.0",
+    "@dudousxd/nestjs-durable-core": "^0.83.0",
     "@dudousxd/nestjs-durable-testing": "^0.21.0",
     "@dudousxd/nestjs-durable-transport-bullmq": "0.22.4",
-    "@dudousxd/nestjs-durable-dashboard": "0.52.0",
     "@dudousxd/nestjs-durable-transport-event-emitter": "^0.5.3"
   },
   "module": "./dist/index.js",

package/skills/durable-workflows/SKILL.md

@@ -98,7 +98,9 @@ const out = await ctx.step<ProcResult>('processing:proc', input);
 side has no `@Step` of its own. `@Step({ name?, input?, output?, retries?, backoff?, backoffMs?,
 backoffMaxMs?, jitter?, timeoutMs? })` additionally opts into RUNTIME validation (a Standard Schema such as zod, or a class-validator DTO
 class) (`input`
-validates before the method runs, `output` validates its return value) and a def-level durable-retry
+validates before the method runs, `output` validates its return value; a mismatch throws a
+`SchemaValidationError` from core, a `FatalError` with code `invalid_input` / `invalid_output` and
+`details.issues`) and a def-level durable-retry
 policy — a bare `@Step()` skips both and dispatches with no retry/timeout.
 
 Every dispatched step is a first-class checkpoint: on crash/replay a `completed` one returns its
@@ -309,7 +311,8 @@ async invalid(ctx: WorkflowCtx, failure: OnErrorInput<Line>): Promise<LineResult
 ```
 
 `error.details` is the third argument of `FatalError(message, code, details)` (e.g. validation
-issues). Retrying the run runs its body again; a new failure goes to a new handler run.
+issues; a `SchemaValidationError` carries `{ issues }`, and `@OnError(SchemaValidationError)` catches
+`invalid_input`, `invalid_output` and `schema_validation`). Retrying the run runs its body again; a new failure goes to a new handler run.
 It matches on `code`, never `instanceof`, must return `run`'s output type, and never sees
 cancellation (a `cancelled` run never routes), `nested_workflow_call` ctx misuse, or `non_determinism`
 (`NonDeterminismError` carries `code: 'non_determinism'`). `@Workflow({ onError: [{ code, workflow }] })` routes to another workflow.