@cosmicdrift/kumiko-bundled-features 0.386.0 → 0.387.0

package/dist/user-data-rights-defaults/hooks/user.userdata-hook.js

@@ -5,25 +5,25 @@ import { USER_ANONYMIZED_DISPLAY_NAME, USER_ANONYMIZED_EMAIL_DOMAIN, USER_ANONYM
 // projection rebuild replays the events, so the anonymization survives it.
 // A direct write would be wiped on rebuild — the Art.17 hole this fixes.
 const crud = createEventStoreExecutor(userTable, userEntity, { entityName: "user" });
-// userData-Hook fuer user-entity (S2.H1).
+// The user-data hook for the user entity.
 //
-// Export-Hook liefert Profil-Daten ohne security-sensitive Felder
-// (passwordHash, roles, status — DSGVO Art. 20 ist Datenportabilitaet
-// fuer das was der User selbst zur Verfuegung gestellt hat, nicht
-// Lifecycle-Metadata oder Authorization-State).
+// The export hook returns profile data without security-sensitive fields
+// (passwordHash, roles, status — GDPR Art. 20 covers portability of data
+// the user provided themselves, not lifecycle metadata or authorization
+// state).
 //
-// Delete-Hook anonymisiert PII + setzt status=deleted. Der eigentliche
-// softDelete-Flag wird ueber drizzle's deletedAt-Column gesetzt; die
-// Row bleibt fuer Audit-Trail erhalten (alle FK-Refs auf user.id
-// bleiben gueltig). DSGVO-konform via PII-Anonymisierung.
+// The delete hook anonymizes PII and sets status=deleted. The actual
+// softDelete flag is set through Drizzle's deletedAt column; the row remains
+// for the audit trail (all foreign-key references to user.id remain valid).
+// This complies with GDPR through PII anonymization.
 //
 // Strategy:
-//   "delete":    softDelete + email/displayName/passwordHash leeren,
-//                status=deleted (Login geblockt)
-//   "anonymize": email/displayName auf Pseudonym, Row bleibt active
-//                — fuer Cases wo User-Row als FK noch relevant ist
-//                aber PII raus muss (z.B. anonymize mit blockDelete-
-//                Frist auf einer FK-target-Entity)
+//   "delete":    softDelete + clear email/displayName/passwordHash,
+//                status=deleted (login blocked)
+//   "anonymize": replace email/displayName with pseudonyms; the row remains
+//                active when the user row is still needed as a foreign-key
+//                target but PII must be removed (for example, anonymization
+//                with a blockDelete deadline on a foreign-key target entity)
 export const userExportHook = async (ctx) => {
     const row = await ctx.db.fetchOne(userTable, { id: ctx.userId });
     if (!row)
@@ -42,11 +42,11 @@ export const userExportHook = async (ctx) => {
     };
 };
 export const userDeleteHook = async (ctx, strategy) => {
-    // Idempotent: zweiter Call findet die Row schon anonymized + skipt
-    // implicit (UPDATE mit gleichen Werten). Memory feedback_event_store_
-    // tenant_consistency: ctx.tenantId muss in der user-table-Zeile
-    // korrelieren — user.id ist tenant-agnostic (User kann in mehreren
-    // Tenants Member sein), kein tenantId-Filter noetig.
+    // Idempotent: a second call finds the row already anonymized and skips
+    // implicitly (UPDATE with the same values). Event-store tenant
+    // consistency requires ctx.tenantId to correlate with the row in
+    // the user table — user.id is tenant-agnostic (a user can be a member in
+    // multiple tenants), so no tenantId filter is needed.
     // System actor + skipOptimisticLock: the forget pipeline has no read
     // version and writes privileged identity columns ("system" is privileged).
     // crud.update extracts the raw connection from ctx.db via tenantDbRunner
@@ -55,12 +55,13 @@ export const userDeleteHook = async (ctx, strategy) => {
     // TenantDb's own tenant-scoping narrowing never applies to executor writes.
     const systemUser = createSystemUser(ctx.tenantId);
     if (strategy === "delete") {
-        // PII raus + status=deleted (Login geblockt) via Event → Rebuild spielt den
-        // Forget mit. KEIN softDelete: user ist systemStream (eine tenant-agnostische
-        // Row), der Forget laeuft pro Tenant — wuerde isDeleted gesetzt, faende der
-        // loadById (isDeleted:false) die Row beim zweiten Tenant nicht mehr
-        // (not_found). status=Deleted blockt Login; die Row bleibt findbar +
-        // idempotent ueber mehrere Tenant-Durchlaeufe (wie der alte raw UPDATE).
+        // Remove PII and set status=deleted via an event, so a rebuild replays
+        // the forget operation. Do NOT use softDelete: user is systemStream (a
+        // tenant-agnostic row), and forgetting runs once per tenant. Setting
+        // isDeleted would cause loadById (isDeleted:false) to miss the row for
+        // the second tenant (not_found). status=Deleted blocks login; the row
+        // remains findable and idempotent across tenant passes, as with the old
+        // raw UPDATE.
         await crud.update({
             id: ctx.userId,
             changes: {
@@ -75,11 +76,11 @@ export const userDeleteHook = async (ctx, strategy) => {
         }, systemUser, ctx.db, { skipOptimisticLock: true, writePurpose: WritePurposes.erasure });
     }
     else {
-        // anonymize: PII raus, aber Row bleibt active (damit FK-References
-        // weiter aufloesbar sind). Account ist effektiv weiter nutzbar
-        // wenn der User sich neu authentifiziert — pragmatisch akzeptabel
-        // weil "anonymize" auf user-entity ein seltener Edge-Case ist
-        // (typisch hard-delete fuer User).
+        // Anonymize PII, but keep the row active so foreign-key references
+        // remain resolvable. The account can still be used if the user
+        // authenticates again — pragmatically acceptable because "anonymize"
+        // on the user entity is a rare edge case (hard deletion is typical for
+        // users).
         await crud.update({
             id: ctx.userId,
             changes: {

package/dist/user-profile/handlers/change-email.write.js

@@ -5,22 +5,22 @@ import { AuthErrors } from "../../auth-email-password/index.js";
 import { decryptStoredPii, verifyPassword } from "../../shared/index.js";
 import { UserErrors, UserHandlers, UserQueries } from "../../user/index.js";
 import { UserProfileErrors } from "../web/constants.js";
-// Gleiche Failure-Shape wie auth-email-password (anti-enumeration):
-// dessen errors.ts ist nicht Teil des Feature-Barrels, der Reason-Code
-// + i18nKey sind aber stabile Public-API.
+// Same failure shape as auth-email-password (anti-enumeration):
+// its errors.ts is not part of the feature barrel, but the reason code
+// and i18nKey are stable public API.
 // @wrapper-known error-helper
 function invalidCredentials() {
     return writeFailure(new UnprocessableError(AuthErrors.invalidCredentials, {
         i18nKey: "auth.errors.invalidCredentials",
     }));
 }
-// Change-email — authenticated, self-only. Der User bestätigt mit seinem
-// aktuellen Passwort (Re-Auth wie change-password); die neue Adresse wird
-// via ctx.writeAs(system) gegen den user-update-Handler geschrieben, weil
-// `email` field-level privileged ist und bei Self-Updates sonst silent
-// gestrippt würde. emailVerified flippt auf false — die App triggert
-// anschließend den Verification-Flow (request-email-verification ist
-// public; der ProfileScreen ruft ihn nach Erfolg auf).
+// Change-email — authenticated, self-only. The user confirms with their
+// current password (re-authentication as with change-password); the new
+// address is written through the user-update handler via ctx.writeAs(system)
+// because `email` is field-level privileged and would otherwise be silently
+// stripped during self-updates. emailVerified is set to false — the app then
+// triggers the verification flow (request-email-verification is public; the
+// ProfileScreen calls it after success).
 export const changeEmailWrite = defineWriteHandler({
     name: "change-email",
     schema: z.object({
@@ -67,9 +67,9 @@ export const changeEmailWrite = defineWriteHandler({
                 i18nKey: "user.errors.emailAlreadyExists",
             }));
         }
-        // user ist systemStream (#497): der Event-Stream liegt deterministisch
-        // auf SYSTEM_TENANT_ID. Pre-#497-Streams brauchen einmalig
-        // backfillUserStreamTenants (#762).
+        // user is systemStream: the event stream is deterministically located
+        // on SYSTEM_TENANT_ID. Older streams require a one-time
+        // backfillUserStreamTenants.
         const writer = createSystemUser(SYSTEM_TENANT_ID);
         const writeRes = await ctx.writeAs(writer, UserHandlers.update, {
             id: me.id,

package/dist/user-profile/index.js

@@ -1,5 +1,5 @@
-// Bewusst OHNE i18n-Export: das Server-Barrel muss von Server-Samples
-// ohne jsx-tsconfig kompilierbar bleiben (i18n zieht kumiko-renderer →
-// .tsx). Translations kommen via ./web (userProfileClient).
+// Deliberately no i18n export: the server barrel must remain compilable by server samples
+// without a JSX tsconfig (i18n pulls in kumiko-renderer → .tsx). Translations are provided
+// through ./web (userProfileClient).
 export { createUserProfileFeature } from "./feature.js";
 export { USER_PROFILE_FEATURE, UserDataRightsHandlers, UserProfileErrors, UserProfileHandlers, UserProfileQueries, } from "./web/constants.js";

package/dist/user-profile/web/client-plugin.js

@@ -3,7 +3,7 @@ import { CHANGE_EMAIL_SECTION_EXTENSION_NAME, CHANGE_PASSWORD_SECTION_EXTENSION_
 import { defaultTranslations } from "./i18n.js";
 import { ChangeEmailSection, ChangePasswordSection } from "./profile-screen.js";
 // Supplies the ChangeEmail/ChangePassword extension components for the
-// declarative `profile` projectionDetail screen (fw#2312, ../feature.ts,
+// declarative `profile` projectionDetail screen (../feature.ts,
 // registered there server-side) plus the default translations. Apps add it
 // via createKumikoApp({ clientFeatures: [userProfileClient()] }) and place
 // the screen (id "profile") via r.nav — the screen itself has no r.nav of

package/dist/user-profile/web/constants.js

@@ -2,7 +2,7 @@
 // import them; runtime code (handlers/feature) may pull client files anyway.
 export const USER_PROFILE_FEATURE = "user-profile";
 export const PROFILE_SCREEN_ID = "profile";
-// EditExtensionSection `__component` markers (fw#2312) — change-password and
+// EditExtensionSection `__component` markers — change-password and
 // change-email stay React components (re-auth flows a declarative action
 // can't express); deletion moved to declarative fields/actions on the screen
 // itself (feature.ts), same split as user-data-rights' privacy-center.

package/dist/user-profile/web/profile-screen.js

@@ -1,6 +1,6 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
 // Change-password and change-email sections for the declarative `profile`
-// projectionDetail screen (fw#2312, ../feature.ts). Both keep re-auth flows
+// projectionDetail screen (../feature.ts). Both keep re-auth flows
 // a declarative action can't express, so they stay React `EditExtensionSection`
 // components; account deletion moved to declarative fields/actions on the
 // screen itself — same split as user-data-rights' privacy-center

package/dist/workflow-runner/aggregate-id.d.ts

@@ -6,6 +6,6 @@
  * race on `expectedVersion` and have the loser fail the unique constraint
  * instead of silently double-running. It does NOT dedup sequential
  * re-triggers of the same key — those land as version 2, 3, ... on the same
- * stream and each starts its own run; that's out of scope for #2478.
+ * stream and each starts its own run; that's out of scope.
  */
 export declare function workflowRunAggregateId(workflowName: string, key: string): string;

package/dist/workflow-runner/aggregate-id.js

@@ -10,7 +10,7 @@ const WORKFLOW_RUN_NAMESPACE = "1f8a6c3e-7d2b-4a91-9e3f-5c8b2a41d6f0";
  * race on `expectedVersion` and have the loser fail the unique constraint
  * instead of silently double-running. It does NOT dedup sequential
  * re-triggers of the same key — those land as version 2, 3, ... on the same
- * stream and each starts its own run; that's out of scope for #2478.
+ * stream and each starts its own run; that's out of scope.
  */
 // @wrapper-known uuid-domain
 export function workflowRunAggregateId(workflowName, key) {

package/dist/workflow-runner/event-subscriber.js

@@ -1,6 +1,5 @@
 // event-subscriber — wakes up pending waitForEvent suspensions when their
-// awaited domain event arrives (framework#2513 Phase 3b, D4 in
-// workflow-resume-loop.md).
+// awaited domain event arrives (in workflow-resume-loop.md).
 //
 // registerEventTrigger (event-trigger.ts) calls registerEventWakeup for
 // every workflow it registers, building ONE MultiStreamProjection PER
@@ -17,12 +16,12 @@
 // already in hand, has no such hazard — same reasoning event-trigger.ts
 // already applies to the run-start MSP.
 //
-// This subscriber never resumes a run itself (D3, workflow-resume-loop.md):
+// This subscriber never resumes a run itself (in workflow-resume-loop.md):
 // the MultiStreamApplyContext it runs in has no callFeature/runStepList
 // access, only unsafeAppendEvent/loadAggregate. It writes triggerEventType
 // + triggerEventRef + wakeAt=now() onto the matching pending row(s); the
-// existing resume-due-runs job (Phase 2) picks the row up on its next
-// cron tick — the one resume path stays exactly the one Phase 2 built.
+// existing resume-due-runs job picks the row up on its next
+// cron tick — the resume path remains unchanged.
 import { selectMany, updateMany } from "@cosmicdrift/kumiko-framework/db";
 import { evaluateEventMatch } from "@cosmicdrift/kumiko-framework/engine";
 import { createFallbackLogger } from "@cosmicdrift/kumiko-framework/logging";

package/dist/workflow-runner/event-trigger.js

@@ -8,7 +8,7 @@
 // wiring uses the unbound pool), so `workflow.run-started` and the rest of
 // the pipeline are not atomic. A throw from startAndRunWorkflow is recorded
 // as `workflow.run-failed` and swallowed, so the dispatcher moves on.
-import { buildPipelineSteps, createSystemUser, describeWorkflowStepError, getStep, SYSTEM_TENANT_ID, unwrapWorkflowStepError, WORKFLOW_AGGREGATE_TYPE, WORKFLOW_RUN_FAILED_TYPE, WorkflowStepError, } from "@cosmicdrift/kumiko-framework/engine";
+import { buildPipelineSteps, createSystemUser, describeWorkflowStepError, getStep, SYSTEM_TENANT_ID, unwrapWorkflowStepError, WORKFLOW_AGGREGATE_TYPE, WORKFLOW_RUN_FAILED_TYPE, WorkflowStepError, walkStepInstances, } from "@cosmicdrift/kumiko-framework/engine";
 import { createFallbackLogger } from "@cosmicdrift/kumiko-framework/logging";
 import { workflowRunAggregateId } from "./aggregate-id.js";
 import { registerEventWakeup } from "./event-subscriber.js";
@@ -26,19 +26,6 @@ const STEP_KINDS_NEEDING_HANDLER_CONTEXT = new Set([
     "unsafeProjectionUpsert",
     "unsafeProjectionDelete",
 ]);
-function* walkStepInstances(steps) {
-    for (const step of steps) {
-        yield step;
-        const { args } = step;
-        if (typeof args !== "object" || args === null)
-            continue;
-        for (const path of getStep(step.kind)?.subPaths ?? []) {
-            const nested = path in args ? Reflect.get(args, path) : undefined;
-            if (Array.isArray(nested))
-                yield* walkStepInstances(nested);
-        }
-    }
-}
 export function assertEventTriggerStepsSupported(workflow) {
     let steps;
     try {
@@ -54,7 +41,7 @@ export function assertEventTriggerStepsSupported(workflow) {
         throw new Error(`Workflow "${workflow.name}" pipeline closure threw at registration: ${String(error)}. ` +
             "Build the step list without reading event payload fields; read them inside step resolvers.", { cause: error });
     }
-    for (const step of walkStepInstances(steps)) {
+    for (const step of walkStepInstances(steps, `workflow "${workflow.name}" eventTrigger`)) {
         if (getStep(step.kind) === undefined) {
             throw new Error(`Workflow "${workflow.name}" uses unknown step kind "${step.kind}"`);
         }
@@ -66,12 +53,12 @@ export function assertEventTriggerStepsSupported(workflow) {
 }
 export function registerEventTrigger(r, workflow) {
     // Populate the workflow-registry unconditionally, before the event-trigger
-    // guard below — resume-run (framework#2513 Phase 2) looks workflows up by
+    // guard below — resume-run looks workflows up by
     // name regardless of trigger kind, and a cron-triggered workflow that never
     // reaches the MSP branch still needs to be resumable.
     registerWorkflow(workflow);
     // Independent of trigger.kind — a cron-triggered workflow can still have
-    // waitForEvent steps in its pipeline (framework#2513 Phase 3b, D4).
+    // waitForEvent steps in its pipeline.
     registerEventWakeup(r, workflow);
     // skip: cron-triggered workflows have no domain event to project off — they
     // need a scheduler, not an MSP, so there is nothing to register here.

package/dist/workflow-runner/feature.js

@@ -9,8 +9,8 @@
 // `workflowRunnerFeature` documents that dependency and reserves the
 // picker/manifest slot.
 //
-// It also registers the resume loop (framework#2513 Phase 2 + 3b):
-//   - the workflow_run_pending MSP (Phase 1) materialises suspended
+// It also registers the resume loop:
+//   - the workflow_run_pending MSP materialises suspended
 //     wait/waitForEvent/retry steps into a pending-set table
 //   - the `resume-due-runs` cron job (perTenant) scans that table for
 //     `wakeAt < now()` rows and dispatches `resume-run` per row — the job

package/dist/workflow-runner/handlers/resume-run.write.js

@@ -1,10 +1,10 @@
 // resume-run — wakes one suspended workflow step. Dispatched by the
-// resume-due-runs job (framework#2513 Phase 2), never called directly by a
+// resume-due-runs job, never called directly by a
 // user — r.systemScope() + access: { roles: [SYSTEM_ROLE] } enforce that.
 //
 // The job does nothing but SELECT + dispatch; all resume logic lives here,
 // adapted from samples/recipes/workflow-engine/src/resume-loop.ts:
-//   1. Q7 fingerprint check FIRST — before claiming, before any pipeline
+//   1. Fingerprint check FIRST — before claiming, before any pipeline
 //      work. A changed workflow definition fails loud (WORKFLOW_RUN_FAILED,
 //      reason "workflow_definition_changed"), never a silent skip.
 //   2. Claim via a savepoint-scoped WORKFLOW_RESUMED append (ctx.tryAppendEvent,
@@ -23,8 +23,8 @@
 // shows up here in its shredded form, and an unloadable one (archived
 // stream) fails the run. The pending row's own
 // triggerEventType/triggerEventRef columns are a DIFFERENT thing: for a
-// waitForEvent suspension they point at the AWAITED event the Phase 3b
-// event-subscriber matched (NULL until then, and NULL forever on a
+// waitForEvent suspension they point at the AWAITED event the event-subscriber
+// matched (NULL until then, and NULL forever on a
 // timeout-without-a-match). That event's payload becomes the resumed
 // pipeline's result for the skipped waitForEvent step itself (see
 // resultKey on steps/wait-for-event.ts) — pre-seeded into stepsAcc below so

package/dist/workflow-runner/pending-projection.js

@@ -4,13 +4,12 @@
 // Insert (upsert, for idempotent at-least-once redelivery) on every
 // suspension: wait, waitForEvent, retry. Delete on WORKFLOW_RESUMED or a
 // terminal run outcome (completed/failed) — a run only ever has one row
-// pending at a time (D1: a later suspension always targets a fresh
-// stepIndex, since the prior one was resumed away first), so deleting by
+// pending at a time (a later suspension always targets a fresh stepIndex,
+// since the prior one was resumed away first), so deleting by
 // (tenantId, runId) alone is exact.
 //
-// No resume logic here — framework#2513 Phase 2 owns the job that reads
-// this table and dispatches the actual resume. This projection only writes
-// the rows.
+// No resume logic here — the job that reads this table and dispatches the
+// actual resume is separate. This projection only writes the rows.
 import { deleteMany, fetchOne, upsertOnConflict } from "@cosmicdrift/kumiko-framework/db";
 import { WORKFLOW_RESUMED_TYPE, WORKFLOW_RETRY_SCHEDULED_TYPE, WORKFLOW_RUN_COMPLETED_TYPE, WORKFLOW_RUN_FAILED_TYPE, WORKFLOW_WAITING_FOR_EVENT_TYPE, WORKFLOW_WAITING_TYPE, } from "@cosmicdrift/kumiko-framework/engine";
 import { workflowRunPendingTable } from "./tables.js";
@@ -24,8 +23,8 @@ async function upsertPending(tx, row) {
         return;
     await upsertOnConflict(tx, workflowRunPendingTable, {
         ...row,
-        // Phase 3's event-subscriber writes these when the awaited event
-        // arrives — Phase 1 never touches them, insert or update.
+        // The event-subscriber writes these when the awaited event
+        // arrives — they are never touched here, on insert or update.
         triggerEventType: null,
         triggerEventRef: null,
         triggerPayload: null,

package/dist/workflow-runner/runner.js

@@ -2,12 +2,12 @@
 // pipeline until first suspension or completion, and writing run-completed.
 //
 // wait / retry / waitForEvent suspensions are all resumable — the
-// resume-due-runs job + resume-run handler (framework#2513 Phase 2) wake
-// wait/retry via a plain wakeAt timeout; waitForEvent additionally gets
-// woken early by the event-subscriber (Phase 3b, event-subscriber.ts) when
-// its awaited event arrives, and by the same wakeAt timeout otherwise
-// (D1's `wakeAt ?? timeoutAt`). startAndRunWorkflow returns a silent
-// "suspended" outcome for all three instead of throwing.
+// resume-due-runs job + resume-run handler wake wait/retry via a plain
+// wakeAt timeout; waitForEvent additionally gets woken early by the
+// event-subscriber (event-subscriber.ts) when its awaited event arrives,
+// and by the same wakeAt timeout otherwise (D1's `wakeAt ?? timeoutAt`).
+// startAndRunWorkflow returns a silent "suspended" outcome for all three
+// instead of throwing.
 import { buildPipelineSteps, computeDefinitionFingerprint, runStepList, WORKFLOW_AGGREGATE_TYPE, WORKFLOW_RUN_COMPLETED_TYPE, WORKFLOW_RUN_STARTED_TYPE, } from "@cosmicdrift/kumiko-framework/engine";
 // Suspensions the resume loop knows how to wake — every Tier-3 step that
 // can return SUSPEND_SENTINEL. Kept as an explicit allowlist (not "every

package/dist/workflow-runner/tables.js

@@ -1,11 +1,11 @@
 import { defineUnmanagedTable, index, instant, integer, jsonb, table as pgTable, primaryKey, text, uuid, } from "@cosmicdrift/kumiko-framework/db";
 // workflow_run_pending — one row per currently-suspended workflow step.
-// Read-side of the resume loop (framework#2513 Phase 1): the wait /
+// Read-side of the resume loop: the wait /
 // waitForEvent / retry steps already write their suspension onto the
 // workflow-run event stream, but scanning kumiko_events for due runs
 // doesn't scale (see samples/recipes/workflow-engine/postgres-resume-loop.ts,
 // which does exactly that). This table is kept in sync by
-// pending-projection.ts's MultiStreamProjection so Phase 2's resume job can
+// pending-projection.ts's MultiStreamProjection so the resume job can
 // do an indexed `wakeAt < now()` scan instead.
 //
 // **Unmanaged table** — same reasoning as delivery/tables.ts'
@@ -19,7 +19,7 @@ import { defineUnmanagedTable, index, instant, integer, jsonb, table as pgTable,
 // key only, see aggregate-id.ts), so two tenants triggering the same
 // workflow with the same idempotencyKey get the SAME run_id. Without
 // tenant_id in the key, a same-stepIndex suspension from tenant B would
-// upsert onto tenant A's row and silently steal it (framework#2513).
+// upsert onto tenant A's row and silently steal it.
 export const workflowRunPendingTable = pgTable("workflow_run_pending", {
     runId: uuid("run_id").notNull(),
     tenantId: uuid("tenant_id").notNull(),
@@ -31,14 +31,14 @@ export const workflowRunPendingTable = pgTable("workflow_run_pending", {
     // which step suspended.
     wakeAt: instant("wake_at").notNull(),
     retryAttempt: integer("retry_attempt"),
-    // Q7 snapshot fingerprint — Phase 2 compares this against the current
+    // Snapshot fingerprint — compares this against the current
     // workflow definition's fingerprint before resuming.
     definitionFingerprint: text("definition_fingerprint"),
     // Set only for waitForEvent suspensions; NULL for wait/retry.
     waitEventType: text("wait_event_type"),
     matchExpr: jsonb("match_expr"),
-    // Written by the Phase 3 event-subscriber when the awaited event
-    // arrives — always NULL in Phase 1/2. The row points at the awaited event
+    // Written by the event subscriber when the awaited event
+    // arrives — always NULL initially. The row points at the awaited event
     // ({ eventId, aggregateId, version }); resume-run re-reads it from the
     // event store, so erasing the event also covers the workflow.
     triggerEventType: text("trigger_event_type"),

package/dist/workflow-runner/workflow-registry.js

@@ -1,6 +1,6 @@
 // workflow-registry — process-local lookup from workflow name to its
 // WorkflowDefinition. registerEventTrigger populates it at feature-
-// registration time; resume-run (Phase 2) is the only reader — it has
+// registration time; resume-run is the only reader — it has
 // nothing but a workflow name on the pending row and needs the live
 // definition to rebuild the pipeline + recompute the Q7 fingerprint.
 //

package/package.json

@@ -1,8 +1,8 @@
 {
   "name": "@cosmicdrift/kumiko-bundled-features",
-  "version": "0.386.0",
+  "version": "0.387.0",
   "description": "Built-in features — tenant, user, auth, delivery. The stuff you'd rewrite anyway, already typed.",
-  "license": "BUSL-1.1",
+  "license": "MIT",
   "author": "Marc Frost <marc@cosmicdriftgamestudio.com>",
   "repository": {
     "type": "git",
@@ -544,9 +544,9 @@
     }
   },
   "dependencies": {
-    "@cosmicdrift/kumiko-framework": "0.386.0",
-    "@cosmicdrift/kumiko-renderer": "0.386.0",
-    "@cosmicdrift/kumiko-types": "0.386.0",
+    "@cosmicdrift/kumiko-framework": "0.387.0",
+    "@cosmicdrift/kumiko-renderer": "0.387.0",
+    "@cosmicdrift/kumiko-types": "0.387.0",
     "@mollie/api-client": "^4.5.0",
     "@node-rs/argon2": "^2.0.2",
     "@tiptap/core": "3.31.3",
@@ -1116,15 +1116,15 @@
   ],
   "devDependencies": {
     "@testing-library/user-event": "^14.6.1",
-    "@cosmicdrift/kumiko-locale-de": "0.386.0",
-    "@cosmicdrift/kumiko-locale-es": "0.386.0",
-    "@cosmicdrift/kumiko-renderer-mail-html": "0.386.0",
+    "@cosmicdrift/kumiko-locale-de": "0.387.0",
+    "@cosmicdrift/kumiko-locale-es": "0.387.0",
+    "@cosmicdrift/kumiko-renderer-mail-html": "0.387.0",
     "jsqr": "^1.4.0",
     "unpdf": "^1.8.1",
-    "@cosmicdrift/kumiko-testing": "0.386.0"
+    "@cosmicdrift/kumiko-testing": "0.387.0"
   },
   "peerDependencies": {
-    "@cosmicdrift/kumiko-testing": "0.386.0"
+    "@cosmicdrift/kumiko-testing": "0.387.0"
   },
   "peerDependenciesMeta": {
     "@cosmicdrift/kumiko-testing": {