@prisma-next/cli 0.1.0-pr.72.1 → 0.2.0

package/README.md

@@ -102,7 +102,7 @@ prisma-next db verify [--db <url>] [--config <path>] [--json] [-v] [-q] [--times
 ```
 
 Options:
-- `--db <url>`: Database connection string (optional; defaults to `config.db.url` if set)
+- `--db <url>`: Database connection string (optional, falls back to `config.db.url` or `DATABASE_URL` environment variable)
 - `--config <path>`: Optional. Path to `prisma-next.config.ts` (defaults to `./prisma-next.config.ts` if present)
 - `--json`: Output as JSON object
 - `-q, --quiet`: Quiet mode (errors only)
@@ -130,8 +130,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 `extensions` (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';
@@ -258,7 +256,7 @@ prisma-next db introspect [--db <url>] [--config <path>] [--json] [-v] [-q] [--t
 ```
 
 Options:
-- `--db <url>`: Database connection string (optional; defaults to `config.db.url` if set)
+- `--db <url>`: Database connection string (optional, falls back to `config.db.url` or `DATABASE_URL` environment variable)
 - `--config <path>`: Optional. Path to `prisma-next.config.ts` (defaults to `./prisma-next.config.ts` if present)
 - `--json`: Output as JSON object
 - `-q, --quiet`: Quiet mode (errors only)
@@ -375,7 +373,7 @@ sql schema (tables: 2)
 
 **Error Codes:**
 - `PN-CLI-4010`: Missing driver in config — provide a driver descriptor
-- `PN-CLI-4005`: Missing database URL — provide `--db <url>` or set `db.url` in config
+- `PN-CLI-4011`: Missing database URL — provide `--db` flag or `config.db.url` or `DATABASE_URL` environment variable
 
 **Family Requirements:**
 
@@ -409,7 +407,7 @@ prisma-next db sign [--db <url>] [--config <path>] [--json] [-v] [-q] [--timesta
 ```
 
 Options:
-- `--db <url>`: Database connection string (optional; defaults to `config.db.url` if set)
+- `--db <url>`: Database connection string (optional, falls back to `config.db.url` or `DATABASE_URL` environment variable)
 - `--config <path>`: Optional. Path to `prisma-next.config.ts` (defaults to `./prisma-next.config.ts` if present)
 - `--json`: Output as JSON object
 - `-q, --quiet`: Quiet mode (errors only)
@@ -572,7 +570,7 @@ For updated markers:
 
 **Error Codes:**
 - `PN-CLI-4010`: Missing driver in config — provide a driver descriptor
-- `PN-CLI-4005`: Missing database URL — provide `--db <url>` or set `db.url` in config
+- `PN-CLI-4011`: Missing database URL — provide `--db` flag or `config.db.url` or `DATABASE_URL` environment variable
 - Exit code 1: Schema verification failed — database schema does not match contract (marker is not written)
 
 **Relationship to Other Commands:**
@@ -611,7 +609,7 @@ The SQL family provides this via `@prisma-next/family-sql/control`. The `sign()`
 
 ### `prisma-next db init`
 
-Initialize a database schema from the contract. This command plans and applies **additive-only** operations (create missing tables/columns/constraints/indexes) until the database satisfies the contract, then writes the contract marker.
+Initialize a database schema from the contract. This command generates a migration plan to bring an empty database in sync with the contract and executes it.
 
 **Command:**
 ```bash
@@ -619,10 +617,10 @@ prisma-next db init [--db <url>] [--config <path>] [--plan] [--json] [-v] [-q] [
 ```
 
 Options:
-- `--db <url>`: Database connection string (optional; defaults to `config.db.url` if set)
+- `--db <url>`: Database connection string (optional, falls back to `config.db.url` or `DATABASE_URL` environment variable)
 - `--config <path>`: Optional. Path to `prisma-next.config.ts` (defaults to `./prisma-next.config.ts` if present)
 - `--plan`: Only show the migration plan, do not apply it
-- `--json [format]`: Output as JSON (`object` only; `ndjson` is not supported for this command)
+- `--json`: Output as JSON object
 - `-q, --quiet`: Quiet mode (errors only)
 - `-v, --verbose`: Verbose output (debug info, timings)
 - `-vv, --trace`: Trace output (deep internals, stack traces)
@@ -648,8 +646,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 `extensions` (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';
@@ -681,54 +677,49 @@ export default defineConfig({
 2. **Connect to Database**: Uses `config.driver.create(url)` to create a driver
 3. **Create Family Instance**: Calls `config.family.create()` with target, adapter, driver, and extensions
 4. **Introspect Schema**: Calls `familyInstance.introspect()` to get the current database schema IR
-5. **Validate wiring**: Ensures the contract is compatible with the CLI config:
-   - `contract.targetFamily` matches `config.family.familyId`
-   - `contract.target` matches `config.target.targetId`
-   - `contract.extensionPacks` (if present) are provided by `config.extensions` (matched by descriptor `id`)
-6. **Create Planner/Runner**: Uses `config.target.migrations.createPlanner()` and `config.target.migrations.createRunner()`
-7. **Plan Migration**: Calls `planner.plan()` with the contract IR, schema IR, additive-only policy, and `frameworkComponents` (the active target/adapter/extension descriptors)
+5. **Create Planner/Runner**: Asks the target to construct a `MigrationPlanner` and `MigrationRunner`
+6. **Plan Migration**: Calls `planner.plan()` with the contract IR, schema IR, and additive-only policy
    - On conflict: Returns a structured failure with conflict list
    - On success: Returns a migration plan with operations
-8. **Apply Migration** (if not `--plan`):
+7. **Apply Migration** (if not `--plan`):
    - Calls `runner.execute()` to apply the plan
+   - Runner executes pre/post checks for each operation
    - After execution, verifies schema matches contract
-   - Writes contract marker (and records a ledger entry via the target runner)
+   - Writes contract marker and ledger entry
 
 **Output Format (TTY - Plan Mode):**
 
 ```
-prisma-next db init ➜ Bootstrap a database to match the current contract
+prisma-next db init ➜ Initialize database schema from contract
   config:          prisma-next.config.ts
   contract:        src/prisma/contract.json
-  mode:            plan (dry run)
+  database:        localhost:5432/mydb
 
-✔ Planned 4 operation(s)
-│
-├─ Create table user [additive]
-├─ Add unique constraint user_email_key on user [additive]
-├─ Create index user_email_idx on user [additive]
-└─ Add foreign key post_userId_fkey on post [additive]
+Migration Plan (4 operations)
+├─ Create extension "plpgsql"
+├─ Create table "user"
+│   ├─ id: int4 (not null, primary key)
+│   └─ email: text (not null)
+└─ Create unique index "user_email_key"
 
-Destination hash: sha256:abc123...
-
-This is a dry run. No changes were applied.
-Run without --plan to apply changes.
+Run without --plan to apply this migration.
 ```
 
 **Output Format (TTY - Apply Mode):**
 
 ```
-prisma-next db init ➜ Bootstrap a database to match the current contract
+prisma-next db init ➜ Initialize database schema from contract
   config:          prisma-next.config.ts
   contract:        src/prisma/contract.json
+  database:        localhost:5432/mydb
 
-Applying migration plan and verifying schema...
-  → Create table user...
-  → Add unique constraint user_email_key on user...
-  → Create index user_email_idx on user...
-  → Add foreign key post_userId_fkey on post...
-✔ Applied 4 operation(s)
-  Marker written: sha256:abc123...
+✔ Applied 4 migration operations
+  ├─ Created extension "plpgsql"
+  ├─ Created table "user"
+  └─ Created unique index "user_email_key"
+✔ Contract marker written
+  coreHash: sha256:abc123...
+✔ Ledger entry recorded
 ```
 
 **Output Format (JSON):**
@@ -738,41 +729,33 @@ Applying migration plan and verifying schema...
   "ok": true,
   "mode": "apply",
   "plan": {
-    "targetId": "postgres",
-    "destination": {
-      "coreHash": "sha256:abc123..."
-    },
-    "operations": [
-      {
-        "id": "table.user",
-        "label": "Create table user",
-        "operationClass": "additive"
-      }
-    ]
+    "operations": [...],
+    "conflicts": []
   },
   "execution": {
-    "operationsPlanned": 4,
-    "operationsExecuted": 4
-  },
-  "marker": {
-    "coreHash": "sha256:abc123..."
+    "operations": [...],
+    "marker": {
+      "coreHash": "sha256:abc123...",
+      "profileHash": "sha256:def456..."
+    },
+    "ledger": {
+      "id": "ledger-entry-uuid",
+      "createdAt": "2025-01-01T00:00:00Z"
+    }
   }
 }
 ```
 
 **Error Codes:**
-- `PN-CLI-4004`: Contract file not found
-- `PN-CLI-4005`: Missing database URL
-- `PN-CLI-4008`: Unsupported JSON format (`--json ndjson` is rejected for `db init`)
-- `PN-CLI-4010`: Missing driver in config
-- `PN-CLI-4020`: Migration planning failed (conflicts)
-- `PN-CLI-4021`: Target does not support migrations
-- `PN-RTM-3000`: Runtime error (includes marker mismatch failures)
-
-**Behavior Notes:**
-
-- If the database already has a marker that matches the destination contract, `db init` succeeds as a noop (0 operations planned/executed).
-- If the database has a marker that does **not** match the destination contract, `db init` fails (including in `--plan` mode). Use `db init` for bootstrapping; use your migration workflow to reconcile existing databases.
+- `PN-CLI-4010`: Missing driver in config — provide a driver descriptor
+- `PN-CLI-4011`: Missing database URL — provide `--db` flag or `config.db.url` or `DATABASE_URL` environment variable
+- `PN-CLI-4011`: Migration planning failed due to conflicts (exit code 1)
+- `PN-CLI-4012`: Target does not support migrations
+
+**Current Limitations (v1):**
+- Only supports empty databases (no existing tables)
+- Non-empty databases result in a planning failure with conflict details
+- Future `db update` command will support additive changes to existing schemas
 
 **Config File (`prisma-next.config.ts`):**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma-next/cli",
-  "version": "0.1.0-pr.72.1",
+  "version": "0.2.0",
   "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.1",
-    "@prisma-next/core-control-plane": "0.1.0-pr.72.1",
-    "@prisma-next/emitter": "0.1.0-pr.72.1",
-    "@prisma-next/utils": "0.1.0-pr.72.1"
+    "@prisma-next/core-control-plane": "0.2.0",
+    "@prisma-next/emitter": "0.2.0",
+    "@prisma-next/contract": "0.2.0",
+    "@prisma-next/utils": "0.2.0"
   },
   "devDependencies": {
     "@types/node": "24.10.4",
@@ -31,12 +31,12 @@
     "typescript": "^5.9.3",
     "vite-tsconfig-paths": "^5.1.4",
     "vitest": "^4.0.16",
-    "@prisma-next/sql-contract": "0.1.0-pr.72.1",
-    "@prisma-next/sql-contract-emitter": "0.1.0-pr.72.1",
-    "@prisma-next/sql-contract-ts": "0.1.0-pr.72.1",
-    "@prisma-next/sql-operations": "0.1.0-pr.72.1",
-    "@prisma-next/sql-runtime": "0.1.0-pr.72.1",
-    "@prisma-next/test-utils": "0.0.1"
+    "@prisma-next/sql-contract": "0.2.0",
+    "@prisma-next/sql-contract-emitter": "0.2.0",
+    "@prisma-next/sql-runtime": "0.2.0",
+    "@prisma-next/test-utils": "0.0.1",
+    "@prisma-next/sql-operations": "0.2.0",
+    "@prisma-next/sql-contract-ts": "0.2.0"
   },
   "exports": {
     ".": {