@pattern-stack/codegen 0.14.1 → 0.15.0

package/CHANGELOG.md

@@ -4,6 +4,94 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [0.15.0] — 2026-06-02
+
+Package-mode consumer **events** — the seam that lets a project consuming the
+runtime from the package (`runtime: package`, ADR-037) declare its own
+`events/*.yaml`, get a typed `TypedEventBus`, and publish typed domain events.
+Completes the package-mode story alongside 0.14.2's bridge fixes. Vendored mode
+is byte-stable; everything here is additive.
+
+### Added
+
+- **`EventsModuleOptions.typedBus?: Type<unknown>`** — binds a consumer-supplied
+  `TypedEventBus` class to `TYPED_EVENT_BUS` (via `forRoot`). Omitted ⇒ falls
+  back to the bundled `./generated/bus` (which IS the consumer's generated file
+  in a vendored tree), so existing consumers and tests are unaffected. Nest
+  constructs the supplied class with this module's `EVENT_BUS` +
+  `EVENTS_MULTI_TENANT` providers (string-valued tokens match across the package
+  boundary).
+
+### Fixed
+
+- **Event codegen is package-mode-aware.** Previously `entity new --all` in
+  package mode wrote the five generated event files
+  (`types/schemas/registry/bus/index.ts`) into a stray
+  `src/shared/subsystems/events/generated/` tree whose `../event-bus.protocol` /
+  `../events.tokens` / `../events-errors` imports don't exist in package mode —
+  the tree didn't typecheck and was orphaned (the bundled empty `TypedEventBus`
+  won at runtime). Now in package mode the files land in the consumer's
+  `src/generated/events/`, those three runtime imports resolve through the
+  published `@pattern-stack/codegen/runtime/subsystems/events/index` barrel, and
+  the subsystem barrel threads the generated `TypedEventBus` into
+  `EventsModule.forRoot({ typedBus })`. A package-mode consumer's typed
+  `publish<'…'>()` now resolves against THEIR event union and stamps the right
+  `pool` / `direction`.
+- **Scope-entity-type is package-mode-aware** — relocated to
+  `src/generated/scope-entity-type.ts` (a self-contained zod-only union) instead
+  of the stray vendored `jobs/generated/` path.
+- **Package-mode bridge trigger validation now runs.** Because the consumer's
+  event registry now exists at a real path (`src/generated/events/registry.ts`),
+  the bridge registry generator validates `@JobHandler.triggers` event types
+  against it (the 0.14.2 "known gap"). `subsystem install events` drops an
+  empty-set `src/generated/events/` stub so the barrel's `./events/bus` import
+  never dangles before the next `entity new`.
+
+## [0.14.2] — 2026-06-02
+
+Package-mode bridge fixes — the two gaps that left the event→job bridge wired but
+inert when the runtime is consumed from the package (`runtime: package`, ADR-037)
+rather than vendored. Both are follow-ons to 0.14.1's package-mode subsystem
+support. Vendored mode is unchanged; these are additive.
+
+### Fixed
+
+- **Embedded worker now drains the reserved `events_*` bridge pools.** The
+  subsystem barrel emitted `JobWorkerModule.forRoot({ mode: 'embedded' })` with no
+  pool list, so the in-process worker polled only `interactive` + `batch` and
+  bridge wrappers sat pending forever (the BRIDGE-8 footgun, just past the boot
+  guard). When `bridge` is in `subsystems.install`, the embedded worker now
+  defaults to `allPools: true` (every lane in-process — exactly the knob
+  `BridgeModule`'s reserved-pool guard short-circuits on).
+- **A package-mode consumer's `@JobHandler.triggers` now bind.** Previously
+  `BridgeModule` hardwired the bundled `./generated/registry` placeholder (frozen
+  `{}` inside the package), and the registry generator skipped entirely in package
+  mode (it gated on a vendored `bridge.protocol.ts` that doesn't exist), so no
+  event ever routed to a job. The registry is now generated into the consumer's
+  `src/generated/bridge-registry.ts` (type imported from
+  `@pattern-stack/codegen/runtime/subsystems/bridge/index`, install gated on
+  `subsystems.install`) and threaded into `BridgeModule.forRoot({ registry })` by
+  the barrel. `subsystem install bridge` drops an empty-registry stub so the
+  import never dangles before the next `entity new`.
+
+### Added
+
+- **`BridgeModuleOptions.registry?: BridgeRegistry`** — lets the generated barrel
+  supply the consumer's scanned registry. Omitted ⇒ falls back to the bundled
+  `./generated/registry` (which IS the consumer's generated file in vendored
+  mode), so existing consumers and tests are unaffected.
+- **`jobs.worker_pools: string[]` and `jobs.all_pools: true`** config knobs on the
+  embedded worker. Precedence: explicit `worker_pools` (→ `pools: [...]`) >
+  `all_pools` (→ `allPools: true`) > bridge-installed default (`allPools: true`) >
+  the non-reserved default (unchanged).
+
+### Known gaps
+
+- Package-mode trigger-event **validation** against the events registry is skipped
+  (the event codegen generator is not yet mode-aware, so its registry isn't found
+  under the package-mode generated path). Triggers still generate and bind; only
+  the build-time "unknown event" check is inert. Tracked for a follow-on.
+
 ## [0.13.0] — 2026-05-31
 
 Track D round-2/3 — the integration codegen now emits the **full** integration

package/dist/runtime/subsystems/bridge/bridge.module.d.ts

@@ -1,5 +1,6 @@
 import { OnModuleInit, DynamicModule } from '@nestjs/common';
 import { JobWorkerModuleOptions } from '../jobs/job-worker.module.js';
+import { BridgeRegistry } from './bridge.protocol.js';
 import '@nestjs/core';
 import '../../types/drizzle.js';
 import 'drizzle-orm/node-postgres';
@@ -15,6 +16,7 @@ import '../events/generated/types.js';
 import '../jobs/job-run-service.protocol.js';
 import '../jobs/job-step-service.protocol.js';
 import '../jobs/job-worker.js';
+import './bridge-delivery.schema.js';
 
 /**
  * BridgeModule — `DynamicModule.forRoot({ backend, multiTenant })`
@@ -75,6 +77,26 @@ interface BridgeModuleOptions {
      * `null` always passes (cross-tenant work). Defaults to `false`.
      */
     multiTenant?: boolean;
+    /**
+     * The codegen-emitted `Record<EventTypeName, BridgeTriggerEntry[]>` that
+     * drives outbox-drain trigger lookup (BRIDGE-4) and the facade's Case B
+     * dedup (BRIDGE-7).
+     *
+     * **Package mode (ADR-037).** When the runtime is imported from
+     * `@pattern-stack/codegen` (not vendored), the bundled
+     * `./generated/registry` is a frozen empty placeholder (`{}`) — a
+     * consumer's `@JobHandler.triggers` are scanned into a registry that lives
+     * in THEIR `src/generated/bridge-registry.ts`, which the package can't
+     * import. The generated subsystem barrel therefore threads that registry in
+     * here: `BridgeModule.forRoot({ ..., registry: bridgeRegistry })`. Omitted
+     * (vendored mode / tests) ⇒ falls back to the bundled `./generated/registry`,
+     * which in vendored mode IS the consumer's freshly-generated file.
+     *
+     * Without this, package-mode consumers' triggers never bind and the bridge
+     * routes nothing (the "wrappers sit pending" footgun's silent twin —
+     * nothing is ever enqueued in the first place).
+     */
+    registry?: BridgeRegistry;
 }
 declare class BridgeModule implements OnModuleInit {
     private readonly workerOpts?;

package/dist/runtime/subsystems/bridge/bridge.module.js

@@ -3427,7 +3427,11 @@ var BridgeModule = class {
       providers: [
         { provide: BRIDGE_MODULE_OPTIONS, useValue: opts },
         { provide: BRIDGE_MULTI_TENANT, useValue: opts.multiTenant ?? false },
-        { provide: BRIDGE_REGISTRY, useValue: bridgeRegistry },
+        // Package mode threads the consumer's generated registry through
+        // `opts.registry`; vendored mode omits it and we fall back to the
+        // bundled `./generated/registry` (which IS the consumer's generated
+        // file in a vendored tree). See `BridgeModuleOptions.registry`.
+        { provide: BRIDGE_REGISTRY, useValue: opts.registry ?? bridgeRegistry },
         repoProvider,
         // Drain hook — always wired; `DrizzleEventBus` consumes it via
         // `@Optional()`, so non-bridge mounts simply see `undefined`.