feat: typed prisma.compute.ts compute config (#84)

## What

Adds **`prisma.compute.ts`** — a typed, committed deploy configuration
for Prisma Compute — and makes the entire `app` command surface
config-aware. One config declares the deployable system (apps, roots,
frameworks, ports, env, build settings); the CLI derives everything
else, with flags as one-shot overrides and detection filling whatever is
omitted.

```ts
import { defineComputeConfig } from "@prisma/compute-sdk/config";

export default defineComputeConfig({
  apps: {
    api: { root: "apps/api", framework: "hono", entry: "src/index.ts", httpPort: 8080 },
    web: { root: "apps/web", framework: "nextjs",
           build: { command: "npm run build", outputDirectory: ".next/standalone" } },
  },
});
```

```bash
prisma-cli app deploy          # deploys api and web, in order
prisma-cli app deploy web      # one target
cd apps/api && prisma-cli app deploy   # target inferred from cwd
```

## Design rules

- **Discovery is bounded:** nearest config from cwd up to the source
root (`.git`/workspace markers); never escapes the repository;
location-only discovery (no config evaluation) at CLI bootstrap.
- **The config directory is the project directory:**
`.prisma/local.json` pin, the state cache, and the `--db` schema scan
anchor there; config-relative paths resolve from the config file so a
committed config means the same thing from any cwd.
- **One precedence everywhere:** `--app` > `PRISMA_APP_ID` > config
target (positional `[app]` or cwd-inferred, deepest root wins) >
remembered selection > inference. `--env` flags replace config env
entirely.
- **The config never selects Project, Branch, or production** — those
stay explicit per the resource model.
- **Bare `app deploy` against a multi-app config deploys the system**
(declaration order, fail-fast with already-live/not-attempted reporting,
per-app flags rejected, `--create-project` binds once).
- **One framework detection** shared by deploy/build/run, driven by the
capability registry in `@prisma/compute-sdk/config` — adding a framework
is one registry entry plus its strategy. Covers **nextjs, nuxt, astro,
hono, tanstack-start, bun** (matching the git-push path). For nuxt/astro
the strategy owns the build, so a config `build` block is rejected
(`BUILD_SETTINGS_UNSUPPORTED`) instead of silently ignored; with a build
block and no declared framework, `app build` resolves the framework like
deploy does before applying it.

## Also in this PR

- **`prisma.app.json` removed:** never read or written. Leftovers that
match inference warn for deletion; customized ones fail with
`BUILD_SETTINGS_MIGRATION_REQUIRED` showing the exact `build` block —
builds never change silently.
- **Workspace build fixes:** package-manager detection walks up to the
workspace root; ancestor `node_modules/.bin` dirs join the build PATH;
Next.js standalone staging flattens **bun's isolated store** alongside
pnpm's.
- **`--db` is provision-only:** creates the branch database and wires
`DATABASE_URL`/`DIRECT_URL`; never runs `db push`/`migrate
deploy`/`generate`. Suggests the detected schema command plus `database
connection create <id>` (env values are write-only on the platform by
design). ⚠️ **This deliberately supersedes the schema-execution part of
#82** (`resolvePrismaInvocation`, pinned `npx prisma@<x>` fallback): the
rebase keeps #82's Next.js full-tree fallback work intact and removes
only the schema-command execution it improved, since that execution path
no longer exists.
- **Packaging:** the config contract (types, framework registry,
validation, discovery, jiti loading) is consumed from
`@prisma/compute-sdk/config` (extracted in prisma/project-compute#86,
released as 0.23.0) — single source of truth shared with the
build-runner. The CLI keeps only its concerns: flag/config precedence
merging and CliError presentation. There is no `@prisma/cli/config`
export; configs import the helper from `@prisma/compute-sdk/config`,
which the loader resolves without a local install. Publish-prep now
carries `exports` into the published manifest (was silently dropping
it).
- **CI:** new `test.yml` workflow running the CLI suite and build on
**ubuntu and windows**; new-code Windows audit done (platform-aware
separators/delimiters throughout).
- Removed the unused `c12` dependency.
- Production-gate copy fixed (`prisma` → `prisma-cli`).

## New error codes

`COMPUTE_CONFIG_INVALID`, `COMPUTE_CONFIG_TARGET_REQUIRED`,
`COMPUTE_CONFIG_TARGET_UNKNOWN`, `BUILD_SETTINGS_MIGRATION_REQUIRED`,
`BUILD_SETTINGS_UNSUPPORTED`. Retired: `APP_CONFIG_INVALID`.

## Verification

- 470 tests (≈45 new: discovery boundaries, inference, deploy-all
ordering and flag rejection, merge precedence, legacy migration
classification, workspace package-manager walk-up, publish-prep
exports).
- Live-verified end to end: single-app zero-config deploys; an
npm-workspaces monorepo (fully hoisted deps) deploying Hono and Next.js
targets; deploy/build/run/logs/show from inside target roots;
deploy-all; and a stock `bunx create-better-t-stack` scaffold (bun
workspaces + catalogs + workspace imports) deployed with a 20-line
config — which surfaced and fixed the bun-store staging bug.

## Out of scope / follow-ups

- Config scaffolding (post-deploy offer / create-prisma template) — the
biggest remaining DX gap.
- `database` as config surface (designed, deliberately deferred; spec
carries a reserved-growth-path note).
- Cross-app URL references (web needing the server's deployed URL) —
known first-contact friction.
- Spec divergence with the platform team's `compute-branching.md` stages
sketch (branch mapping in config) needs a deliberate reconciliation.

JSON output shapes changed in beta: deploy-all aggregate result,
`deploySettings.config` now `{ path: string|null, status:
"config"|"inferred" }`, `branchDatabase.schema` removed.

Author: AmanVarshney01

.github/workflows/test.yml

@@ -0,0 +1,57 @@
+name: Test
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+concurrency:
+  group: test-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os:
+          - ubuntu-latest
+          - windows-latest
+    runs-on: ${{ matrix.os }}
+    permissions:
+      contents: read
+
+    steps:
+      - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10 # v6.0.3
+        with:
+          persist-credentials: false
+
+      - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
+        with:
+          node-version: 24
+
+      - name: Enable pnpm
+        shell: bash
+        run: |
+          corepack enable
+          PNPM_VERSION="$(node -p 'const pm = require("./package.json").packageManager; const match = pm && pm.match(/^pnpm@(.+)$/); if (!match) throw new Error("packageManager must be pnpm@<version>"); match[1]')"
+          corepack prepare "pnpm@${PNPM_VERSION}" --activate
+          echo "PNPM_STORE_PATH=$(pnpm store path)" >> "$GITHUB_ENV"
+
+      - name: Cache pnpm store
+        uses: actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830 # v4.3.0
+        with:
+          path: ${{ env.PNPM_STORE_PATH }}
+          key: pnpm-store-${{ runner.os }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: |
+            pnpm-store-${{ runner.os }}-
+
+      - name: Install dependencies
+        run: pnpm install --frozen-lockfile
+
+      - name: Run CLI tests
+        run: pnpm --filter @prisma/cli test
+
+      - name: Build CLI
+        run: pnpm --filter @prisma/cli build

docs/product/command-spec.md

@@ -170,7 +170,11 @@ These codes are the minimum stable set for the MVP:
 - `LOCAL_STATE_WRITE_FAILED`
 - `LOCAL_STATE_STALE`
 - `BRANCH_NOT_DEPLOYABLE`
-- `APP_CONFIG_INVALID`
+- `COMPUTE_CONFIG_INVALID`
+- `COMPUTE_CONFIG_TARGET_REQUIRED`
+- `COMPUTE_CONFIG_TARGET_UNKNOWN`
+- `BUILD_SETTINGS_MIGRATION_REQUIRED`
+- `BUILD_SETTINGS_UNSUPPORTED`
 - `FRAMEWORK_NOT_DETECTED`
 - `DEPLOYMENT_NOT_FOUND`
 - `NO_DEPLOYMENTS`
@@ -223,7 +227,11 @@ Recommended meanings:
 - `LOCAL_STATE_WRITE_FAILED`: the CLI could not save local Project binding state such as `.prisma/local.json` or the matching `.gitignore` entry; callers should fix directory permissions or filesystem state before retrying
 - `LOCAL_STATE_STALE`: local Project pin no longer matches platform data and continuing would be ambiguous
 - `BRANCH_NOT_DEPLOYABLE`: command tried to deploy to a non-deployable branch context
-- `APP_CONFIG_INVALID`: `prisma.app.json` is missing required build settings, has invalid JSON, or points outside the app root
+- `COMPUTE_CONFIG_INVALID`: `prisma.compute.ts` failed to load or validate
+- `COMPUTE_CONFIG_TARGET_REQUIRED`: a multi-app compute config needs an `[app]` target and none was given or inferred
+- `COMPUTE_CONFIG_TARGET_UNKNOWN`: the `[app]` target matches no configured app
+- `BUILD_SETTINGS_MIGRATION_REQUIRED`: a legacy `prisma.app.json` contains custom build settings that must move into the `build` block of `prisma.compute.ts`
+- `BUILD_SETTINGS_UNSUPPORTED`: a compute config `build` block targets a framework whose strategy owns its build (nuxt, astro)
 - `FRAMEWORK_NOT_DETECTED`: app deploy could not detect a supported Beta framework and no explicit framework/build type was provided
 - `DEPLOYMENT_NOT_FOUND`: requested deployment id does not exist
 - `NO_DEPLOYMENTS`: command resolved a branch or app but found no deployments

docs/product/error-conventions.md

@@ -338,7 +338,7 @@ Examples:
 - `app deploy` should state the resolved target that matters in the current slice
 - first local `app deploy` binding should make the Project choice explicit before work begins
 - subsequent `app deploy` calls should use a compact target header such as `Deploying ./j1 to j1 / main / j1`
-- config-backed `app deploy` builds should show whether they created or used `prisma.app.json` before build starts: `Build Command` with its source when inferred, and `Output Directory` as a literal path such as `.next/standalone` rather than an opaque framework default label
+- config-backed `app deploy` builds should show the resolved build settings before build starts: `Build Command` and `Output Directory` with their sources (`prisma.compute.ts` or inference), `Output Directory` as a literal path such as `.next/standalone` rather than an opaque framework default label
 - `app logs` should state the deployment it resolved
 - `app list-deploys` should state which app or branch is being listed
 

docs/product/output-conventions.md

@@ -37,8 +37,8 @@ Rules:
 
 - `project` is not the same thing as `app`
 - Public Beta does not read or write committed config files such as `prisma.config.ts` or `.prisma/settings.json` for project resolution
-- `.prisma/local.json` is a gitignored local pin/cache for Workspace and Project IDs; it is not a declarative repo config file
-- `prisma.app.json` is a committed app build-settings file only; it must not contain Workspace, Project, Branch, App, env, or secret resolution state
+- `.prisma/local.json` is a gitignored local pin/cache for Workspace and Project IDs; it is not a declarative repo config file. When a `prisma.compute.ts` is discovered (nearest config from the invocation directory up to the repository or workspace root), the pin and the CLI state cache (`.prisma/cli/state.json`) are read and written in the config file's directory; without a config they stay in the invocation directory
+- `prisma.compute.ts` is a committed deploy-defaults file; it must not contain Workspace, Project, Branch, env-secret, or credential resolution state
 - Project setup is explicit: users choose an existing Project or explicitly create a new one before remote work starts
 - `app deploy` may orchestrate Project setup, but it must not silently choose or create Project scope
 - everything under a project happens in a branch
@@ -104,7 +104,7 @@ Rules:
 - the runtime app service is scoped by branch in the platform model
 - the app may be selected or created as part of app deployment workflows
 - app selection is local CLI state when needed for the beta package
-- app build settings may live in `prisma.app.json` beside `package.json`; v1 fields are `buildCommand` and `outputDirectory`
+- app build settings live in the `build` block of `prisma.compute.ts` (`command`, `outputDirectory`); `prisma.app.json` is legacy and no longer read
 
 ### Deployment
 
@@ -188,9 +188,9 @@ Rules:
 - first production deploy setup writes production `DATABASE_URL` and `DIRECT_URL` env vars before the App has a live deployment
 - database setup never overwrites an existing branch-scoped `DATABASE_URL`
 - production setup treats existing production `DATABASE_URL` or `DIRECT_URL` as BYO DB intent and leaves env vars unchanged
-- schema setup is sourced only from local code; the CLI does not clone or infer schema from another database
-- Prisma Next config (`prisma-next.config.*`) is preferred over `schema.prisma`
-- known non-Postgres Prisma sources are treated as unsupported for automatic Prisma Postgres setup
+- the CLI provisions the database and wires its env vars; it never runs schema, migration, or generate commands. A detected local Prisma schema source feeds only the suggested follow-up command the user runs themselves; the CLI does not clone or infer schema from another database
+- when detecting that local schema source for the suggestion, a Prisma Next config (`prisma-next.config.*`) is preferred over `schema.prisma`
+- a known non-Postgres Prisma source is treated as unsupported: it does not trigger automatic database prompting, and explicit `--db` is rejected
 - later production database configuration is managed through explicit environment-variable commands
 
 ## Relationships

docs/product/resource-model.md

@@ -12,7 +12,7 @@
     "lint": "biome check .",
     "lint:fix": "biome check . --write",
     "lint:skills": "node scripts/validate-skills.mjs",
-    "prepare": "skills add ./skills --skill '*' --agent universal claude-code -y",
+    "prepare": "node scripts/prepare-skills.mjs",
     "smoke:cli-nextjs": "node scripts/smoke-cli-nextjs-artifact.mjs",
     "test:skills": "node --test scripts/validate-skills.test.mjs",
     "test": "pnpm --filter @prisma/cli test",

package.json

@@ -6,6 +6,9 @@
   "bin": {
     "prisma-cli": "./dist/cli.js"
   },
+  "exports": {
+    "./package.json": "./package.json"
+  },
   "files": [
     "dist",
     "README.md",
@@ -41,11 +44,10 @@
   },
   "dependencies": {
     "@clack/prompts": "^1.5.0",
-    "@prisma/compute-sdk": "^0.22.0",
+    "@prisma/compute-sdk": "^0.23.0",
     "@prisma/credentials-store": "^7.8.0",
     "@prisma/management-api-sdk": "^1.37.0",
     "better-result": "^2.9.2",
-    "c12": "4.0.0-beta.5",
     "colorette": "^2.0.20",
     "commander": "^14.0.3",
     "dotenv": "^17.4.2",