@prisma-next/cli 0.1.0-dev.3 → 0.1.0-dev.30

package/README.md

@@ -19,7 +19,7 @@ Provide a command-line interface that:
 - **TS Contract Loading**: Bundle and load TypeScript contract files with import allowlist enforcement
 - **CLI Command Interface**: Parse arguments and route to command handlers using commander
 - **File I/O**: Read TS contracts, write emitted artifacts (`contract.json`, `contract.d.ts`)
-- **Extension Pack Loading**: Load adapter and extension pack manifests for emission
+- **Extension Pack Descriptor Assembly**: Collect adapter and extension descriptors for emission
 - **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
 
@@ -53,7 +53,7 @@ The `contract emit` command requires a `driver` in the config (even though it do
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
 import postgresDriver from '@prisma-next/driver-postgres/control';
-import postgres from '@prisma-next/targets-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
 import sql from '@prisma-next/family-sql/control';
 import { contract } from './prisma/contract';
 
@@ -62,7 +62,7 @@ export default defineConfig({
   target: postgres,
   adapter: postgresAdapter,
   driver: postgresDriver, // Required even though emit doesn't use it
-  extensions: [],
+  extensionPacks: [],
   contract: {
     source: contract,
     output: 'src/prisma/contract.json',
@@ -134,7 +134,7 @@ The `db verify` command requires a `driver` in the config to connect to the data
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
 import postgresDriver from '@prisma-next/driver-postgres/control';
-import postgres from '@prisma-next/targets-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
 import sql from '@prisma-next/family-sql/control';
 import { contract } from './prisma/contract';
 
@@ -143,7 +143,7 @@ export default defineConfig({
   target: postgres,
   adapter: postgresAdapter,
   driver: postgresDriver,
-  extensions: [],
+  extensionPacks: [],
   contract: {
     source: contract,
     output: 'src/prisma/contract.json',
@@ -221,20 +221,21 @@ Failure:
 
 **Family Requirements:**
 
-The family must provide a `create()` method in the family descriptor that returns a `FamilyInstance` with a `verify()` method:
+The family must provide a `create()` method in the family descriptor that returns a `ControlFamilyInstance` with a `verify()` method:
 
 ```typescript
-interface FamilyDescriptor {
+interface ControlFamilyDescriptor {
   create(options: {
-    target: TargetDescriptor;
-    adapter: AdapterDescriptor;
-    extensions: ExtensionDescriptor[];
-  }): FamilyInstance;
+    target: ControlTargetDescriptor;
+    adapter: ControlAdapterDescriptor;
+    driver: ControlDriverDescriptor;
+    extensions: ControlExtensionDescriptor[];
+  }): ControlFamilyInstance;
 }
 
-interface FamilyInstance {
+interface ControlFamilyInstance {
   verify(options: {
-    driver: ControlPlaneDriver;
+    driver: ControlDriverInstance;
     contractIR: ContractIR;
     expectedTargetId: string;
     contractPath: string;
@@ -287,7 +288,7 @@ The `db introspect` command requires a `driver` in the config to connect to the
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
 import postgresDriver from '@prisma-next/driver-postgres/control';
-import postgres from '@prisma-next/targets-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
 import sql from '@prisma-next/family-sql/control';
 
 export default defineConfig({
@@ -295,7 +296,7 @@ export default defineConfig({
   target: postgres,
   adapter: postgresAdapter,
   driver: postgresDriver,
-  extensions: [],
+  extensionPacks: [],
   db: {
     url: process.env.DATABASE_URL, // Optional: can also use --db flag
   },
@@ -377,11 +378,11 @@ sql schema (tables: 2)
 **Family Requirements:**
 
 The family must provide:
-1. A `create()` method in the family descriptor that returns a `FamilyInstance` with an `introspect()` method
-2. An optional `toSchemaView()` method on the `FamilyInstance` to project family-specific schema IR into `CoreSchemaView`
+1. A `create()` method in the family descriptor that returns a `ControlFamilyInstance` with an `introspect()` method
+2. An optional `toSchemaView()` method on the `ControlFamilyInstance` to project family-specific schema IR into `CoreSchemaView`
 
 ```typescript
-interface FamilyInstance {
+interface ControlFamilyInstance {
   introspect(options: {
     driver: ControlDriverInstance;
     contractIR?: ContractIR;
@@ -438,7 +439,7 @@ The `db sign` command requires a `driver` in the config to connect to the databa
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
 import postgresDriver from '@prisma-next/driver-postgres/control';
-import postgres from '@prisma-next/targets-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
 import sql from '@prisma-next/family-sql/control';
 import { contract } from './prisma/contract';
 
@@ -447,7 +448,7 @@ export default defineConfig({
   target: postgres,
   adapter: postgresAdapter,
   driver: postgresDriver,
-  extensions: [],
+  extensionPacks: [],
   contract: {
     source: contract,
     output: 'src/prisma/contract.json',
@@ -583,10 +584,10 @@ The `db sign` command is idempotent and safe to run multiple times:
 - Safe to run in CI/deployment pipelines
 
 **Family Requirements:**
-The family must provide a `create()` method in the family descriptor that returns a `FamilyInstance` with `schemaVerify()` and `sign()` methods:
+The family must provide a `create()` method in the family descriptor that returns a `ControlFamilyInstance` with `schemaVerify()` and `sign()` methods:
 
 ```typescript
-interface FamilyInstance {
+interface ControlFamilyInstance {
   schemaVerify(options: {
     driver: ControlDriverInstance;
     contractIR: ContractIR;
@@ -606,9 +607,159 @@ interface FamilyInstance {
 
 The SQL family provides this via `@prisma-next/family-sql/control`. The `sign()` method handles ensuring the marker schema/table exist, reading existing markers, comparing hashes, and writing/updating markers internally.
 
+### `prisma-next db init`
+
+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
+prisma-next db init [--db <url>] [--config <path>] [--plan] [--json] [-v] [-q] [--timestamps] [--color/--no-color]
+```
+
+Options:
+- `--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`: 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)
+- `--timestamps`: Add timestamps to output
+- `--color/--no-color`: Force/disable color output
+
+Examples:
+```bash
+# Initialize database with config defaults
+prisma-next db init
+
+# Preview migration plan without applying
+prisma-next db init --plan
+
+# Specify database URL
+prisma-next db init --db postgresql://user:pass@localhost/db
+
+# JSON output
+prisma-next db init --json
+```
+
+**Config File Requirements:**
+
+The `db init` command requires a `driver` in the config to connect to the database:
+
+```typescript
+import { defineConfig } from '@prisma-next/cli/config-types';
+import postgresAdapter from '@prisma-next/adapter-postgres/control';
+import postgresDriver from '@prisma-next/driver-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
+import sql from '@prisma-next/family-sql/control';
+import { contract } from './prisma/contract';
+
+export default defineConfig({
+  family: sql,
+  target: postgres,
+  adapter: postgresAdapter,
+  driver: postgresDriver,
+  extensionPacks: [],
+  contract: {
+    source: contract,
+    output: 'src/prisma/contract.json',
+    types: 'src/prisma/contract.d.ts',
+  },
+  db: {
+    url: process.env.DATABASE_URL, // Optional: can also use --db flag
+  },
+});
+```
+
+**Initialization Process:**
+
+1. **Load Contract**: Reads the emitted `contract.json` from `config.contract.output`
+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. **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
+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 ledger entry
+
+**Output Format (TTY - Plan Mode):**
+
+```
+prisma-next db init ➜ Initialize database schema from contract
+  config:          prisma-next.config.ts
+  contract:        src/prisma/contract.json
+  database:        localhost:5432/mydb
+
+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"
+
+Run without --plan to apply this migration.
+```
+
+**Output Format (TTY - Apply Mode):**
+
+```
+prisma-next db init ➜ Initialize database schema from contract
+  config:          prisma-next.config.ts
+  contract:        src/prisma/contract.json
+  database:        localhost:5432/mydb
+
+✔ 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):**
+
+```json
+{
+  "ok": true,
+  "mode": "apply",
+  "plan": {
+    "operations": [...],
+    "conflicts": []
+  },
+  "execution": {
+    "operations": [...],
+    "marker": {
+      "coreHash": "sha256:abc123...",
+      "profileHash": "sha256:def456..."
+    },
+    "ledger": {
+      "id": "ledger-entry-uuid",
+      "createdAt": "2025-01-01T00:00:00Z"
+    }
+  }
+}
+```
+
+**Error Codes:**
+- `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`):**
 
-The CLI uses a config file to specify the target family, target, adapter, extensions, and contract.
+The CLI uses a config file to specify the target family, target, adapter, extensionPacks, and contract.
 
 **Config Discovery:**
 - `--config <path>`: Explicit path (relative or absolute)
@@ -620,7 +771,7 @@ The CLI uses a config file to specify the target family, target, adapter, extens
 ```typescript
 import { defineConfig } from '@prisma-next/cli/config-types';
 import postgresAdapter from '@prisma-next/adapter-postgres/control';
-import postgres from '@prisma-next/targets-postgres/control';
+import postgres from '@prisma-next/target-postgres/control';
 import sql from '@prisma-next/family-sql/control';
 import { contract } from './prisma/contract';
 
@@ -628,7 +779,7 @@ export default defineConfig({
   family: sql,
   target: postgres,
   adapter: postgresAdapter,
-  extensions: [],
+  extensionPacks: [],
   contract: {
     source: contract, // Can be a value or a function: () => import('./contract').then(m => m.contract)
     output: 'src/prisma/contract.json', // Optional: defaults to 'src/prisma/contract.json'
@@ -724,7 +875,7 @@ See `.cursor/rules/config-validation-and-normalization.mdc` for detailed pattern
 
 ### Pack Assembly
 - **Family instances** now handle pack assembly internally. The CLI creates a family instance via `config.family.create()` and reads assembly data (operation registry, type imports, extension IDs) from the instance.
-- **Removed**: `pack-assembly.ts` has been removed. Pack assembly is now handled by family instances. For SQL family, tests can import pack-based helpers directly from `packages/sql/family/src/core/assembly.ts` using relative paths.
+- **Removed**: `pack-assembly.ts` has been removed. Pack assembly is now handled by family instances. For SQL family, tests can import pack-based helpers directly from `packages/2-sql/3-tooling/family/src/core/assembly.ts` using relative paths.
 - Assembly logic is family-specific and owned by each family's instance implementation (e.g., `createSqlFamilyInstance` in `@prisma-next/family-sql`).
 
 ### Output Formatting (`utils/output.ts`)
@@ -758,8 +909,63 @@ See `.cursor/rules/config-validation-and-normalization.mdc` for detailed pattern
   - `schemaVerify(options)` - Verifies database schema against contract
   - `introspect(options)` - Introspects database schema
 
-### Pack Manifest Types (IR)
-- Families define their manifest IR and related types under their own tooling packages. CLI treats manifests as opaque data.
+### Descriptor Declarative Fields
+- Families expose component descriptors (target, adapter, driver, extensions) as plain TypeScript objects. Each descriptor includes **declarative fields**: metadata that describes what the component *provides* (independent of its runtime implementation), and that the CLI can safely copy into emitted artifacts.
+  - Common declarative keys:
+    - **`version`**: Component version included in emitted metadata (useful for debugging and reproducibility).
+    - **`capabilities`**: Feature flags the component contributes (e.g., adapter/runtime lowering requirements). Typically namespaced by target (e.g., `{ postgres: { returning: true } }`) so contracts can be validated against the active target.
+    - **`types`**: Type import specs and type IDs contributed by the component. Common examples:
+      - `types.codecTypes.import`: Where to import codec type mappings for `contract.d.ts`.
+      - `types.operationTypes.import`: Where to import operation type mappings for `contract.d.ts` (extensions).
+      - `types.storage`: Storage type bindings (`typeId`, `nativeType`, etc.) used in authoring/emission.
+    - **`operations`**: Operation signatures the component contributes (extensions), used for type generation and (optionally) validation/lowering.
+    - **Component-specific metadata**:
+      - Extensions may also include control-plane-only metadata like `databaseDependencies` (used by verify/schema-verify and not required at runtime).
+
+Unlike the older **manifest-based IR** approach (separate JSON manifests + a parsing/validation step to build an IR), descriptors are imported directly from packages (e.g., `@prisma-next/*/control`). This removes a file-format boundary and keeps the data and its types co-located.
+- Benefits: fewer moving parts (no JSON parsing), easier refactors (TypeScript catches drift), and clearer ownership (the package exports the canonical descriptor object).
+- Trade-offs: descriptors must be available as build-time imports (less dynamic discovery vs scanning arbitrary manifest files).
+
+**Illustrative example (descriptor object):**
+
+```typescript
+import type { SqlControlExtensionDescriptor } from '@prisma-next/family-sql/control';
+
+const exampleExtension: SqlControlExtensionDescriptor<'postgres'> = {
+  kind: 'extension',
+  id: 'example',
+  version: '1.0.0',
+  familyId: 'sql',
+  targetId: 'postgres',
+  capabilities: { postgres: { 'example/feature': true } },
+  types: {
+    operationTypes: {
+      import: {
+        package: '@prisma-next/extension-example/operation-types',
+        named: 'OperationTypes',
+        alias: 'ExampleOperationTypes',
+      },
+    },
+  },
+  operations: [],
+  create: () => ({ familyId: 'sql', targetId: 'postgres' }),
+};
+
+export default exampleExtension;
+```
+
+**How CLI consumers import/use it:**
+- Config imports descriptors directly and passes them to `defineConfig()` (see “Config File Requirements” under `prisma-next contract emit` above; also see “Entrypoints” below for the `@prisma-next/*/control` subpaths):
+
+```typescript
+import { defineConfig } from '@prisma-next/cli/config-types';
+import exampleExtension from '@prisma-next/extension-example/control';
+
+export default defineConfig({
+  // family/target/adapter/driver omitted for brevity
+  extensionPacks: [exampleExtension],
+});
+```
 
 ## Dependencies
 
@@ -831,7 +1037,7 @@ The CLI package exports several subpaths for different use cases:
 
 - **`@prisma-next/cli`** (main export): Exports `loadContractFromTs` and `createContractEmitCommand`
 - **`@prisma-next/cli/config-types`**: Exports `defineConfig` and config types
-- **`@prisma-next/cli/pack-loading`**: Exports `loadExtensionPacks` and `loadExtensionPackManifest`
+- **`@prisma-next/cli/commands/db-init`**: Exports `createDbInitCommand`
 - **`@prisma-next/cli/commands/db-introspect`**: Exports `createDbIntrospectCommand`
 - **`@prisma-next/cli/commands/db-schema-verify`**: Exports `createDbSchemaVerifyCommand`
 - **`@prisma-next/cli/commands/db-sign`**: Exports `createDbSignCommand`
@@ -839,7 +1045,7 @@ The CLI package exports several subpaths for different use cases:
 - **`@prisma-next/cli/commands/contract-emit`**: Exports `createContractEmitCommand`
 - **`@prisma-next/cli/config-loader`**: Exports `loadConfig` function
 
-**Important**: `loadContractFromTs` is exported from the main package (`@prisma-next/cli`), not from `@prisma-next/cli/pack-loading`. See `.cursor/rules/cli-package-exports.mdc` for import patterns.
+**Important**: `loadContractFromTs` is exported from the main package (`@prisma-next/cli`). See `.cursor/rules/cli-package-exports.mdc` for import patterns.
 
 ## Package Location
 
@@ -847,7 +1053,7 @@ This package is part of the **framework domain**, **tooling layer**, **migration
 - **Domain**: framework (target-agnostic)
 - **Layer**: tooling
 - **Plane**: migration
-- **Path**: `packages/framework/tooling/cli`
+- **Path**: `packages/1-framework/3-tooling/cli`
 
 ## See Also
 

package/dist/{chunk-4Q3MO4TK.js → chunk-464LNZCE.js}

@@ -9,7 +9,7 @@ import {
   performAction,
   setCommandDescriptions,
   withSpinner
-} from "./chunk-3EODSNGS.js";
+} from "./chunk-BZMBKEEQ.js";
 import {
   loadConfig
 } from "./chunk-HWYQOCAJ.js";
@@ -74,7 +74,7 @@ function createContractEmitCommand() {
         target: config.target,
         adapter: config.adapter,
         driver: config.driver,
-        extensions: config.extensions ?? []
+        extensionPacks: config.extensionPacks ?? []
       });
       let contractRaw;
       if (typeof contractConfig.source === "function") {
@@ -131,4 +131,4 @@ function createContractEmitCommand() {
 export {
   createContractEmitCommand
 };
-//# sourceMappingURL=chunk-4Q3MO4TK.js.map
+//# sourceMappingURL=chunk-464LNZCE.js.map

package/dist/chunk-464LNZCE.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/commands/contract-emit.ts"],"sourcesContent":["import { mkdirSync, writeFileSync } from 'node:fs';\nimport { dirname, relative, resolve } from 'node:path';\nimport { errorContractConfigMissing } from '@prisma-next/core-control-plane/errors';\nimport { Command } from 'commander';\nimport { loadConfig } from '../config-loader';\nimport { performAction } from '../utils/action';\nimport { setCommandDescriptions } from '../utils/command-helpers';\nimport { parseGlobalFlags } from '../utils/global-flags';\nimport {\n  formatCommandHelp,\n  formatEmitJson,\n  formatEmitOutput,\n  formatStyledHeader,\n  formatSuccessMessage,\n} from '../utils/output';\nimport { handleResult } from '../utils/result-handler';\nimport { withSpinner } from '../utils/spinner';\n\ninterface ContractEmitOptions {\n  readonly config?: string;\n  readonly json?: string | boolean;\n  readonly quiet?: boolean;\n  readonly q?: boolean;\n  readonly verbose?: boolean;\n  readonly v?: boolean;\n  readonly vv?: boolean;\n  readonly trace?: boolean;\n  readonly timestamps?: boolean;\n  readonly color?: boolean;\n  readonly 'no-color'?: boolean;\n}\n\nexport function createContractEmitCommand(): Command {\n  const command = new Command('emit');\n  setCommandDescriptions(\n    command,\n    'Write your contract to JSON and sign it',\n    'Reads your contract source (TypeScript or Prisma schema) and emits contract.json and\\n' +\n      'contract.d.ts. The contract.json contains the canonical contract structure, and\\n' +\n      'contract.d.ts provides TypeScript types for type-safe query building.',\n  );\n  command\n    .configureHelp({\n      formatHelp: (cmd) => {\n        const flags = parseGlobalFlags({});\n        return formatCommandHelp({ command: cmd, flags });\n      },\n    })\n    .option('--config <path>', 'Path to prisma-next.config.ts')\n    .option('--json [format]', 'Output as JSON (object or ndjson)', false)\n    .option('-q, --quiet', 'Quiet mode: errors only')\n    .option('-v, --verbose', 'Verbose output: debug info, timings')\n    .option('-vv, --trace', 'Trace output: deep internals, stack traces')\n    .option('--timestamps', 'Add timestamps to output')\n    .option('--color', 'Force color output')\n    .option('--no-color', 'Disable color output')\n    .action(async (options: ContractEmitOptions) => {\n      const flags = parseGlobalFlags(options);\n\n      const result = await performAction(async () => {\n        // Load config\n        const config = await loadConfig(options.config);\n\n        // Resolve contract from config\n        if (!config.contract) {\n          throw errorContractConfigMissing({\n            why: 'Config.contract is required for emit. Define it in your config: contract: { source: ..., output: ..., types: ... }',\n          });\n        }\n\n        // Contract config is already normalized by defineConfig() with defaults applied\n        const contractConfig = config.contract;\n\n        // Resolve artifact paths from config (already normalized by defineConfig() with defaults)\n        if (!contractConfig.output || !contractConfig.types) {\n          throw errorContractConfigMissing({\n            why: 'Contract config must have output and types paths. This should not happen if defineConfig() was used.',\n          });\n        }\n        const outputJsonPath = resolve(contractConfig.output);\n        const outputDtsPath = resolve(contractConfig.types);\n\n        // Output header (only for human-readable output)\n        if (flags.json !== 'object' && !flags.quiet) {\n          // Normalize config path for display (match contract path format - no ./ prefix)\n          const configPath = options.config\n            ? relative(process.cwd(), resolve(options.config))\n            : 'prisma-next.config.ts';\n          // Convert absolute paths to relative paths for display\n          const contractPath = relative(process.cwd(), outputJsonPath);\n          const typesPath = relative(process.cwd(), outputDtsPath);\n          const header = formatStyledHeader({\n            command: 'contract emit',\n            description: 'Write your contract to JSON and sign it',\n            url: 'https://pris.ly/contract-emit',\n            details: [\n              { label: 'config', value: configPath },\n              { label: 'contract', value: contractPath },\n              { label: 'types', value: typesPath },\n            ],\n            flags,\n          });\n          console.log(header);\n        }\n\n        // Create family instance (assembles operation registry, type imports, extension IDs)\n        // Note: emit command doesn't need driver, but ControlFamilyDescriptor.create() requires it\n        // We'll need to provide a minimal driver descriptor or make driver optional for emit\n        // For now, we'll require driver to be present in config even for emit\n        if (!config.driver) {\n          throw errorContractConfigMissing({\n            why: 'Config.driver is required. Even though emit does not use the driver, it is required by ControlFamilyDescriptor.create()',\n          });\n        }\n        const familyInstance = config.family.create({\n          target: config.target,\n          adapter: config.adapter,\n          driver: config.driver,\n          extensionPacks: config.extensionPacks ?? [],\n        });\n\n        // Resolve contract source from config (user's config handles loading)\n        let contractRaw: unknown;\n        if (typeof contractConfig.source === 'function') {\n          contractRaw = await contractConfig.source();\n        } else {\n          contractRaw = contractConfig.source;\n        }\n\n        // Call emitContract on family instance (handles stripping mappings and validation internally)\n        const emitResult = await withSpinner(\n          () => familyInstance.emitContract({ contractIR: contractRaw }),\n          {\n            message: 'Emitting contract...',\n            flags,\n          },\n        );\n\n        // Create directories if needed\n        mkdirSync(dirname(outputJsonPath), { recursive: true });\n        mkdirSync(dirname(outputDtsPath), { recursive: true });\n\n        // Write the results to files\n        writeFileSync(outputJsonPath, emitResult.contractJson, 'utf-8');\n        writeFileSync(outputDtsPath, emitResult.contractDts, 'utf-8');\n\n        // Add blank line after all async operations if spinners were shown\n        if (!flags.quiet && flags.json !== 'object' && process.stdout.isTTY) {\n          console.log('');\n        }\n\n        // Return result with file paths for output formatting\n        return {\n          coreHash: emitResult.coreHash,\n          profileHash: emitResult.profileHash,\n          outDir: dirname(outputJsonPath),\n          files: {\n            json: outputJsonPath,\n            dts: outputDtsPath,\n          },\n          timings: {\n            total: 0, // Timing is handled by emitContract internally if needed\n          },\n        };\n      });\n\n      // Handle result - formats output and returns exit code\n      const exitCode = handleResult(result, flags, (emitResult) => {\n        // Output based on flags\n        if (flags.json === 'object') {\n          // JSON output to stdout\n          console.log(formatEmitJson(emitResult));\n        } else {\n          // Human-readable output to stdout\n          const output = formatEmitOutput(emitResult, flags);\n          if (output) {\n            console.log(output);\n          }\n          // Output success message\n          if (!flags.quiet) {\n            console.log(formatSuccessMessage(flags));\n          }\n        }\n      });\n      process.exit(exitCode);\n    });\n\n  return command;\n}\n"],"mappings":";;;;;;;;;;;;;;;;;AAAA,SAAS,WAAW,qBAAqB;AACzC,SAAS,SAAS,UAAU,eAAe;AAC3C,SAAS,kCAAkC;AAC3C,SAAS,eAAe;AA6BjB,SAAS,4BAAqC;AACnD,QAAM,UAAU,IAAI,QAAQ,MAAM;AAClC;AAAA,IACE;AAAA,IACA;AAAA,IACA;AAAA,EAGF;AACA,UACG,cAAc;AAAA,IACb,YAAY,CAAC,QAAQ;AACnB,YAAM,QAAQ,iBAAiB,CAAC,CAAC;AACjC,aAAO,kBAAkB,EAAE,SAAS,KAAK,MAAM,CAAC;AAAA,IAClD;AAAA,EACF,CAAC,EACA,OAAO,mBAAmB,+BAA+B,EACzD,OAAO,mBAAmB,qCAAqC,KAAK,EACpE,OAAO,eAAe,yBAAyB,EAC/C,OAAO,iBAAiB,qCAAqC,EAC7D,OAAO,gBAAgB,4CAA4C,EACnE,OAAO,gBAAgB,0BAA0B,EACjD,OAAO,WAAW,oBAAoB,EACtC,OAAO,cAAc,sBAAsB,EAC3C,OAAO,OAAO,YAAiC;AAC9C,UAAM,QAAQ,iBAAiB,OAAO;AAEtC,UAAM,SAAS,MAAM,cAAc,YAAY;AAE7C,YAAM,SAAS,MAAM,WAAW,QAAQ,MAAM;AAG9C,UAAI,CAAC,OAAO,UAAU;AACpB,cAAM,2BAA2B;AAAA,UAC/B,KAAK;AAAA,QACP,CAAC;AAAA,MACH;AAGA,YAAM,iBAAiB,OAAO;AAG9B,UAAI,CAAC,eAAe,UAAU,CAAC,eAAe,OAAO;AACnD,cAAM,2BAA2B;AAAA,UAC/B,KAAK;AAAA,QACP,CAAC;AAAA,MACH;AACA,YAAM,iBAAiB,QAAQ,eAAe,MAAM;AACpD,YAAM,gBAAgB,QAAQ,eAAe,KAAK;AAGlD,UAAI,MAAM,SAAS,YAAY,CAAC,MAAM,OAAO;AAE3C,cAAM,aAAa,QAAQ,SACvB,SAAS,QAAQ,IAAI,GAAG,QAAQ,QAAQ,MAAM,CAAC,IAC/C;AAEJ,cAAM,eAAe,SAAS,QAAQ,IAAI,GAAG,cAAc;AAC3D,cAAM,YAAY,SAAS,QAAQ,IAAI,GAAG,aAAa;AACvD,cAAM,SAAS,mBAAmB;AAAA,UAChC,SAAS;AAAA,UACT,aAAa;AAAA,UACb,KAAK;AAAA,UACL,SAAS;AAAA,YACP,EAAE,OAAO,UAAU,OAAO,WAAW;AAAA,YACrC,EAAE,OAAO,YAAY,OAAO,aAAa;AAAA,YACzC,EAAE,OAAO,SAAS,OAAO,UAAU;AAAA,UACrC;AAAA,UACA;AAAA,QACF,CAAC;AACD,gBAAQ,IAAI,MAAM;AAAA,MACpB;AAMA,UAAI,CAAC,OAAO,QAAQ;AAClB,cAAM,2BAA2B;AAAA,UAC/B,KAAK;AAAA,QACP,CAAC;AAAA,MACH;AACA,YAAM,iBAAiB,OAAO,OAAO,OAAO;AAAA,QAC1C,QAAQ,OAAO;AAAA,QACf,SAAS,OAAO;AAAA,QAChB,QAAQ,OAAO;AAAA,QACf,gBAAgB,OAAO,kBAAkB,CAAC;AAAA,MAC5C,CAAC;AAGD,UAAI;AACJ,UAAI,OAAO,eAAe,WAAW,YAAY;AAC/C,sBAAc,MAAM,eAAe,OAAO;AAAA,MAC5C,OAAO;AACL,sBAAc,eAAe;AAAA,MAC/B;AAGA,YAAM,aAAa,MAAM;AAAA,QACvB,MAAM,eAAe,aAAa,EAAE,YAAY,YAAY,CAAC;AAAA,QAC7D;AAAA,UACE,SAAS;AAAA,UACT;AAAA,QACF;AAAA,MACF;AAGA,gBAAU,QAAQ,cAAc,GAAG,EAAE,WAAW,KAAK,CAAC;AACtD,gBAAU,QAAQ,aAAa,GAAG,EAAE,WAAW,KAAK,CAAC;AAGrD,oBAAc,gBAAgB,WAAW,cAAc,OAAO;AAC9D,oBAAc,eAAe,WAAW,aAAa,OAAO;AAG5D,UAAI,CAAC,MAAM,SAAS,MAAM,SAAS,YAAY,QAAQ,OAAO,OAAO;AACnE,gBAAQ,IAAI,EAAE;AAAA,MAChB;AAGA,aAAO;AAAA,QACL,UAAU,WAAW;AAAA,QACrB,aAAa,WAAW;AAAA,QACxB,QAAQ,QAAQ,cAAc;AAAA,QAC9B,OAAO;AAAA,UACL,MAAM;AAAA,UACN,KAAK;AAAA,QACP;AAAA,QACA,SAAS;AAAA,UACP,OAAO;AAAA;AAAA,QACT;AAAA,MACF;AAAA,IACF,CAAC;AAGD,UAAM,WAAW,aAAa,QAAQ,OAAO,CAAC,eAAe;AAE3D,UAAI,MAAM,SAAS,UAAU;AAE3B,gBAAQ,IAAI,eAAe,UAAU,CAAC;AAAA,MACxC,OAAO;AAEL,cAAM,SAAS,iBAAiB,YAAY,KAAK;AACjD,YAAI,QAAQ;AACV,kBAAQ,IAAI,MAAM;AAAA,QACpB;AAEA,YAAI,CAAC,MAAM,OAAO;AAChB,kBAAQ,IAAI,qBAAqB,KAAK,CAAC;AAAA,QACzC;AAAA,MACF;AAAA,IACF,CAAC;AACD,YAAQ,KAAK,QAAQ;AAAA,EACvB,CAAC;AAEH,SAAO;AACT;","names":[]}