@prisma/orm-toolchain 8.0.0-rc.4-dev.13 → 8.0.0-rc.4-dev.14

package/dist/cli.mjs

@@ -33,12 +33,12 @@ import { applyEdits, modify, parse, printParseErrorCode } from "jsonc-parser";
 import stringWidth from "string-width";
 import { bold, createColors, cyan, cyanBright, dim, green, yellow } from "colorette";
 import { build } from "esbuild";
-//#region ../../../1-framework/3-tooling/cli/dist/load-config-ChYX98p-.mjs
-var version = "8.0.0-rc.4-dev.13";
+//#region ../../../1-framework/3-tooling/cli/dist/load-config-D8DBODld.mjs
+var version = "8.0.0-rc.4-dev.14";
 const MISSING_CONFIG_ACTION = {
 	kind: "run-command",
 	label: "Create a config file",
-	command: "prisma-cli init"
+	command: "prisma orm init"
 };
 function editConfigAction(field) {
 	return {
@@ -2527,8 +2527,8 @@ const formatCommand = createFormatCommand();
 *
 * - We only inspect the unnamed top-level `catalog:` block. pnpm also
 *   supports `catalogs:` (plural — *named* catalogs referenced via
-*   `catalog:foo` specifiers); those don't apply to a vanilla
-*   `pnpm add prisma-next` invocation, so we skip them.
+*   `catalog:foo` specifiers); those don't apply to the vanilla
+*   `pnpm add` invocations `init` runs, so we skip them.
 * - We don't validate YAML syntax exhaustively. The file format pnpm
 *   ships is line-oriented and well-known; a minimal regex is more
 *   robust than depending on a YAML parser for one warning.
@@ -2643,7 +2643,7 @@ function errorInitMissingFlags(options) {
 	}).join(" ");
 	return new CliStructuredError$1$1("CLI.INIT_MISSING_FLAGS", "Missing required flags", {
 		why: `${options.why} Missing required flag(s): ${flagList}.`,
-		fix: `Re-run with the missing flag(s) supplied, e.g. \`prisma-cli init --yes ${fixList}\`. Use \`prisma-cli init --help\` to see every flag.`,
+		fix: `Re-run with the missing flag(s) supplied, e.g. \`prisma orm init --yes ${fixList}\`. Use \`prisma orm init --help\` to see every flag.`,
 		docsUrl: docsUrlFor("CLI.INIT_MISSING_FLAGS"),
 		meta: { missingFlags: options.missing }
 	});
@@ -2685,15 +2685,13 @@ function errorInitAuthoringSchemaPathMismatch(options) {
 }
 /**
 * The user cancelled an interactive prompt (Ctrl-C, escape, declined a
-* selection). Distinct from `errorInitReinitNeedsForce` because that path
-* applies to non-interactive mode where the user was never given the
-* choice; this one is the generic "user said no" path. Maps to exit code
+* selection) — the generic "user said no" path. Maps to exit code
 * 3 (USER_ABORTED).
 */
 function errorInitUserAborted() {
 	return new CliStructuredError$1$1("CLI.INIT_USER_ABORTED", "Init cancelled", {
 		why: "The interactive prompt was cancelled before all required inputs were supplied. No files were modified.",
-		fix: "Re-run `prisma-cli init` and complete the prompts, or pass the required inputs as flags (see `--help`) for a non-interactive run.",
+		fix: "Re-run `prisma orm init` and complete the prompts, or pass the required inputs as flags (see `--help`) for a non-interactive run.",
 		severity: "info"
 	});
 }
@@ -2726,7 +2724,7 @@ function errorInitStrictProbeWithoutProbe() {
 function errorInitInvalidManifest(options) {
 	return new CliStructuredError$1$1("CLI.INIT_INVALID_MANIFEST", `Failed to parse ${options.path}`, {
 		why: `\`${options.path}\` is not valid JSON: ${options.cause}`,
-		fix: `Fix the JSON syntax in \`${options.path}\` (a missing comma or unbalanced brace is the most common cause), then re-run \`prisma-cli init\`.`,
+		fix: `Fix the JSON syntax in \`${options.path}\` (a missing comma or unbalanced brace is the most common cause), then re-run \`prisma orm init\`.`,
 		docsUrl: docsUrlFor("CLI.INIT_INVALID_MANIFEST"),
 		meta: {
 			path: options.path,
@@ -2751,7 +2749,7 @@ function errorInitInvalidManifest(options) {
 function errorInitInvalidTsconfig(options) {
 	return new CliStructuredError$1$1("CLI.INIT_INVALID_TSCONFIG", `Failed to parse ${options.path}`, {
 		why: `\`${options.path}\` is not valid JSON or JSONC: ${options.cause}`,
-		fix: `Fix the syntax in \`${options.path}\` and re-run \`prisma-cli init\`. \`init\` accepts JSONC (comments and trailing commas) but cannot recover from unbalanced braces or missing commas.`,
+		fix: `Fix the syntax in \`${options.path}\` and re-run \`prisma orm init\`. \`init\` accepts JSONC (comments and trailing commas) but cannot recover from unbalanced braces or missing commas.`,
 		docsUrl: docsUrlFor("CLI.INIT_INVALID_TSCONFIG"),
 		meta: {
 			path: options.path,
@@ -2795,7 +2793,7 @@ function errorInitProbeFailed(options) {
 function errorInitWriteFailed(options) {
 	return new CliStructuredError$1$1("CLI.INIT_WRITE_FAILED", `Failed to write ${options.path}`, {
 		why: `\`${options.path}\` could not be written: ${options.cause}`,
-		fix: "Fix what stopped the write — a directory sitting where the file goes, permissions, a full disk — then run `prisma-cli init` again. It will ask you to confirm replacing the files this run already wrote (listed in `meta.filesWritten`).",
+		fix: "Fix what stopped the write — a directory sitting where the file goes, permissions, a full disk — then run `prisma orm init` again. Interactive runs ask before replacing the files this run already wrote (listed in `meta.filesWritten`); non-interactive runs grant that consent with `--confirm <directory name>`.",
 		docsUrl: docsUrlFor("CLI.INIT_WRITE_FAILED"),
 		meta: {
 			path: options.path,
@@ -2839,7 +2837,7 @@ async function probeServerVersion(ctx, overrides = {}) {
 			minVersion,
 			meetsMinimum: null,
 			cause: err.message,
-			message: `Skipped --probe-db: ${err.message}. (Run with install enabled, or install the driver yourself, then re-run \`prisma-cli init --probe-db\`.)`
+			message: `Skipped --probe-db: ${err.message}. (Run with install enabled, or install the driver yourself, then re-run \`prisma orm init --probe-db\`.)`
 		};
 		const cause = redactDatabaseUrlSecrets(causeMessage$2(err));
 		return {
@@ -3004,7 +3002,7 @@ const DEFAULT_SKILL_SOURCES = [
 * `#ref` fragment is dropped — local-path mode in upstream's CLI does
 * not accept refs, and the local clone has whatever content the test
 * checked into it anyway. When set to anything else (e.g. a fork name
-* `myuser/prisma-next`), the ref policy is preserved.
+* `myuser/prisma`), the ref policy is preserved.
 */
 function resolveAgentSkillBase(env) {
 	const override = env["PRISMA_NEXT_SKILLS_BASE"]?.trim();
@@ -3126,10 +3124,13 @@ const AGENT_SKILL_ROOTS = [
 /**
 * Every directory a retired per-workflow skill may occupy in a
 * consumer project. Init deletes each (recursively) before running the
-* skill install.
+* skill install. Names that are also in `DEFAULT_SKILL_SOURCES` are
+* excluded so a list mistake can never delete a skill init installs
+* (or one `--skip-skills` preserves) — see TML-2637.
 */
-function legacySkillDirs() {
-	return AGENT_SKILL_ROOTS.flatMap((root) => RETIRED_SKILL_NAMES.map((name) => `${root}/${name}`));
+function legacySkillDirs(retired = RETIRED_SKILL_NAMES, sources = DEFAULT_SKILL_SOURCES) {
+	const installed = new Set(sources.map((source) => source.skill));
+	return AGENT_SKILL_ROOTS.flatMap((root) => retired.filter((name) => !installed.has(name)).map((name) => `${root}/${name}`));
 }
 /**
 * The resolver a scaffold for `target` is written against.
@@ -4153,7 +4154,7 @@ function requirementsBlock(target) {
 		"## Requirements",
 		"",
 		`- **${TARGET_LABEL[target]} ${MIN_SERVER_VERSION[target]} or newer.** Older servers are not supported. Run ${target === "postgres" ? "`SELECT version()`" : "`db.runCommand({ buildInfo: 1 })`"} against your server to verify.`,
-		"- The CLI never connects to your database without explicit consent. Pass `--probe-db` to `prisma-cli init` if you want `init` to verify the server version itself."
+		"- The CLI never connects to your database without explicit consent. Pass `--probe-db` to `prisma orm init` if you want `init` to verify the server version itself."
 	].join("\n");
 }
 const sharedVariables = [