@prisma-next/cli 0.1.0-pr.72.2 → 0.3.0-dev.1

package/README.md

@@ -23,6 +23,20 @@ Provide a command-line interface that:
 - **Help Output Formatting**: Custom styled help output with command trees and formatted descriptions
 - **Config Management**: Load and validate `prisma-next.config.ts` files using Arktype validation
 
+### Wiring validation
+
+The CLI performs **wiring validation** at the composition boundary: it ensures the emitted contract artifacts are compatible with the descriptors wired in `prisma-next.config.ts`.
+
+This prevents runtime mismatches (for example: a contract that declares extension packs, but a config that doesn’t provide the matching descriptors).
+
+Commands that enforce wiring validation:
+- **`db verify`**
+- **`db introspect`** (when a contract is provided)
+- **`db sign`**
+- **`db init`**
+
+If you hit a wiring validation error: add the required descriptors to `config.extensionPacks` (matched by descriptor `id`) and re-run the command.
+
 **Note**: Control plane domain actions (database verification, contract emission) are implemented in `@prisma-next/core-control-plane`. The CLI uses the control plane domain actions programmatically but does not define control plane types itself.
 
 ## Command Descriptions
@@ -130,8 +144,6 @@ prisma-next db verify -v --timestamps
 
 The `db verify` command requires a `driver` in the config to connect to the database:
 
-If your emitted `contract.json` declares `extensionPacks`, your config must include matching descriptors in `extensionPacks` (by `id`). The CLI validates this wiring before running the command.
-
 ```typescript
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
@@ -648,8 +660,6 @@ prisma-next db init --json
 
 The `db init` command requires a `driver` in the config to connect to the database:
 
-If your emitted `contract.json` declares `extensionPacks`, your config must include matching descriptors in `extensionPacks` (by `id`). The CLI validates this wiring before running the command.
-
 ```typescript
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma-next/cli",
-  "version": "0.1.0-pr.72.2",
+  "version": "0.3.0-dev.1",
   "type": "module",
   "sideEffects": false,
   "files": [
@@ -19,10 +19,10 @@
     "string-width": "^7.2.0",
     "strip-ansi": "^7.1.2",
     "wrap-ansi": "^9.0.2",
-    "@prisma-next/contract": "0.1.0-pr.72.2",
-    "@prisma-next/core-control-plane": "0.1.0-pr.72.2",
-    "@prisma-next/emitter": "0.1.0-pr.72.2",
-    "@prisma-next/utils": "0.1.0-pr.72.2"
+    "@prisma-next/contract": "0.3.0-dev.1",
+    "@prisma-next/core-control-plane": "0.3.0-dev.1",
+    "@prisma-next/emitter": "0.3.0-dev.1",
+    "@prisma-next/utils": "0.3.0-dev.1"
   },
   "devDependencies": {
     "@types/node": "24.10.4",
@@ -31,11 +31,11 @@
     "typescript": "^5.9.3",
     "vite-tsconfig-paths": "^5.1.4",
     "vitest": "^4.0.16",
-    "@prisma-next/sql-contract": "0.1.0-pr.72.2",
-    "@prisma-next/sql-contract-emitter": "0.1.0-pr.72.2",
-    "@prisma-next/sql-contract-ts": "0.1.0-pr.72.2",
-    "@prisma-next/sql-operations": "0.1.0-pr.72.2",
-    "@prisma-next/sql-runtime": "0.1.0-pr.72.2",
+    "@prisma-next/sql-contract": "0.3.0-dev.1",
+    "@prisma-next/sql-contract-emitter": "0.3.0-dev.1",
+    "@prisma-next/sql-contract-ts": "0.3.0-dev.1",
+    "@prisma-next/sql-operations": "0.3.0-dev.1",
+    "@prisma-next/sql-runtime": "0.3.0-dev.1",
     "@prisma-next/test-utils": "0.0.1"
   },
   "exports": {