@pattern-stack/codegen 0.12.0 → 0.12.1

package/CHANGELOG.md

@@ -4,6 +4,30 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [0.12.1] — 2026-05-31
+
+Track D (provider/adapter integration codegen) discoverability fix. The 0.12.0
+generator wiring is correct and shipped — provider + adapter emission runs as a
+post-step of `codegen entity new` whenever `definitions/providers/*.yaml` exist
+— but nothing in the CLI surfaced that, so consumers searched `--help` for a
+`provider` / `integration` / `gen` command, found none, and mistook a working
+feature for a publish gap. Docs-and-help only; no generator behavior changed.
+
+### Changed
+
+- **`codegen entity new --help`** now documents every post-generation step it
+  runs (event / bridge / orchestration / **provider + adapter (Track D)**
+  codegen), including Track D's trigger (`definitions/providers/*.yaml`), output
+  paths (`<backendSrc>/integrations/{providers,}`), emit-once semantics, and an
+  explicit note that there is no standalone `provider` / `integration` / `gen`
+  command — Track D is driven entirely by re-running `entity new`.
+- **`codegen entity` summary hints** now surface a Track D regen hint when the
+  project has a providers directory — a discoverability path that does not
+  require reading `entity new --help`.
+- **Integration domain skill** (`protocols-and-ports.md`, `SKILL.md`) documents
+  the Track D invocation, the skip-when-no-providers-dir behavior, and that the
+  generated scaffold (not the `.d.ts`) is ground truth for adapter port shape.
+
 ## [0.12.0] — 2026-05-31
 
 Integration codegen retarget (RFC-0001): a **provider/adapter/surface** model
@@ -12,8 +36,11 @@ for integration codegen, plus a **surface-package framework**. Additive over
 is unchanged. The one breaking item (the ADR-033.2 per-entity provider tuples)
 has no consumers. Consumers adopt by adding `definitions/providers/*.yaml` and
 regenerating. Ships alongside four independently-versioned **surface packages**
-(`@pattern-stack/codegen-{crm,calendar,mail,transcript}`) publishing fresh at
-`0.1.0`.
+(`@pattern-stack/codegen-{crm,calendar,mail,transcript}`) at `0.1.1`. (Their
+initial `0.1.0` release peer-depended on `@pattern-stack/codegen` `^0.11.0`,
+which predates the `./subsystems` export they require; `0.1.1` corrects the peer
+to `^0.12.0`. The peer source fix merged with 0.12.0 but the version bump was
+missed — this completes it.)
 
 ### ⚠ BREAKING CHANGES
 
@@ -41,7 +68,7 @@ regenerating. Ships alongside four independently-versioned **surface packages**
     conformance helper (on the `/testing` subpath).
   - **`@pattern-stack/codegen-{calendar,mail,transcript}`** — incremental-read
     interaction surfaces (`CalendarPort` / `MailPort` / `TranscriptPort`,
-    canonical types, capability descriptors). Independently versioned (`0.1.0`).
+    canonical types, capability descriptors). Independently versioned (`0.1.1`).
 - **Track D — provider/adapter integration codegen (RFC-0001).**
   - `definitions/providers/<provider>.yaml` — providers as first-class
     declarative artifacts (slug, auth strategy, client, surfaces); Zod schema +

package/dist/src/cli/index.js

@@ -8740,20 +8740,45 @@ async function hints(ctx) {
       }
     ];
   }
-  return [
+  const baseHints = [
     { command: "codegen entity new <file>", description: "Generate one entity" },
     { command: "codegen entity new --all", description: "Regenerate all entities" },
     { command: "codegen entity validate", description: "Validate YAML definitions" },
     { command: "codegen entity list", description: "List entities as a table" }
   ];
+  const providersDir = ctx.config?.paths?.providers != null ? path13.resolve(
+    ctx.cwd,
+    ctx.config.paths.providers
+  ) : path13.resolve(ctx.cwd, "definitions/providers");
+  if (fs9.existsSync(providersDir)) {
+    baseHints.push({
+      command: "codegen entity new --all",
+      description: "Regenerate provider modules + adapter scaffolds (Track D)"
+    });
+  }
+  return baseHints;
 }
 var EntityNewCommand = class extends Command2 {
   static paths = [["entity", "new"]];
   static usage = Command2.Usage({
     description: "Generate code for one or more entities from YAML",
+    details: `
+			Generates Clean Architecture code for the named entity (or all entities with \`--all\`), then runs the post-generation codegen steps that share this entrypoint:
+
+			- **Event codegen** \u2014 \`AppDomainEvent\` union + typed bus from \`events/*.yaml\`.
+			- **Bridge registry** \u2014 when the bridge subsystem is installed.
+			- **Orchestration modules** \u2014 from orchestration patterns.
+			- **Provider + adapter codegen (Track D, RFC-0001)** \u2014 when \`definitions/providers/*.yaml\` exist, emits one provider module per file into \`<backendSrc>/integrations/providers/\` and the matching adapter scaffolds + \`@generated\` files into \`<backendSrc>/integrations/\`. Author-owned scaffolds are emit-once (never overwritten); \`@generated\` files re-emit each run. With no providers dir the step is silently skipped.
+
+			There is no separate \`provider\`, \`integration\`, or \`gen\` command \u2014 Track D codegen is driven entirely by re-running \`entity new\`. The \`just gen\` / \`just gen-all\` recipes are thin wrappers over it.
+		`,
     examples: [
       ["Generate a single entity", "codegen entity new entities/contact.yaml"],
       ["Regenerate all entities", "codegen entity new --all"],
+      [
+        "Regenerate everything incl. provider/adapter codegen",
+        "codegen entity new --all"
+      ],
       ["Preview without writing", "codegen entity new entities/contact.yaml --dry-run"]
     ]
   });