@sanity/workflow-engine-test 0.10.0 → 0.11.0

package/CHANGELOG.md

@@ -1,5 +1,42 @@
 # @sanity/workflow-engine-test
 
+## 0.11.0
+
+### Minor Changes
+
+- 4e2b5bb: **BREAKING:** the bench now mirrors the engine's read/write surface exactly instead of paraphrasing it.
+  - `editDocument` performs the real write for every action it accepts, so guards scoped to that action are genuinely consulted: `publish` promotes the existing draft onto the published id and `unpublish` retracts it (both through the fake client's document actions, vetted by the guard seam under that action); previously both silently landed as a plain update and a guard scoped to `actions: ['publish']` was never consulted. `create` is no longer accepted — create through the client, which the same seam gates. The return type is now honest: `StoreDocument | undefined` (`undefined` after `delete`/`unpublish`, or when the default identity can't read the written doc) instead of a cast that crashed at runtime.
+  - Read helpers sharing an engine verb's name now delegate to that verb with the engine's args shape: `getInstance`/`listPendingEffects` (was `pendingEffects`)/`findPendingEffects` (new)/`children`/`instancesForDocument`/`definitionsForDocument` all take the engine's args objects, and missing/foreign-tag instances throw the engine's typed `InstanceNotFoundError` instead of a bench-local `Error`.
+  - `instancesByStage` speaks the engine's filter vocabulary: `definition` (was `workflowName`) and `includeCompleted` (was `openOnly` — polarity AND default flip: in-flight only unless opted in).
+  - `deleteDefinition` joins the engine-call wrappers with the same `actor:`/`grants:` identity shortcuts as every other write verb — no more routing around the bench via `createBenchEngine`.
+
+  `@sanity-labs/client-fake-for-test` ^0.8.0 (the document publish/unpublish guard-interception seam) is now a regular dependency — the bench has always imported it at runtime, but it was previously declared only as a devDependency, so an external install got a broken package.
+
+- 6a46db1: **BREAKING:** the definition root's `applicableWhen` moved to `start.filter`, inside a new `start` block — `{kind?: 'interactive' | 'autonomous', filter?: GROQ}` — describing how standalone runs begin. No alias, no dual-read: definitions authored with `applicableWhen` fail the strict parse until rewritten.
+  - `start.kind` classifies who initiates a run — a person from a start surface (`'interactive'`, the default; `startKindOf(def)` is the one reading rule) or a system reacting to a document (`'autonomous'`, hidden from human start pickers). Classification only: `startInstance` stays one verb and one code path for every caller and kind — an interactive start of an autonomous workflow is legal. Deploy invariants: a spawn-only (`lifecycle: 'child'`) definition may not declare `start`; an `'autonomous'` kind requires every required input entry to be subject-style (`doc.ref`/`doc.refs` — the shared `isSubjectEntry` rule); a `start.filter` may read only declared **input-sourced** entries via `$fields` (a typo or a query/literal entry is a silent never-pass); and a root-reading filter (`_type == …`, `@`, or a `^` escaping a scan) requires a subject entry, since a read surface with no subject never binds a root.
+  - `start.filter` is a **read-side visibility rule, not a gate** — `startInstance` never evaluates it and never throws on it; it starts whenever the caller supplies the required inputs. The filter decides what appears in / is chosen from Start lists: `definitionsForDocument`/applicability and the Studio start control evaluate it in a widened, named start-filter context (`START_FILTER_VARS`) — the candidate document as root, `$tag`/`$definition`/`$now`/`$fields` bound (`$fields` = the caller's input entries as GDR envelopes, so `$fields.<entry>.id` is the GDR URI), and `*[...]` = the workflow resource's dataset. Filters that never scan keep the cheap pure evaluation (`analyzeCondition(...).readsDataset` decides); scanning filters evaluate over a fetched slice of EVERY instance in the tag (completed included — `*` carries no hidden predicate; filters qualify in-flight themselves with `!defined(completedAt)`), so a filter can bound what surfaces (WIP limits, one-run-per-subject). Absent bindings evaluate GROQ-null and fail closed.
+
+- e5f5b77: **BREAKING:** actions become the only payload mechanism — every op, effect, and spawn in the system lives on an action; structure never does.
+  - Actions gain `when` (cascade-fired trigger: the engine fires it the moment it's true, at most once per stage visit, level-triggered; never fireAction-able) and `spawn` (the subworkflow block, unlocking caller-triggered and conditional spawn). Fires-on-entry is spelled `when: 'true'`.
+  - Deleted from the model: `activation`, activity-level `ops`/`effects`/`subworkflows`, `completeWhen`/`failWhen`, `kind`, and transition `ops`/`effects`. Transitions are pure edges `{name, when, to}` (the condition key renamed from `filter` — trigger semantics). `target` survives as the off-system marker; `kind` is now always derived, plus a new derived executor classification (autonomous / interactive / off-system / hybrid) on activity evaluations.
+  - Activities are `active` from stage entry (no `pending` status, no activation moment, no machine-step implicit); a new deploy invariant requires every activity to have a reachable path to a terminal status.
+  - A cascade hop is ONE transaction: the current stage's triggered actions run to in-memory fixpoint, then transition selection, then a single CAS commit; chain hops stay separate commits. The per-visit `firedActions` ledger on the activity entry re-arms on re-entry (a stage resets on re-entry). The cascading token executes triggered actions; `roles` on a triggered action pins which identities may execute it (an incapable token leaves it armed).
+  - The context bag split: `$effects` now carries completed effects' outputs ONLY (derived from `effectHistory`), and the new `$context` carries the `startInstance` seed plus a parent's `spawn.context` handoff (the persisted `effectsContext` field renamed `context`; `startInstance`'s seed arg renamed accordingly). `$effectStatus` is unchanged.
+  - Spawn registry rows key per (activity entry, spawning action), so two spawn actions on one activity can never cross-adopt each other's children.
+  - `fireAction` rejects a `when` action (`cascade-fired` verdict); evaluation projects triggered actions as narratable (`triggered: true` + `whenInsight`), never as buttons.
+
+### Patch Changes
+
+- Updated dependencies [11e2d6f]
+- Updated dependencies [7510fd5]
+- Updated dependencies [01e8042]
+- Updated dependencies [79c54db]
+- Updated dependencies [6a46db1]
+- Updated dependencies [35b9b85]
+- Updated dependencies [e5f5b77]
+- Updated dependencies [01e8042]
+  - @sanity/workflow-engine@0.16.0
+
 ## 0.10.0
 
 ### Minor Changes

package/README.md

@@ -20,15 +20,18 @@ Sanity client, an all-access default actor, and a bench-owned clock. Every
 wrapped verb injects the bench's client, tag, workflow resource, access
 default, and clock, so a test reads as the workflow it exercises:
 
-- **Runtime verbs** — `deployDefinitions`, `startInstance`, `fireAction`,
-  `editField`, `completeEffect` (and `completePendingEffect`, addressed by
-  effect name), `tick`, `evaluate`.
+- **Runtime verbs** — `deployDefinitions`, `deleteDefinition`, `startInstance`,
+  `fireAction`, `editField`, `completeEffect` (and `completePendingEffect`,
+  addressed by effect name), `tick`, `evaluate`.
 - **Instance-admin overrides** — `setStage`, `abortInstance`. Same injection,
   so a forced move into a deadline-gated stage evaluates `$now` at bench time,
   not wall-clock.
 - **Reads and probes** — `getInstance`, `currentStage`, `activityStatus`,
-  `pendingEffects`, `children`, `instancesForSubject`, `instancesByStage`,
-  `instancesForDocument`, `query`, plus the guard helpers below.
+  `listPendingEffects`, `findPendingEffects`, `children`, `instancesForSubject`,
+  `instancesByStage`, `instancesForDocument`, `definitionsForDocument`, `query`,
+  plus the guard helpers below. Helpers sharing an engine verb's name take the
+  engine's own args objects and throw its typed errors — bench reads and engine
+  reads cannot drift.
 
 ```ts
 const bench = createBench({now: '2026-01-01T00:00:00Z'})
@@ -59,7 +62,7 @@ ticking — never by waiting.
 ## Out-of-band engines
 
 Some tests need an engine of their own — custom effect handlers, racing two
-drainers, a `deleteDefinition` call. `createBenchEngine(bench, overrides?)`
+drainers, a custom clock. `createBenchEngine(bench, overrides?)`
 builds one on the bench's client, inheriting its tag, workflow resource, and
 clock (`overrides` win). The bench exposes `tag` and `workflowResource` for
 raw `workflow.*` calls, and the default tag ships as the `BENCH_TAG` constant.
@@ -80,7 +83,12 @@ bench gives you a helper for each:
   writes through the bench client (`patch` is a `{set?, unset?, insert?}` spec),
   and a write a deployed guard denies throws `MutationGuardDeniedError` — the
   rejection the lake is designed to apply to _any_ client once guard
-  enforcement ships; the bench reproduces it on the client it mints.
+  enforcement ships; the bench reproduces it on the client it mints. Every
+  guard action is a real write: `action: 'delete'` deletes, `'publish'`
+  promotes the existing `drafts.<id>` draft onto the published id, and
+  `'unpublish'` retracts it — so a guard scoped to `actions: ['publish']` is
+  genuinely consulted. The helper resolves to the post-write document, or
+  `undefined` once a delete/unpublish removed it.
 - **Read-time preflight** — `bench.activeGuardsForDocument(id)` answers "_would_
   a write be denied right now?" _without_ writing. This is the check a UI uses
   to disable a button or show a lock ahead of time. It's a pure read over the