feat(cli): add JSON compute config format to init

init gains --format <ts|json>. The json format writes a dependency-free
prisma.compute.json through the SDK's serializeComputeConfigJson with a
$schema-first document, pins the same resolved values as the TypeScript
path, and keeps the wx no-overwrite semantics. Because the format exists
to be dependency-free, the types install step never runs with it and
--install becomes a usage error; the custom framework is refused since
strict JSON cannot carry the commented build stub init relies on.

An explicit --format ts with an existing prisma.compute.json is the
graduation path: the JSON config is validated, rewritten as
prisma.compute.ts wrapping the same object in defineComputeConfig, the
JSON file is deleted in the same operation, and the types install step
runs. The reverse direction fails with INIT_CONVERT_UNSUPPORTED because
TypeScript configs may contain logic a static file cannot express.
Plain init still refuses every existing config with INIT_CONFIG_EXISTS.

The result envelope now reports format and converted alongside
configPath.

The product decision asked for a --json boolean; that name is the
global JSON-output flag on every command, so the config format rides a
dedicated --format option instead.

Author: AmanVarshney01

docs/product/command-spec.md

@@ -384,17 +384,22 @@ prisma-cli --version --json
 
 `prisma-cli version` is the richer environment report; `prisma-cli --version` is the terse one-liner. Both report the same `cli.version`. Use the flag for quick checks, the subcommand for support tickets and bug reports.
 
-## `prisma-cli init --framework <nextjs|nuxt|astro|hono|nestjs|tanstack-start|bun|custom> --entry <path> --http-port <port> --region <region> --name <app-name> --link --no-link --project <id-or-name> --install --no-install`
+## `prisma-cli init --framework <nextjs|nuxt|astro|hono|nestjs|tanstack-start|bun|custom> --entry <path> --http-port <port> --region <region> --name <app-name> --link --no-link --project <id-or-name> --install --no-install --format <ts|json>`
 
 Purpose:
 
-- write a committed `prisma.compute.ts` for the app in this directory
+- write a committed `prisma.compute.ts` (or, with `--format json`, a dependency-free `prisma.compute.json`) for the app in this directory
 
 Behavior:
 
 - init is the config formalizer: `app deploy` works with zero config, and init writes down what deploy would infer so the setup is committed, reviewable, and stable for teammates and CI
 - writing the config requires no auth and no network; linking is the only remote step
 - fails with `INIT_CONFIG_EXISTS` when a compute config already exists in the invocation directory or any ancestor up to the repository or workspace root; the error names the existing file, and init never overwrites or merges — editing a committed config is the user's editor's job
+- `--format <ts|json>` selects the config serialization; `ts` (alias `typescript`) is the default and writes `prisma.compute.ts`, `json` writes `prisma.compute.json` via the shared SDK serializer with a `$schema`-first document that validates in editors without any local dependency; both formats pin exactly the same resolved values, and the CLI's global `--json` output flag is unrelated to the config format
+- with `--format json`, the types install step never runs: the JSON format exists to be dependency-free, so `--install` is a usage error and the result reports the step as skipped with no install hint
+- with `--format json` and the custom framework, init fails with a usage error: custom needs `build.outputDirectory` and `build.entrypoint`, which init does not collect, and strict JSON cannot carry the commented build stub the TypeScript format uses; the fix is the TypeScript format or a hand-written `build` object
+- graduation path: an explicit `--format ts` with an existing `prisma.compute.json` converts it in place; the JSON config is loaded and validated, the equivalent `prisma.compute.ts` wrapping the same object in `defineComputeConfig` is written next to it, the JSON file is deleted in the same operation, and the types install step runs as usual (skippable with `--no-install`); values are transported, never re-resolved, and the conversion is reported with `converted: true`
+- conversion is one-way and explicit: plain `init` with any existing config still fails with `INIT_CONFIG_EXISTS`, and `--format json` with an existing TypeScript config fails with `INIT_CONVERT_UNSUPPORTED` because TypeScript configs may contain logic that a static JSON file cannot express; a fully static config can be rewritten by hand
 - detects the framework from the same registry and signals `app deploy` uses; explicit `--framework` wins over detection
 - `--entry` sets the source entrypoint for entrypoint frameworks (Bun, Hono); `--http-port` overrides the framework default port; `--name` overrides the app name inferred from `package.json#name` or the directory name
 - previews the resolved values with per-value source annotations (`detected`, `framework default`, `package.json`, `flag`) before writing; in interactive mode the preview is followed by an optional adjust step for framework and HTTP port, and `--yes` accepts the preview as shown
@@ -415,7 +420,7 @@ Behavior:
   - link failures and cancellations after the config is written downgrade to warnings and `nextSteps`; the config write stands and init exits 0
 - `nextSteps` includes the deploy command, plus the project link command when the directory is still unlinked
 - user-facing command hints in init output (next steps, link hints, error recovery commands) use the package runner detected from the project, such as `pnpm dlx @prisma/cli@latest project link` or `npx -y @prisma/cli@latest app deploy`, matching the `agent` group's convention
-- in `--json`, `result` includes `configPath`, the written `app` values, per-value `settings` sources, and `link` state; `--json` never prompts
+- in `--json`, `result` includes `configPath`, `format` (`typescript` or `json`), `converted` (true only for the `--format ts` conversion path), the written `app` values (null when a conversion transported a config that does not pin a single fully-resolved app), per-value `settings` sources, and `link` state; `--json` never prompts
 
 Examples:
 
@@ -424,6 +429,8 @@ prisma-cli init
 prisma-cli init --framework hono --entry src/index.ts
 prisma-cli init --name api --http-port 8080 --no-link
 prisma-cli init --project proj_123
+prisma-cli init --format json
+prisma-cli init --format ts
 prisma-cli init --json
 ```
 

docs/product/error-conventions.md

@@ -188,6 +188,7 @@ These codes are the minimum stable set for the MVP:
 - `BUILD_SETTINGS_UNSUPPORTED`
 - `FRAMEWORK_NOT_DETECTED`
 - `INIT_CONFIG_EXISTS`
+- `INIT_CONVERT_UNSUPPORTED`
 - `INIT_DETECTION_FAILED`
 - `DEPLOYMENT_NOT_FOUND`
 - `NO_DEPLOYMENTS`
@@ -261,6 +262,7 @@ Recommended meanings:
 - `BUILD_SETTINGS_UNSUPPORTED`: a compute config `build` block targets a framework whose SDK strategy does not consume committed build settings
 - `FRAMEWORK_NOT_DETECTED`: app deploy could not detect a supported Beta framework and no explicit framework/build type was provided
 - `INIT_CONFIG_EXISTS`: a compute config already exists in this directory or an ancestor; init never overwrites or merges
+- `INIT_CONVERT_UNSUPPORTED`: `init --format json` found an existing TypeScript config; TypeScript configs may contain logic, so converting them to JSON automatically would be lossy and the rewrite is manual
 - `INIT_DETECTION_FAILED`: no supported framework detected and no --framework passed; `meta.frameworks` lists the valid values
 - `DEPLOYMENT_NOT_FOUND`: requested deployment id does not exist
 - `NO_DEPLOYMENTS`: command resolved a branch or app but found no deployments

packages/cli/src/commands/init/index.ts

@@ -43,7 +43,13 @@ export function createInitCommand(runtime: CliRuntime): Command {
     .addOption(
       new Option("--install", "Install @prisma/compute-sdk for config types"),
     )
-    .addOption(new Option("--no-install", "Skip the types install step"));
+    .addOption(new Option("--no-install", "Skip the types install step"))
+    .addOption(
+      new Option(
+        "--format <ts|json>",
+        "Config file format: ts (default) writes prisma.compute.ts, json writes dependency-free prisma.compute.json; --format ts converts an existing prisma.compute.json",
+      ),
+    );
   addGlobalFlags(command);
 
   command.action(async (options) => {
@@ -56,6 +62,7 @@ export function createInitCommand(runtime: CliRuntime): Command {
       link?: boolean;
       project?: string;
       install?: boolean;
+      format?: string;
     };
 
     await runCommand<InitResult>(
@@ -72,6 +79,7 @@ export function createInitCommand(runtime: CliRuntime): Command {
           link: flags.link,
           project: flags.project,
           install: flags.install,
+          format: flags.format,
         }),
       {
         renderHuman: (context, descriptor, result) =>