@penvhq/cli 0.10.0 → 0.12.0

package/dist/index.d.cts

@@ -1,5 +1,6 @@
 import * as citty from 'citty';
 import { ProjectionProvider, Provider, PenvConfig, DotenvEntry, ParameterRef, Scope, DotenvDiagnostic, Resolution, AnyProvider, RotationMechanism, RotationState } from '@penvhq/core';
+import { InstallPlan, InstallRuntime } from './install.cjs';
 import { z } from 'zod';
 
 /**
@@ -413,53 +414,6 @@ interface DraftField extends SchemaField {
     readonly required: boolean;
 }
 
-/**
- * The runtime dependencies an adopted project takes, and how they get there.
- *
- * PRD §3: an adopted project depends on `@penvhq/penv` at the engine's own
- * version — the typed `@env` surface, not a CLI distribution. It also depends on
- * zod, because the `penv.schema.ts` init scaffolds imports it: zod is a *peer* of
- * `@penvhq/penv`, and a peer is a package the project supplies. Under pnpm's
- * strict layout nothing hoists it to the project root, so an install that named
- * only `@penvhq/penv` left the very schema init had just written unable to
- * resolve `zod` — and adoption could never finish.
- *
- * Both are installed with the package manager the project already uses, and only
- * after showing the exact `package.json` and lockfile change: an install is the
- * one step of adoption that reaches outside the repository, so it is the one step
- * that is shown before it happens rather than reported after.
- *
- * The install itself is a seam. It shells out to a package manager, which the
- * tests must never do — and a fake here is not a weaker test, because what init
- * has to get right is the plan, the consent, and the refusal when the install
- * does not happen.
- */
-
-type PackageManager = "pnpm" | "npm" | "yarn" | "bun";
-/** One package the adopted project needs, and what its `package.json` says today. */
-interface InstallPackage {
-    readonly name: string;
-    readonly version: string;
-    /** What `package.json` already says about it, when it says anything. */
-    readonly declared?: string;
-    /** True when this project already has it — nothing to install for this one. */
-    readonly satisfied: boolean;
-}
-interface InstallPlan {
-    readonly root: string;
-    readonly manager: PackageManager;
-    /** Everything an adopted project needs, in the order the diff shows them. */
-    readonly packages: readonly InstallPackage[];
-    /** The command, argv-shaped — what runs, and what a refusal tells the user to run. */
-    readonly command: readonly string[];
-    /** The lockfile the manager will rewrite, when the project has one. */
-    readonly lockfile?: string;
-    /** True when every package is already there — nothing to install. */
-    readonly satisfied: boolean;
-}
-/** Runs an install plan, or throws. Replaced in tests; never spawns there. */
-type InstallRuntime = (plan: InstallPlan) => Promise<void>;
-
 /** What init touched, so a caller can report it and a test can assert it. */
 type InitTarget = "penv-dir" | "schema" | "env" | "config" | "tsconfig" | "gitignore" | "seam";
 /**

package/dist/index.d.ts

@@ -1,5 +1,6 @@
 import * as citty from 'citty';
 import { ProjectionProvider, Provider, PenvConfig, DotenvEntry, ParameterRef, Scope, DotenvDiagnostic, Resolution, AnyProvider, RotationMechanism, RotationState } from '@penvhq/core';
+import { InstallPlan, InstallRuntime } from './install.js';
 import { z } from 'zod';
 
 /**
@@ -413,53 +414,6 @@ interface DraftField extends SchemaField {
     readonly required: boolean;
 }
 
-/**
- * The runtime dependencies an adopted project takes, and how they get there.
- *
- * PRD §3: an adopted project depends on `@penvhq/penv` at the engine's own
- * version — the typed `@env` surface, not a CLI distribution. It also depends on
- * zod, because the `penv.schema.ts` init scaffolds imports it: zod is a *peer* of
- * `@penvhq/penv`, and a peer is a package the project supplies. Under pnpm's
- * strict layout nothing hoists it to the project root, so an install that named
- * only `@penvhq/penv` left the very schema init had just written unable to
- * resolve `zod` — and adoption could never finish.
- *
- * Both are installed with the package manager the project already uses, and only
- * after showing the exact `package.json` and lockfile change: an install is the
- * one step of adoption that reaches outside the repository, so it is the one step
- * that is shown before it happens rather than reported after.
- *
- * The install itself is a seam. It shells out to a package manager, which the
- * tests must never do — and a fake here is not a weaker test, because what init
- * has to get right is the plan, the consent, and the refusal when the install
- * does not happen.
- */
-
-type PackageManager = "pnpm" | "npm" | "yarn" | "bun";
-/** One package the adopted project needs, and what its `package.json` says today. */
-interface InstallPackage {
-    readonly name: string;
-    readonly version: string;
-    /** What `package.json` already says about it, when it says anything. */
-    readonly declared?: string;
-    /** True when this project already has it — nothing to install for this one. */
-    readonly satisfied: boolean;
-}
-interface InstallPlan {
-    readonly root: string;
-    readonly manager: PackageManager;
-    /** Everything an adopted project needs, in the order the diff shows them. */
-    readonly packages: readonly InstallPackage[];
-    /** The command, argv-shaped — what runs, and what a refusal tells the user to run. */
-    readonly command: readonly string[];
-    /** The lockfile the manager will rewrite, when the project has one. */
-    readonly lockfile?: string;
-    /** True when every package is already there — nothing to install. */
-    readonly satisfied: boolean;
-}
-/** Runs an install plan, or throws. Replaced in tests; never spawns there. */
-type InstallRuntime = (plan: InstallPlan) => Promise<void>;
-
 /** What init touched, so a caller can report it and a test can assert it. */
 type InitTarget = "penv-dir" | "schema" | "env" | "config" | "tsconfig" | "gitignore" | "seam";
 /**