@pattern-stack/codegen 0.10.0 → 0.10.1

package/CHANGELOG.md

@@ -4,6 +4,79 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [0.10.1] — 2026-05-28
+
+Dogfood fixes found wiring `@pattern-stack/codegen@0.10.0` into a second
+consumer (swe-brain): the type-check blockers that forced consumers to exclude
+the vendored subsystem tree from `tsc` are gone. A drizzle-only install now
+type-checks its full tree (`src/shared/subsystems/**` included) with no
+`ioredis`/`bullmq` peer deps.
+
+### Fixed
+
+- **`fix(subsystems)` — detection + barrel emission key on `<name>.module.ts`
+  (#4, #2).** Installing one subsystem can vendor *protocol stubs* of another
+  (e.g. events vendors `bridge/bridge.protocol.ts`); detection used to report
+  those stub-only dirs as `installed` and the barrel emitted a phantom
+  `BridgeModule` import for a module that was never installed (TS2307).
+  Detection now requires the module file; `subsystem list` reports `incomplete`
+  for stub-only dirs; the barrel skips them.
+- **`fix(events)` — drizzle backend type-checks against its paired schema
+  (#3).** `event-bus.drizzle-backend.ts` read a `tier` column the schema never
+  emitted and `tenant_id` columns only present under multi-tenancy. `tier` is
+  now always emitted; `tenant_id` access is gated behind `multiTenant`, so the
+  backend type-checks under any configuration.
+- **`fix(subsystems)` — installs no longer vendor unselected backends (#6).** A
+  `--backend drizzle` install previously vendored the Redis and BullMQ backend
+  sources too, dragging `ioredis`/`bullmq` (uninstalled optional peers) into the
+  consumer's type-check. The copy filter now prunes `*.redis-backend.ts` /
+  `*.bullmq-backend.ts` for non-matching installs; modules lazy-load the chosen
+  backend via a non-literal dynamic import; backend-specific classes are no
+  longer re-exported from the public barrels; `bullmq.config.ts` is kept on
+  every install (peer-dep-free) for its static token references; the BullMQ
+  backend is `noImplicitAny`-clean.
+- **`fix(barrel)` — empty-composer output emits the `DynamicModule` import.** A
+  generated `subsystems.ts` with no composer calls referenced `DynamicModule`
+  without importing it (latent since BULLMQ-1, surfaced by the stricter
+  detection above).
+
+### Added
+
+- **`feat(cli)` — `codegen subsystem remove` (#5, #7).** Real implementation:
+  deletes the vendored subsystem dir, regenerates the barrel, git-safety gated
+  with `--force`, and `--yes`/`-y` parity with `install`. Prints the manual
+  follow-ups it deliberately does *not* perform (config-block strip,
+  `forRoot` un-registration).
+- **`test(smoke)` — `run-smoke-subsystems.ts`.** Exercises an events + jobs +
+  bridge drizzle install with a full-tree `tsc` (no subsystem excludes) + a
+  programmatic NestJS boot that validates the bridge reserved-pool dependency
+  graph. Wired into `just test-all`.
+
+## [0.10.0] — 2026-05-27
+
+### Added
+
+- **`feat(cli)` — consumer skill distribution (ADR-035).** A curated
+  `consumer-skills/` set (a `codegen` router plus `entities`, `subsystems`,
+  `jobs`, `events`, `bridge`, `sync`) is vendored into a consumer's
+  `.claude/skills/` via a new `skills` noun (`codegen skills install` / `list`),
+  and by `codegen init` by default (`--no-skills` to opt out). Authored fresh
+  for a consumer audience; shipped in the npm `files` array.
+- **`feat(cli)` — `codegen update`.** Re-syncs the vendored runtime closure,
+  installed subsystems' runtime, and consumer skills to the installed package
+  version after a bump. Drift-aware, git-clean gated (`--force`), `--dry-run`;
+  never touches consumer-owned files (config, `app.module.ts`, barrels).
+- **`feat(parser)` — recursive YAML discovery.** Entity / relationship /
+  junction / event discovery routes through a single `findYamlFiles` helper;
+  domain-folder layouts (`entities/crm/account.yaml`) are first-class.
+
+### Changed
+
+- **Docs split.** `CONSUMER-SETUP.md` became a hub; the per-subsystem deep dives
+  moved to `docs/consumer/{events,bridge,sync,auth,openapi}.md` (progressive
+  disclosure), with jobs-API drift (`JobsModule` → `JobsDomainModule` +
+  `JobWorkerModule`, `JobHandlerBase`, `concurrency: { key }`) corrected.
+
 ## [0.9.0] — 2026-05-25
 
 Bundles four merged PRs (none carried a version bump): the BullMQ backend and

package/consumer-skills/events/typed-bus-and-outbox.md

@@ -65,7 +65,7 @@ New code should prefer `TypedEventBus`.
 
 ## The outbox table and drain loop
 
-`domain_events` is the outbox. Key columns: `id` (UUID, the idempotency key), `type`, `aggregate_id`, `aggregate_type`, `payload` (jsonb), `occurred_at`, `processed_at`, `status` (`pending | processed | failed`), `error`, `metadata`, and first-class `pool` / `direction` columns (populated from `metadata` at insert so the drain can filter by lane without unpacking JSON).
+`domain_events` is the outbox. Key columns: `id` (UUID, the idempotency key), `type`, `aggregate_id`, `aggregate_type`, `payload` (jsonb), `occurred_at`, `processed_at`, `status` (`pending | processed | failed`), `error`, `metadata`, and first-class `pool` / `direction` / `tier` columns (populated from `metadata` at insert so the drain can filter by lane without unpacking JSON). `tier` (`'domain'` | `'audit'`, default `'domain'`) is always emitted; the `domain_events_tier_routing_check` constraint enforces that `tier='audit'` rows have null `pool`/`direction`. `tenant_id` is the only conditional column — emitted only under `events.multi_tenant: true`.
 
 The drain loop (Drizzle backend):
 1. Claims a batch (default 50) of `pending` rows with `FOR UPDATE SKIP LOCKED`, optionally filtered by pool, ordered by `occurred_at ASC`. `SKIP LOCKED` lets multiple worker processes drain concurrently without double-dispatching.

package/consumer-skills/subsystems/SKILL.md

@@ -87,8 +87,42 @@ pools, and multi-tenancy are in `wiring-and-order.md`.
   must be registered after them.
 - **Multi-tenancy is a config flip + a `forRoot` flag + a migration** — never a
   runtime-only toggle. See `wiring-and-order.md`.
+- **`subsystem list` can report `incomplete`, and that's usually fine.**
+  Installing one subsystem may vendor *stub* files of another — e.g. installing
+  `events` drops `bridge/bridge.protocol.ts` + `bridge.tokens.ts` because the
+  events Drizzle backend imports them. That `bridge/` directory has the protocol
+  stubs but no `bridge.module.ts`, so `subsystem list` shows it `incomplete`. It
+  is **not** registered in the generated `subsystems.ts` barrel (the barrel only
+  emits a `forRoot()` for subsystems whose `<name>.module.ts` exists), so it
+  won't break your `tsc`. Run `subsystem install bridge` to promote it to
+  `installed` when you actually want the bridge.
 - **`--backend memory`** is for tests; the scaffolded default is `drizzle`
   (`local` for storage).
+- **Install vendors only the selected backend.** Alternate-backend source
+  files are pruned: a `--backend drizzle` events install does NOT vendor
+  `event-bus.redis-backend.ts`, and a drizzle/memory jobs install does NOT
+  vendor `job-orchestrator.bullmq-backend.ts`, `job-worker.bullmq-backend.ts`,
+  or `bullmq.config.ts`. The module files (`events.module.ts`,
+  `jobs-domain.module.ts`, `job-worker.module.ts`) lazy-load the chosen
+  backend via dynamic `import()` with a non-literal specifier, so the unused
+  backends never drag their peer deps (`ioredis`, `bullmq`) into your `tsc`
+  graph. `bullmq` and `ioredis` are declared as **optional peer
+  dependencies** — install them ONLY if you actually select that backend.
+  **Drizzle installs no longer drag `bullmq` / `ioredis` into your consumer
+  peer-deps**; if your `package.json` carries them only as workarounds for
+  earlier 0.10.x scaffolds, you can drop them.
+- **Bundler caveat.** The dynamic-import specifier is captured in a variable
+  (e.g. `const spec = './event-bus.redis-backend'; await import(spec)`) on
+  purpose — that's what makes `tsc` treat it as `any` and skip resolving the
+  pruned file. A bundler (webpack / esbuild / rollup) won't static-analyse a
+  non-literal specifier either, so it won't include the dynamically-imported
+  file in its output bundle. In practice this is fine: when the file isn't
+  vendored (drizzle install) there's nothing to bundle; when it IS vendored
+  (redis / bullmq install) consumers typically run Node/Bun directly against
+  the source tree. If you bundle a redis/bullmq build for deployment, ensure
+  your bundler is configured to include the vendored
+  `<subsystems-root>/<name>/` tree (e.g. mark it as external + ship alongside)
+  or pin the dynamic-import path to a literal in your own wrapper.
 
 ## Do not
 
@@ -103,3 +137,25 @@ pools, and multi-tenancy are in `wiring-and-order.md`.
   runtime source, not the tenancy-gated Drizzle schema files. If a schema shape
   changed across versions, re-run `subsystem install <name> --force
   --force-config`.
+
+## Removing a subsystem
+
+`codegen subsystem remove <name>` deletes the vendored
+`<subsystems-root>/<name>/` directory and regenerates
+`src/generated/subsystems.ts` so the removed subsystem drops out of the
+`SUBSYSTEM_MODULES` barrel. Git-safety gated like install (warns on
+uncommitted changes; `--force` overrides). `--yes`/`-y` is accepted for flag
+parity with `install`.
+
+What removal does NOT do (intentionally — explicit beats silent rewrites):
+
+- It does **not** strip the `<name>:` block from `codegen.config.yaml`.
+- It does **not** remove the `<Name>Module.forRoot(...)` line from
+  `app.module.ts`.
+- It does **not** strip shared runtime deps (`src/shared/types/drizzle.ts`,
+  `src/shared/constants/tokens.ts`) — other subsystems may still need them.
+
+The CLI prints the two follow-up edits on success. `openapi-config` (a
+config-only pseudo-subsystem) and `auth-integrations` (vendored outside the
+subsystems root, alongside the codegen-emitted entity layer) are not
+auto-removable — the command errors with the right manual next-step.

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

@@ -5,7 +5,6 @@ import '../../types/drizzle.js';
 import 'drizzle-orm/node-postgres';
 import '../jobs/jobs-domain.module.js';
 import '../jobs/bullmq.config.js';
-import 'bullmq';
 import '../jobs/pool-config.loader.js';
 import '../../../job-orchestrator.protocol-CHOEqBDk.js';
 import '../events/event-bus.protocol.js';