@vellumai/assistant 0.10.12 → 0.11.0-staging.1

package/src/workspace/migrations/registry.ts

@@ -131,6 +131,8 @@ import { speechModeToProviderMigration } from "./130-speech-mode-to-provider.js"
 import { dropWebFetchModeMigration } from "./131-drop-web-fetch-mode.js";
 import { webSearchModeToProviderMigration } from "./132-web-search-mode-to-provider.js";
 import { collapseProviderConnectionsMigration } from "./133-collapse-provider-connections.js";
+import { imageGenerationModeToProviderMigration } from "./134-image-generation-mode-to-provider.js";
+import { copySubstrateTunablesMigration } from "./135-copy-substrate-tunables.js";
 import { migrateToWorkspaceVolumeMigration } from "./migrate-to-workspace-volume.js";
 import type { WorkspaceMigration } from "./types.js";
 
@@ -277,4 +279,6 @@ export const WORKSPACE_MIGRATIONS: WorkspaceMigration[] = [
   dropWebFetchModeMigration,
   webSearchModeToProviderMigration,
   collapseProviderConnectionsMigration,
+  imageGenerationModeToProviderMigration,
+  copySubstrateTunablesMigration,
 ];

package/src/__tests__/memory-retrieval-budget.test.ts

@@ -1,49 +0,0 @@
-import { describe, expect, test } from "bun:test";
-
-import { computeRecallBudget } from "../plugins/defaults/memory/retrieval-budget.js";
-
-describe("memory retrieval budget", () => {
-  test("clamps to maxInjectTokens when headroom is large", () => {
-    const budget = computeRecallBudget({
-      estimatedPromptTokens: 20_000,
-      maxInputTokens: 180_000,
-      targetHeadroomTokens: 8_000,
-      minInjectTokens: 1_200,
-      maxInjectTokens: 10_000,
-    });
-    expect(budget).toBe(10_000);
-  });
-
-  test("clamps to minInjectTokens when headroom is tight", () => {
-    const budget = computeRecallBudget({
-      estimatedPromptTokens: 172_000,
-      maxInputTokens: 180_000,
-      targetHeadroomTokens: 8_000,
-      minInjectTokens: 1_200,
-      maxInjectTokens: 10_000,
-    });
-    expect(budget).toBe(1_200);
-  });
-
-  test("returns computed value when between min and max", () => {
-    const budget = computeRecallBudget({
-      estimatedPromptTokens: 165_000,
-      maxInputTokens: 180_000,
-      targetHeadroomTokens: 8_000,
-      minInjectTokens: 1_200,
-      maxInjectTokens: 10_000,
-    });
-    expect(budget).toBe(7_000);
-  });
-
-  test("normalizes invalid min/max ordering safely", () => {
-    const budget = computeRecallBudget({
-      estimatedPromptTokens: 150_000,
-      maxInputTokens: 180_000,
-      targetHeadroomTokens: 8_000,
-      minInjectTokens: 12_000,
-      maxInjectTokens: 1_200,
-    });
-    expect(budget).toBe(12_000);
-  });
-});

package/src/__tests__/secret-patterns.test.ts

@@ -1,27 +0,0 @@
-import { describe, expect, test } from "bun:test";
-
-import { PREFIX_PATTERNS } from "../security/secret-patterns.js";
-
-function matchingLabels(text: string): string[] {
-  return PREFIX_PATTERNS.filter((p) => p.regex.test(text)).map((p) => p.label);
-}
-
-describe("Vercel AI Gateway API Key", () => {
-  test("matches a vck_ key as exactly one pattern", () => {
-    expect(matchingLabels(`vck_${"a".repeat(32)}`)).toEqual([
-      "Vercel AI Gateway API Key",
-    ]);
-  });
-
-  test("does not match a short vck_ string", () => {
-    expect(matchingLabels("vck_abc")).toEqual([]);
-  });
-});
-
-describe("OpenRouter API Key", () => {
-  test("matches an sk-or-v1- key", () => {
-    expect(matchingLabels(`sk-or-v1-${"a".repeat(40)}`)).toEqual([
-      "OpenRouter API Key",
-    ]);
-  });
-});

package/src/config/__tests__/proc-to-skills.test.ts

@@ -1,21 +0,0 @@
-import { describe, expect, test } from "bun:test";
-
-import { isProcToSkillsActive } from "../memory-v3-gate.js";
-import type { AssistantConfig } from "../schema.js";
-
-describe("isProcToSkillsActive (v3-live)", () => {
-  const v3Live = { memory: { v3: { live: true } } } as AssistantConfig;
-  const v3NotLive = { memory: { v3: { live: false } } } as AssistantConfig;
-
-  test("false when v3 is not live", () => {
-    expect(isProcToSkillsActive(v3NotLive)).toBe(false);
-  });
-
-  test("false by default (no v3 config)", () => {
-    expect(isProcToSkillsActive({} as AssistantConfig)).toBe(false);
-  });
-
-  test("true when v3 is live", () => {
-    expect(isProcToSkillsActive(v3Live)).toBe(true);
-  });
-});

package/src/config/memory-tier.test.ts

@@ -1,44 +0,0 @@
-import { describe, expect, test } from "bun:test";
-
-import { memoryTier } from "./memory-tier.js";
-import type { AssistantConfig } from "./schema.js";
-
-describe("memoryTier", () => {
-  test("off when memory is explicitly disabled", () => {
-    const config = { memory: { enabled: false } } as AssistantConfig;
-    expect(memoryTier(config)).toBe("off");
-  });
-
-  test("off wins even when v3 is live (OFF over v3 precedence)", () => {
-    const config = {
-      memory: { enabled: false, v3: { live: true } },
-    } as AssistantConfig;
-    expect(memoryTier(config)).toBe("off");
-  });
-
-  test("v3 when memory-v3 is live", () => {
-    const config = { memory: { v3: { live: true } } } as AssistantConfig;
-    expect(memoryTier(config)).toBe("v3");
-  });
-
-  test("v2 when v2 is enabled and v3 is not live", () => {
-    const config = {
-      memory: { v2: { enabled: true }, v3: { live: false } },
-    } as AssistantConfig;
-    expect(memoryTier(config)).toBe("v2");
-  });
-
-  test("v3 wins over v2 when both are truthy (v3 over v2 precedence)", () => {
-    const config = {
-      memory: { v2: { enabled: true }, v3: { live: true } },
-    } as AssistantConfig;
-    expect(memoryTier(config)).toBe("v3");
-  });
-
-  test("v1 when memory is on but neither v2 nor v3 is selected", () => {
-    const config = {
-      memory: { enabled: true, v2: { enabled: false }, v3: { live: false } },
-    } as AssistantConfig;
-    expect(memoryTier(config)).toBe("v1");
-  });
-});

package/src/daemon/message-types/acp.ts

@@ -1,20 +0,0 @@
-// ACP (Agent Client Protocol) session lifecycle and communication types.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { AcpSessionCompletedEvent } from "../../api/events/acp-session-completed.js";
-import type { AcpSessionErrorEvent } from "../../api/events/acp-session-error.js";
-import type { AcpSessionSpawnedEvent } from "../../api/events/acp-session-spawned.js";
-import type { AcpSessionUpdateEvent } from "../../api/events/acp-session-update.js";
-import type { AcpSessionUsageEvent } from "../../api/events/acp-session-usage.js";
-
-// --- Domain-level union alias (consumed by message-protocol.ts) ---
-
-export type _AcpServerMessages =
-  | AcpSessionSpawnedEvent
-  | AcpSessionUpdateEvent
-  | AcpSessionCompletedEvent
-  | AcpSessionErrorEvent
-  | AcpSessionUsageEvent;

package/src/daemon/message-types/apps.ts

@@ -1,11 +0,0 @@
-// App management, publishing, and sharing.
-//
-// Server→client events that are live hub broadcasts are single-sourced from
-// their canonical `api/events` wire schemas; this file only composes them into
-// the domain union consumed by `message-protocol.ts`. App management — listing,
-// bundling, sharing, publishing, history/diff/restore, signing — is served by
-// the HTTP app-management routes, not by client messages.
-
-import type { AppFilesChangedEvent } from "../../api/events/app-files-changed.js";
-
-export type _AppsServerMessages = AppFilesChangedEvent;

package/src/daemon/message-types/background-tools.ts

@@ -1,14 +0,0 @@
-// Background bash/host_bash command lifecycle types.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { BackgroundToolCompletedEvent } from "../../api/events/background-tool-completed.js";
-import type { BackgroundToolStartedEvent } from "../../api/events/background-tool-started.js";
-
-// --- Domain-level union alias (consumed by message-protocol.ts) ---
-
-export type _BackgroundToolsServerMessages =
-  | BackgroundToolStartedEvent
-  | BackgroundToolCompletedEvent;

package/src/daemon/message-types/bookmarks.ts

@@ -1,13 +0,0 @@
-// Bookmark events. Surfaced over SSE so a `BookmarkStore` instance in any
-// connected client can stay in sync when another window mutates the list.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { BookmarkCreatedEvent } from "../../api/events/bookmark-created.js";
-import type { BookmarkDeletedEvent } from "../../api/events/bookmark-deleted.js";
-
-export type _BookmarksServerMessages =
-  | BookmarkCreatedEvent
-  | BookmarkDeletedEvent;

package/src/daemon/message-types/contacts.ts

@@ -1,13 +0,0 @@
-// Contact events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Contact list/get/delete are served by the HTTP
-// `contacts` routes, not by a client message.
-
-import type { ContactRequestEvent } from "../../api/events/contact-request.js";
-import type { ContactsChangedEvent } from "../../api/events/contacts-changed.js";
-
-export type _ContactsServerMessages =
-  | ContactsChangedEvent
-  | ContactRequestEvent;

package/src/daemon/message-types/document-comments.ts

@@ -1,14 +0,0 @@
-// Document comment event types (Server → Client).
-
-import type { DocumentCommentCreatedEvent } from "../../api/events/document-comment-created.js";
-import type { DocumentCommentDeletedEvent } from "../../api/events/document-comment-deleted.js";
-import type { DocumentCommentReopenedEvent } from "../../api/events/document-comment-reopened.js";
-import type { DocumentCommentResolvedEvent } from "../../api/events/document-comment-resolved.js";
-
-// --- Domain-level union alias (consumed by the barrel file) ---
-
-export type _DocumentCommentsServerMessages =
-  | DocumentCommentCreatedEvent
-  | DocumentCommentResolvedEvent
-  | DocumentCommentReopenedEvent
-  | DocumentCommentDeletedEvent;

package/src/daemon/message-types/documents.ts

@@ -1,13 +0,0 @@
-// Document editor events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Document save/load/list are served by the document
-// tools and HTTP document routes, not by client messages.
-
-import type { DocumentEditorShowEvent } from "../../api/events/document-editor-show.js";
-import type { DocumentEditorUpdateEvent } from "../../api/events/document-editor-update.js";
-
-export type _DocumentsServerMessages =
-  | DocumentEditorShowEvent
-  | DocumentEditorUpdateEvent;

package/src/daemon/message-types/home.ts

@@ -1,15 +0,0 @@
-/**
- * Home — server → client push messages for the macOS Home page.
- *
- * These messages are fire-and-forget notifications; the client reacts
- * by refetching the authoritative state from the HTTP route
- * (`GET /v1/home/state`). Payloads stay deliberately tiny — they carry
- * just enough metadata to invalidate a cache and trigger a refetch.
- */
-
-import type { HomeFeedUpdatedEvent } from "../../api/events/home-feed-updated.js";
-import type { RelationshipStateUpdatedEvent } from "../../api/events/relationship-state-updated.js";
-
-export type _HomeServerMessages =
-  | RelationshipStateUpdatedEvent
-  | HomeFeedUpdatedEvent;

package/src/daemon/message-types/host-bash.ts

@@ -1,12 +0,0 @@
-// Host bash proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostBashCancelEvent } from "../../api/events/host-bash.js";
-import type { HostBashRequestEvent } from "../../api/events/host-bash.js";
-
-export type _HostBashServerMessages =
-  | HostBashRequestEvent
-  | HostBashCancelEvent;

package/src/daemon/message-types/host-cu.ts

@@ -1,10 +0,0 @@
-// Host computer-use proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostCuCancelEvent } from "../../api/events/host-cu.js";
-import type { HostCuRequestEvent } from "../../api/events/host-cu.js";
-
-export type _HostCuServerMessages = HostCuRequestEvent | HostCuCancelEvent;

package/src/daemon/message-types/host-file.ts

@@ -1,12 +0,0 @@
-// Host file proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostFileCancelEvent } from "../../api/events/host-file.js";
-import type { HostFileRequestEvent } from "../../api/events/host-file.js";
-
-export type _HostFileServerMessages =
-  | HostFileRequestEvent
-  | HostFileCancelEvent;

package/src/daemon/message-types/host-transfer.ts

@@ -1,12 +0,0 @@
-// Host transfer proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostTransferCancelEvent } from "../../api/events/host-transfer.js";
-import type { HostTransferRequestEvent } from "../../api/events/host-transfer.js";
-
-export type _HostTransferServerMessages =
-  | HostTransferRequestEvent
-  | HostTransferCancelEvent;

package/src/daemon/message-types/integrations.ts

@@ -1,90 +0,0 @@
-// External service integrations: Slack, Telegram, Vercel, ingress, platform.
-//
-// Server→client events that are live hub broadcasts are single-sourced from
-// their canonical `api/events` wire schemas; this file only composes them into
-// the domain union consumed by `message-protocol.ts`. Config get/set flows
-// (Slack webhook, ingress, platform, Vercel, Telegram, integration listing and
-// connect) are served by the HTTP settings routes, not by client messages.
-
-import type { NavigateSettingsEvent } from "../../api/events/navigate-settings.js";
-import type { OAuthConnectResultEvent } from "../../api/events/oauth-connect-result.js";
-import type { OpenPanelEvent } from "../../api/events/open-panel.js";
-import type { OpenUrlEvent } from "../../api/events/open-url.js";
-import type { PlatformDisconnectedEvent } from "../../api/events/platform-disconnected.js";
-import type { ShowPlatformLoginEvent } from "../../api/events/show-platform-login.js";
-import type { ChannelId } from "../../channels/types.js";
-
-// === Client → Server ===
-
-export interface ChannelVerificationSessionRequest {
-  type: "channel_verification_session";
-  action:
-    | "create_session"
-    | "status"
-    | "cancel_session"
-    | "revoke"
-    | "resend_session";
-  channel?: ChannelId; // Defaults to 'telegram'
-  conversationId?: string;
-  rebind?: boolean; // When true, allows creating a challenge even if a binding already exists
-  /** E.164 phone number for phone, Telegram handle/chat-id. Used by outbound actions. */
-  destination?: string;
-  /** Origin conversation ID so completion/failure pointers can route back. */
-  originConversationId?: string;
-  /** Distinguishes guardian vs trusted-contact verification flows in the unified create endpoint. */
-  purpose?: "guardian" | "trusted_contact";
-  /** Contact-channel ID for the absorbed contact-channel verify flow. */
-  contactChannelId?: string;
-}
-
-// === Server → Client ===
-
-export interface ChannelVerificationSessionResponse {
-  type: "channel_verification_session_response";
-  success: boolean;
-  secret?: string;
-  instruction?: string;
-  /** Present when action is 'status'. */
-  bound?: boolean;
-  guardianExternalUserId?: string;
-  /** The channel this status pertains to (e.g. "telegram", "phone"). Present when action is 'status'. */
-  channel?: ChannelId;
-  /** The assistant ID scoped to this status. Present when action is 'status'. */
-  assistantId?: string;
-  /** The delivery chat ID for the guardian (e.g. Telegram chat ID). Present when action is 'status' and bound is true. */
-  guardianDeliveryChatId?: string;
-  /** Optional channel username/handle for the bound guardian (for UI display). */
-  guardianUsername?: string;
-  /** Optional display name for the bound guardian (for UI display). */
-  guardianDisplayName?: string;
-  /** Whether a pending verification challenge exists for this (assistantId, channel). Used by relay setup to detect active voice verification sessions. */
-  hasPendingChallenge?: boolean;
-  error?: string;
-  /** Human-readable error detail (e.g. for already_bound failures). */
-  message?: string;
-  /** Conversation ID for outbound verification flows. */
-  verificationSessionId?: string;
-  /** Epoch ms when the verification session expires. */
-  expiresAt?: number;
-  /** Epoch ms after which a resend is allowed. */
-  nextResendAt?: number;
-  /** Number of sends for this session. */
-  sendCount?: number;
-  /** Telegram deep-link URL for bootstrap (M3 placeholder). */
-  telegramBootstrapUrl?: string;
-  /** True when the outbound session is still in pending_bootstrap state (Telegram handle flow). Prevents the client from clearing the bootstrap URL during status polling. */
-  pendingBootstrap?: boolean;
-}
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _IntegrationsClientMessages = ChannelVerificationSessionRequest;
-
-export type _IntegrationsServerMessages =
-  | ChannelVerificationSessionResponse
-  | OAuthConnectResultEvent
-  | OpenUrlEvent
-  | OpenPanelEvent
-  | NavigateSettingsEvent
-  | ShowPlatformLoginEvent
-  | PlatformDisconnectedEvent;

package/src/daemon/message-types/memory.ts

@@ -1,10 +0,0 @@
-// Memory recall and status events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Memory has no client messages.
-
-import type { MemoryRecalledEvent } from "../../api/events/memory-recalled.js";
-import type { MemoryStatusEvent } from "../../api/events/memory-status.js";
-
-export type _MemoryServerMessages = MemoryRecalledEvent | MemoryStatusEvent;

package/src/daemon/message-types/schedules.ts

@@ -1,14 +0,0 @@
-// Heartbeat events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Schedule / heartbeat / filing management (list,
-// config, run-now, checklist) is served by the HTTP heartbeat and filing
-// routes, not by client messages.
-
-import type { HeartbeatAlertEvent } from "../../api/events/heartbeat-alert.js";
-import type { HeartbeatConversationCreatedEvent } from "../../api/events/heartbeat-conversation-created.js";
-
-export type _SchedulesServerMessages =
-  | HeartbeatAlertEvent
-  | HeartbeatConversationCreatedEvent;

package/src/daemon/message-types/settings.ts

@@ -1,17 +0,0 @@
-// Client settings: daemon-pushed configuration updates to connected clients.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Settings mutations (voice config, avatar generation)
-// are served by the HTTP settings/avatar routes, not by client messages.
-
-import type { AvatarUpdatedEvent } from "../../api/events/avatar-updated.js";
-import type { ClientSettingsUpdateEvent } from "../../api/events/client-settings-update.js";
-import type { ConfigChangedEvent } from "../../api/events/config-changed.js";
-import type { SoundsConfigUpdatedEvent } from "../../api/events/sounds-config-updated.js";
-
-export type _SettingsServerMessages =
-  | ClientSettingsUpdateEvent
-  | AvatarUpdatedEvent
-  | ConfigChangedEvent
-  | SoundsConfigUpdatedEvent;

package/src/daemon/message-types/subagents.ts

@@ -1,63 +0,0 @@
-// Subagent lifecycle and communication types.
-//
-// The `subagent_spawned` and `subagent_status_changed` server events are
-// single-sourced from their canonical `api/events` wire schemas; this file
-// composes them into the domain union consumed by `message-protocol.ts`.
-
-import type { SubagentSpawnedEvent } from "../../api/events/subagent-spawned.js";
-import type { SubagentStatusChangedEvent } from "../../api/events/subagent-status-changed.js";
-import type { UsageStats } from "./shared.js";
-
-// === Server → Client ===
-
-export interface SubagentDetailResponse {
-  type: "subagent_detail_response";
-  subagentId: string;
-  objective?: string;
-  usage?: UsageStats;
-  events: Array<{
-    type: string;
-    content: string;
-    toolName?: string;
-    isError?: boolean;
-    messageId?: string;
-  }>;
-}
-
-// === Client → Server ===
-
-export interface SubagentAbortRequest {
-  type: "subagent_abort";
-  subagentId: string;
-}
-
-export interface SubagentStatusRequest {
-  type: "subagent_status";
-  /** If omitted, returns all subagents for the conversation. */
-  subagentId?: string;
-}
-
-export interface SubagentMessageRequest {
-  type: "subagent_message";
-  subagentId: string;
-  content: string;
-}
-
-export interface SubagentDetailRequest {
-  type: "subagent_detail_request";
-  subagentId: string;
-  conversationId: string;
-}
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _SubagentsClientMessages =
-  | SubagentAbortRequest
-  | SubagentStatusRequest
-  | SubagentMessageRequest
-  | SubagentDetailRequest;
-
-export type _SubagentsServerMessages =
-  | SubagentSpawnedEvent
-  | SubagentStatusChangedEvent
-  | SubagentDetailResponse;

package/src/daemon/message-types/upgrades.ts

@@ -1,14 +0,0 @@
-// Service-group upgrade lifecycle events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { ServiceGroupUpdateCompleteEvent } from "../../api/events/service-group-update-complete.js";
-import type { ServiceGroupUpdateProgressEvent } from "../../api/events/service-group-update-progress.js";
-import type { ServiceGroupUpdateStartingEvent } from "../../api/events/service-group-update-starting.js";
-
-export type _UpgradesServerMessages =
-  | ServiceGroupUpdateStartingEvent
-  | ServiceGroupUpdateProgressEvent
-  | ServiceGroupUpdateCompleteEvent;

package/src/daemon/message-types/workflows.ts

@@ -1,25 +0,0 @@
-// Workflow orchestration run lifecycle events.
-//
-// Emitted by the `WorkflowRunManager` (run-manager.ts) as a workflow run
-// progresses and completes. These are server → client push events only — the
-// run is launched via the workflow tool / scheduler / routes (later PRs), not
-// via a client message in this union.
-//
-// The events are single-sourced from their canonical `api/events` wire
-// schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { WorkflowCompletedEvent } from "../../api/events/workflow-completed.js";
-import type { WorkflowLeafFinishedEvent } from "../../api/events/workflow-leaf-finished.js";
-import type { WorkflowLeafStartedEvent } from "../../api/events/workflow-leaf-started.js";
-import type { WorkflowProgressEvent } from "../../api/events/workflow-progress.js";
-import type { WorkflowStartedEvent } from "../../api/events/workflow-started.js";
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _WorkflowsServerMessages =
-  | WorkflowProgressEvent
-  | WorkflowCompletedEvent
-  | WorkflowStartedEvent
-  | WorkflowLeafStartedEvent
-  | WorkflowLeafFinishedEvent;