@sanity/workflow-cli 0.29.0 → 0.30.0

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # @sanity/workflow-cli
 
+## 0.30.0
+
+### Minor Changes
+
+- 90207dc: **BREAKING:** `assertReaderModelAcknowledgement` now requires `{requiredMinReaderModel, context?}` instead of a context string, and `ReaderModelAcknowledgementError` accepts its optional context through `{context}`. The Blueprint package's `AcknowledgedDeployment` type moves to the engine as `AcknowledgedWorkflowDeployment`; update imports and use that shared name. Assignment-valued fields can now declare a non-empty `roles` list that limits newly written assignees. Existing fields without `roles` stay unconstrained, retain reader floor 4, and continue deploying with `expectedMinReaderModel: 4`; installing this release requires no coordinated rollout or configuration change.
+
+  Before adding `roles`, upgrade every Studio, CLI, MCP server, Function, and other runtime that shares the affected workflow resource, then change that deployment's literal `expectedMinReaderModel` to `8`. MCP deployments pass the same reviewed literal as the optional `expectedMinReaderModel` tool argument. Definitions and instances carrying the facet require reader model 8. User assignees qualify through direct roles or the definition's role aliases, while collective role assignees must literally match one configured role. Studio assignment controls, including manual start, auto-start, and assignees nested in to-do rows, offer only eligible choices while retaining stale current values so editors can remove or replace them. Constrained pickers name the active eligible roles and distinguish an empty eligible set from a search with no matches. Top-level plural and composite edits retain no more occurrences of a stale assignment at each declared assignment location than the previous value contained; removal and reordering therefore work, while an added copy is a new assignment and must qualify. Direct singular replacements and every assignment present in an `updateWhere` fragment remain strict. Each engine verb uses one member-directory snapshot across retries, cascade hops, and spawned children, then the next verb reads current membership.
+
+  Malformed project-member and project-user directory responses now fail loudly instead of treating bad rows or role records as missing users, and actor resolution reports those failures as `inaccessible`, so integrations can distinguish directory failures from absent membership.
+
+  CLI `start` and `definition delete` no longer apply the definition-submission acknowledgement gate; deploy, check, dry-run, definition diff, Blueprint provision, and engine definition APIs still validate the selected definitions' required floor.
+
+  No reader-fleet rollout or deployment-literal change is required for existing definitions that do not use `roles`.
+
+  **Docs impact:** Update the assignment field reference and authoring examples for `roles`, distinguish eligibility from editability, action permission, and literal queue ownership, and add the model-8 conditional adoption sequence to the prerelease rollout guide.
+
+- b0b1550: **BREAKING:** Product-prefixed telemetry events now use `Workflows <event>` instead of `Editorial Workflows <event>`; `EditorialWorkflowsResource` is replaced by `WorkflowsResource`; and `defineWorkflows` now generates `workflows-<deployment name>` resource names instead of `editorial-workflows-<deployment name>`. Telemetry consumers matching the previous literals stop receiving events until updated, TypeScript consumers importing the previous Blueprint interface no longer compile, and an existing Blueprint stack that relies on the generated name treats the new default as a different resource identity.
+
+  Update telemetry dashboards, schemas, alerts, and queries to match the `Workflows` prefix; event suffixes, payloads, and versions are unchanged. Replace Blueprint imports with `WorkflowsResource`. Before deploying an existing Blueprint stack, either pass its recorded resource name explicitly or plan the detach-and-create migration to the new default. Workflows request-tag families and billing classification are unchanged.
+
+  Other user-facing package copy now uses the Workflows product name. No upgrade action is required for consumers that do not match telemetry event names or use the Blueprint package.
+
+  **Docs impact:** Rename the product throughout the public documentation, move the docs section to `/docs/workflows/*` with permanent redirects from every `/docs/editorial-workflows/*` path, and document the telemetry-prefix, `WorkflowsResource`, and Blueprint resource-name migrations in the telemetry reference, Blueprint guide, and release notes.
+
+### Patch Changes
+
+- Updated dependencies [210ca63]
+- Updated dependencies [a3a8dc0]
+- Updated dependencies [a3a8dc0]
+- Updated dependencies [a3a8dc0]
+- Updated dependencies [90207dc]
+- Updated dependencies [b0b1550]
+  - @sanity/workflow-engine@0.30.0
+
 ## 0.29.0
 
 ### Patch Changes

package/README.md

@@ -183,7 +183,7 @@ Invoke as `sanity-workflows <command>` (or `sanity workflows <command>` once the
 ## Telemetry
 
 The CLI collects usage telemetry through Sanity's standard pipeline: a
-per-command trace (`Editorial Workflows CLI Command Executed` — the command id, the
+per-command trace (`Workflows CLI Command Executed` — the command id, the
 names of declared flags used, never their values, and a success flag) plus
 the engine's adoption events from the operations it drives. Consent is the
 account-wide status managed by `npx sanity telemetry enable|disable|status`;

package/dist/commands/workflows/definition/diff.js

@@ -6,7 +6,7 @@ import { resolveContext } from "../../../lib/context.js";
 import { fetchDeployedDefinition, selectDefinitions, validateOrFail, } from "../../../lib/definitions.js";
 import { diffReport } from "../../../lib/diff.js";
 import { deploymentFlags } from "../../../lib/flags.js";
-import { deploymentToTarget } from "../../../lib/select-deployment.js";
+import { acknowledgeDeployment, deploymentToTarget } from "../../../lib/select-deployment.js";
 export default class DefinitionDiff extends WorkflowCommand {
     static description = 'Diff an in-code definition against the deployed version (latest by default).';
     static examples = [
@@ -24,7 +24,7 @@ export default class DefinitionDiff extends WorkflowCommand {
         const { args, flags } = await this.parse(DefinitionDiff);
         const { deployment, client } = await resolveContext(flags);
         const def = selectDefinitionToDiff(deployment.definitions, args.name);
-        const target = deploymentToTarget(deployment);
+        const target = deploymentToTarget(acknowledgeDeployment(deployment, [def]));
         const spinner = ora(`Diffing ${args.name} against deployed…`).start();
         let deployed;
         try {

package/dist/commands/workflows/deploy.d.ts

@@ -1,4 +1,4 @@
-import { type DeployDefinitionResult, type WorkflowConfig, type WorkflowDefinition, type WorkflowDeployment } from '@sanity/workflow-engine';
+import { type AcknowledgedWorkflowDeployment, type DeployDefinitionResult, type WorkflowConfig, type WorkflowDefinition, type WorkflowDeployment } from '@sanity/workflow-engine';
 import { WorkflowCommand } from '../../lib/base-command.ts';
 import { type DeploymentSelectionOptions } from '../../lib/select-deployment.ts';
 /** A deployment paired with the definitions selected + validated for it. */
@@ -6,6 +6,9 @@ interface DeployBatch {
     deployment: WorkflowDeployment;
     defs: WorkflowDefinition[];
 }
+interface AcknowledgedDeployBatch extends DeployBatch {
+    deployment: AcknowledgedWorkflowDeployment;
+}
 /** A deployment whose deploy/diff threw, kept for the closing summary. */
 interface DeployFailure {
     deployment: Pick<WorkflowDeployment, 'name' | 'tag'>;
@@ -41,7 +44,7 @@ export declare function validateModeFlags(check: boolean, dryRun: boolean): void
 export declare function resolveBatches(config: WorkflowConfig, { only, selection }: {
     only: string | undefined;
     selection: DeploymentSelectionOptions;
-}): Promise<DeployBatch[]>;
+}): Promise<AcknowledgedDeployBatch[]>;
 /**
  * Select and validate every deployment's definitions up front. Validation runs
  * before any network write ({@link validateOrFail} exits on a bad definition),
@@ -51,7 +54,7 @@ export declare function resolveBatches(config: WorkflowConfig, { only, selection
  * multi-deployment run the failure names its deployment — it exits before any
  * banner could attribute it.
  */
-export declare function buildBatches(deployments: WorkflowDeployment[], only: string | undefined): DeployBatch[];
+export declare function buildBatches(deployments: WorkflowDeployment[], only: string | undefined): AcknowledgedDeployBatch[];
 /**
  * Run `processBatch` over each batch, continuing past a failure so one bad
  * deployment can't strand the rest — deployments are independent, and deploys
@@ -62,10 +65,10 @@ export declare function buildBatches(deployments: WorkflowDeployment[], only: st
  * An auth rejection also rethrows regardless of batch count: a dead token is
  * never batch-local, so continuing would just repeat the same failure.
  */
-export declare function reconcileBatches({ batches, log, processBatch, }: {
-    batches: DeployBatch[];
+export declare function reconcileBatches<T extends DeployBatch>({ batches, log, processBatch, }: {
+    batches: T[];
     log: (line: string) => void;
-    processBatch: (batch: DeployBatch) => Promise<void>;
+    processBatch: (batch: T) => Promise<void>;
 }): Promise<DeployFailure[]>;
 /**
  * The closing summary for a multi-deployment run that had failures: the

package/dist/commands/workflows/deploy.js

@@ -1,6 +1,6 @@
 import { styleText } from 'node:util';
 import { Flags } from '@oclif/core';
-import { assertReaderModelAcknowledgement, computeDiffEntries, errorMessage, workflow, } from '@sanity/workflow-engine';
+import { computeDiffEntries, errorMessage, workflow, } from '@sanity/workflow-engine';
 import logSymbols from 'log-symbols';
 import ora from 'ora';
 import { WorkflowCommand } from "../../lib/base-command.js";
@@ -10,7 +10,7 @@ import { diffReport } from "../../lib/diff.js";
 import { fail, isAuthRejection } from "../../lib/fail.js";
 import { deploymentFlags } from "../../lib/flags.js";
 import { loadWorkflowConfig } from "../../lib/load-config.js";
-import { deploymentLabel, deploymentToTarget, selectDeployments, } from "../../lib/select-deployment.js";
+import { acknowledgeDeployment, deploymentLabel, deploymentToTarget, selectDeployments, } from "../../lib/select-deployment.js";
 import { shareDefinitionsAfterDeploy } from "../../lib/share-definitions.js";
 import { cliTelemetry } from "../../lib/telemetry.js";
 import { groupBanner, resourceLabel } from "../../lib/ui.js";
@@ -160,11 +160,10 @@ export async function resolveBatches(config, { only, selection }) {
 }
 export function buildBatches(deployments, only) {
     return deployments.map((deployment) => {
-        assertReaderModelAcknowledgement(deployment.expectedMinReaderModel, `Deployment ${deployment.name}`);
         const context = deployments.length > 1 ? `${deploymentLabel(deployment)} — ` : '';
         const defs = selectDefinitions(deployment.definitions, { only, context });
         validateOrFail(defs, context);
-        return { deployment, defs };
+        return { deployment: acknowledgeDeployment(deployment, defs), defs };
     });
 }
 export async function reconcileBatches({ batches, log, processBatch, }) {

package/dist/lib/context.d.ts

@@ -16,13 +16,8 @@ export interface InstanceContext {
      *  `currentStage`; nuke's instance mode reads the terminal state. */
     instance: WorkflowInstance;
 }
-/**
- * The resolution a deployment-scoped command shares (`start`, `definition
- * delete`, `definition diff`): discover the config, pick the deployment for
- * `--deployment` or `--tag` (or the sole one), assert that deployment's
- * reader-floor acknowledgement, and build an authenticated client for its
- * resource. Instance-id commands resolve elsewhere and do not gate here.
- */
+/** Resolve the selected deployment. Deploy, definition-diff, and blueprint provision compare
+ *  its acknowledgement with submitted definitions; selection alone must not assert a floor. */
 export declare function resolveContext(flags: {
     deployment?: string | undefined;
     tag?: string | undefined;

package/dist/lib/context.js

@@ -1,4 +1,4 @@
-import { assertReadableModel, assertReaderModelAcknowledgement, resourceGdr, } from '@sanity/workflow-engine';
+import { assertReadableModel, resourceGdr, } from '@sanity/workflow-engine';
 import { clientFor, resolveTokenOrFail } from "./client.js";
 import { fail } from "./fail.js";
 import { loadWorkflowConfig } from "./load-config.js";
@@ -7,7 +7,6 @@ import { resourceLabel } from "./ui.js";
 export async function resolveContext(flags) {
     const config = await loadWorkflowConfig();
     const deployment = await selectDeployment(config, { name: flags.deployment, tag: flags.tag });
-    assertReaderModelAcknowledgement(deployment.expectedMinReaderModel, `Deployment ${deployment.name}`);
     return { deployment, client: clientFor(deployment.workflowResource, await resolveTokenOrFail()) };
 }
 function targetsFor(resources, token) {

package/dist/lib/env.d.ts

@@ -2,7 +2,6 @@ export declare const ENV: {
     readonly SANITY_AUTH_TOKEN: "SANITY_AUTH_TOKEN";
     readonly SANITY_API_HOST: "SANITY_API_HOST";
 };
-/** The explicit env token, or undefined when unset/blank. The single owner
- *  of "did the token come from the env?" — token resolution and the auth
- *  recovery hint must never disagree on it. */
+/** The explicit env token, or undefined when unset/blank. Token resolution
+ *  and the auth recovery hint must agree on this. */
 export declare function envAuthToken(): string | undefined;

package/dist/lib/fail.d.ts

@@ -1,17 +1,10 @@
 /**
- * Render a user-facing error and exit non-zero. Writes straight to
- * stderr — no oclif framing, no Node stack — so expected failures
- * (validation, missing input, conflicting flags) read clean.
+ * Render a user-facing error to stderr with no oclif framing or Node stack,
+ * and exit non-zero.
  *
- * Exits by THROWING oclif's `ExitError`, never `process.exit`: the error
- * rides the normal command lifecycle, so the `finally` hook still runs —
- * completing the command trace and flushing batched telemetry — before
- * oclif's handler exits 1 without printing anything further. A raw
- * `process.exit` here would silently drop the trace and every batched
- * event (including already-logged events from earlier in the command).
- *
- * For unexpected failures (network, engine throw) prefer letting the
- * error propagate so the stack is visible for debugging.
+ * Exits via oclif's `Errors.exit`, never `process.exit`: a raw `process.exit`
+ * would skip the command's `finally` hook, dropping the trace and any
+ * batched telemetry that hasn't flushed yet.
  */
 export declare function fail(headline: string, detail?: string): never;
 /**

package/dist/lib/select-deployment.d.ts

@@ -1,4 +1,4 @@
-import { type DeployTarget, type WorkflowConfig, type WorkflowDeployment } from '@sanity/workflow-engine';
+import { type AcknowledgedWorkflowDeployment, type DeployTarget, type WorkflowConfig, type WorkflowDefinition, type WorkflowDeployment } from '@sanity/workflow-engine';
 export type ChooseDeploymentName = (deployments: WorkflowDeployment[]) => Promise<string>;
 export interface DeploymentSelectionOptions {
     name: string | undefined;
@@ -33,11 +33,8 @@ export declare function selectDeployment(config: WorkflowConfig, { name, tag, or
     interactive?: boolean | undefined;
     chooseName?: ChooseDeploymentName | undefined;
 }): Promise<WorkflowDeployment>;
-/**
- * Every deployment carrying `tag`, failing when the tag matches none — the
- * shared resolution for the callers that accept a whole tag group (deploy's
- * tag-as-environment run, the read paths' resource narrowing).
- */
+/** Every deployment carrying `tag`, failing when the tag matches none — the
+ *  shared resolution for callers that accept a whole tag group. */
 export declare function deploymentsForTag(config: WorkflowConfig, tag: string): WorkflowDeployment[];
 /**
  * The deployments a `deploy` run acts on: every one with `--all-tags`, one
@@ -48,9 +45,11 @@ export declare function deploymentsForTag(config: WorkflowConfig, tag: string):
  * explicit opt-in — never a default.
  */
 export declare function selectDeployments(config: WorkflowConfig, { name, tag, allTags, interactive, chooseName }: DeploymentSelectionOptions): Promise<WorkflowDeployment[]>;
+/** The shared acknowledgement boundary for the CLI's definition-submission paths. */
+export declare function acknowledgeDeployment(deployment: WorkflowDeployment, definitions: readonly WorkflowDefinition[]): AcknowledgedWorkflowDeployment;
 /**
  * Project a deployment into the engine's {@link DeployTarget} — the shape the
  * deploy/diff verbs (`deployDefinitions`, `computeDiffEntries`, `diffEntry`)
  * consume — expanding its handle bindings into the alias map in the same step.
  */
-export declare function deploymentToTarget(deployment: WorkflowDeployment): DeployTarget;
+export declare function deploymentToTarget(deployment: AcknowledgedWorkflowDeployment): DeployTarget;

package/dist/lib/select-deployment.js

@@ -1,4 +1,4 @@
-import { assertReaderModelAcknowledgement, resourceAliasesToMap, } from '@sanity/workflow-engine';
+import { assertReaderModelAcknowledgement, requiredDefinitionReaderModel, resourceAliasesToMap, } from '@sanity/workflow-engine';
 import { fail } from "./fail.js";
 import { canPromptOnStderr, selectOnStderr } from "./prompt.js";
 export function deploymentLabel({ name, tag }) {
@@ -69,8 +69,15 @@ async function chooseDeploymentName(deployments) {
 function availableDeployments(config, deployments = config.deployments) {
     return `Available deployments: ${deployments.map(deploymentLabel).join(', ')}`;
 }
+export function acknowledgeDeployment(deployment, definitions) {
+    const expectedMinReaderModel = deployment.expectedMinReaderModel;
+    assertReaderModelAcknowledgement(expectedMinReaderModel, {
+        context: `Deployment ${deployment.name}`,
+        requiredMinReaderModel: requiredDefinitionReaderModel(definitions),
+    });
+    return { ...deployment, expectedMinReaderModel };
+}
 export function deploymentToTarget(deployment) {
-    assertReaderModelAcknowledgement(deployment.expectedMinReaderModel, `Deployment ${deployment.name}`);
     return {
         expectedMinReaderModel: deployment.expectedMinReaderModel,
         tag: deployment.tag,

package/dist/lib/share-definitions.d.ts

@@ -1,21 +1,5 @@
-/**
- * Definition sharing — donating deployed workflow definitions to Sanity is
- * CONTENT sharing, not telemetry: definitions carry customer-authored
- * strings (names, titles, GROQ filters) that the telemetry payload policy
- * bans, so the documents go to Sanity's first-party definition-feedback
- * endpoint — one POST per deploy invocation — and telemetry carries only a
- * content-free marker per shared definition plus a per-invocation decision
- * event.
- *
- * Consent model: opt-OUT. A deploy that creates new definition versions
- * donates by default. The choice is skipped by an explicit flag:
- * `--share-defs` (donate, no prompt) or `--no-share-defs` (don't). Without a
- * flag, the CLI shares. An interactive terminal gets a ONE-TIME notice
- * (persisted in the shared Sanity user config) before the first donation;
- * every later flagless deploy, and every unattended deploy, prints a concise
- * reminder. CI, `DO_NOT_TRACK`, and non-TTY execution do not change the
- * content-sharing default. Only `--no-share-defs` opts out.
- */
+/** Consent model: opt-OUT. Sharing new definition versions defaults on; only
+ *  --no-share-defs turns it off — CI, DO_NOT_TRACK, and non-TTY don't change that. */
 import { type DeployDefinitionResult, type DeployedDefinition, type WorkflowResource } from '@sanity/workflow-engine';
 import type { UserConfigStore } from './telemetry-setup.ts';
 import { type WorkflowDefinitionSharedData } from './telemetry.ts';
@@ -66,7 +50,7 @@ export declare const SHARE_REMINDER: string;
 /**
  * The content-free telemetry marker for one shared definition — projected
  * from the engine's own deploy-event derivation ({@link definitionDeployedData})
- * so `Editorial Workflows Definition Shared` and `Editorial Workflows Definition Deployed` can
+ * so `Workflows Definition Shared` and `Workflows Definition Deployed` can
  * never disagree about one definition's structure. Status is dropped:
  * only newly created versions are ever shared.
  */

package/dist/lib/share-definitions.js

@@ -8,13 +8,13 @@ import { cliTelemetry, WorkflowDefinitionShared, WorkflowDefinitionSharingDecide
 export const SHARE_ENDPOINT_URI = '/workflow/definition-feedback';
 const SHARE_TAG = 'definition.share';
 const SHARE_DECISION_KEY = 'workflowCliDefinitionSharing';
-export const SHARE_FIRST_RUN_NOTICE = `${styleText('bold', 'Sharing new workflow definitions with Sanity')} to improve Editorial Workflows.\n` +
+export const SHARE_FIRST_RUN_NOTICE = `${styleText('bold', 'Sharing new workflow definitions with Sanity')} to improve Workflows.\n` +
     'They are sent verbatim (structure, names, filters, effect configuration,\n' +
     'seeded values) with their deployment coordinates, and kept — never your\n' +
     'content documents, workflow instances, or Sanity auth token. This notice is\n' +
     `shown once on this machine; opt out of any run with ${styleText('cyan', '--no-share-defs')}.\n`;
 export const SHARE_REMINDER = `${styleText('bold', 'Definition sharing: ON (default)')}\n` +
-    'New workflow definition versions are being shared with Sanity to improve Editorial Workflows.\n' +
+    'New workflow definition versions are being shared with Sanity to improve Workflows.\n' +
     'Examples:\n' +
     `  ${styleText('dim', '$')} sanity-workflows deploy                 ${styleText('dim', '# share by default')}\n` +
     `  ${styleText('dim', '$')} sanity-workflows deploy ${styleText('cyan', '--share-defs')}    ${styleText('dim', '# share explicitly; hide this warning')}\n` +

package/dist/lib/telemetry-setup.d.ts

@@ -1,10 +1,5 @@
-/**
- * Once-per-invocation assembly of the CLI telemetry shell — the `prerun`
- * hook's whole job. Discovery is deliberately soft: telemetry must never
- * break (or exit) a command, so a missing/broken config, missing token,
- * or dataset-less config just leaves the invocation with telemetry off;
- * the command itself surfaces those problems where they matter.
- */
+/** Discovery is deliberately soft: telemetry must never break or exit a
+ *  command — a missing/broken config, token, or dataset just leaves it off. */
 import { processShellUserProperties, type TelemetryIntakeClient, type WorkflowResource } from '@sanity/workflow-engine';
 /** The get/set slice of the shared Sanity user config (cli-core's
  *  `getUserConfig`) the shell persists flags into — narrow so tests fake

package/dist/lib/telemetry.d.ts

@@ -1,32 +1,5 @@
-/**
- * The CLI's telemetry shell. A standalone oclif binary is its own app
- * shell — no host to ride — so this module owns the store, the standard
- * Sanity-intake consent/transport recipe (shared via
- * `@sanity/workflow-engine`'s `createTelemetryIntake`), and the one-time
- * disclosure. The `prerun` hook assembles it once per invocation and the
- * `finally` hook completes the command trace and flushes.
- *
- * Consent recipe: CI / `DO_NOT_TRACK` → denied; not logged in → no store
- * (undetermined, nothing sent); otherwise the account-level status the
- * intake recipe fetches. Consent is managed account-wide by
- * `sanity telemetry enable|disable|status` — the CLI inherits it and
- * ships no consent UX of its own.
- *
- * Provided-implementation caveat: a `telemetry` logger on the workflow
- * config replaces this shell wholesale — the built-in store is never
- * constructed and none of its policy (consent, environment suppression,
- * transport) applies; every event flows to the provided logger
- * unconditionally. Gates live in the store, not at emission sites.
- *
- * Payload policy: no customer strings, ever. The command trace carries
- * the command id, the NAMES of declared flags used, and a success flag —
- * never flag values, arguments, or error text. `Editorial Workflows
- * Definition Shared` is a content-free marker (hash + structural counts); the shared
- * document itself rides the first-party feedback endpoint, never
- * telemetry (see `share-definitions.ts`). `Editorial Workflows Definition
- * Sharing Decided` records the per-invocation sharing decision (default /
- * opt-in / opt-out and whether anything was donated) — also content-free.
- */
+/** Payload policy: no customer strings, ever — flag NAMES only (never values,
+ *  arguments, or error text); shared-definition events are content-free markers. */
 import { type DefinedTelemetryTrace, type TelemetryStore } from '@sanity/telemetry';
 import { type TelemetryIntakeClient, type WorkflowDefinitionDeployedData, type WorkflowTelemetryLogger } from '@sanity/workflow-engine';
 export interface WorkflowCliCommandData {

package/dist/lib/telemetry.js

@@ -1,17 +1,17 @@
 import { createBatchedStore, createSessionId, defineEvent, defineTrace, } from '@sanity/telemetry';
 import { createTelemetryIntake, isTelemetryEnvDenied, noopTelemetry, } from '@sanity/workflow-engine';
 export const WorkflowCliCommandExecuted = defineTrace({
-    name: 'Editorial Workflows CLI Command Executed',
+    name: 'Workflows CLI Command Executed',
     version: 1,
     description: 'A workflow CLI command was executed — payload is the command id, the names of declared flags used (never their values), and a success flag',
 });
 export const WorkflowDefinitionShared = defineEvent({
-    name: 'Editorial Workflows Definition Shared',
+    name: 'Workflows Definition Shared',
     version: 1,
-    description: 'A newly created workflow definition version was donated to Sanity. Content-free marker: the content hash plus the same structural counts Editorial Workflows Definition Deployed carries — the document itself goes to the first-party definition-feedback endpoint, never through telemetry.',
+    description: 'A newly created workflow definition version was donated to Sanity. Content-free marker: the content hash plus the same structural counts Workflows Definition Deployed carries — the document itself goes to the first-party definition-feedback endpoint, never through telemetry.',
 });
 export const WorkflowDefinitionSharingDecided = defineEvent({
-    name: 'Editorial Workflows Definition Sharing Decided',
+    name: 'Workflows Definition Sharing Decided',
     version: 2,
     description: 'One per deploy invocation that created new definition versions: whether donation followed the default or an explicit flag, whether anything reached the endpoint, and how many versions were eligible. Content-free — measures the true opt-out rate without ever carrying the document.',
 });

package/oclif.manifest.json

@@ -948,5 +948,5 @@
       ]
     }
   },
-  "version": "0.29.0"
+  "version": "0.30.0"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sanity/workflow-cli",
-  "version": "0.29.0",
+  "version": "0.30.0",
   "description": "Command-line tool for deploying, inspecting, and administering Sanity workflow definitions and instances.",
   "keywords": [
     "cli",
@@ -62,12 +62,12 @@
     "@types/node": "^24.12.4",
     "oclif": "^4.23.16",
     "vitest": "^4.1.8",
-    "@sanity/workflow-engine": "0.29.0",
-    "@sanity/workflow-engine-test": "0.29.0",
-    "@sanity/workflow-examples": "0.10.8"
+    "@sanity/workflow-engine": "0.30.0",
+    "@sanity/workflow-engine-test": "0.30.0",
+    "@sanity/workflow-examples": "0.11.0"
   },
   "peerDependencies": {
-    "@sanity/workflow-engine": "0.29.0"
+    "@sanity/workflow-engine": "0.30.0"
   },
   "oclif": {
     "bin": "sanity-workflows",
@@ -84,7 +84,7 @@
     "topicSeparator": " ",
     "topics": {
       "workflows": {
-        "description": "Deploy, inspect, and administer Editorial Workflows definitions and instances",
+        "description": "Deploy, inspect, and administer Workflows definitions and instances",
         "subtopics": {
           "definition": {
             "description": "Read and manage workflow definitions"