refactor: consolidate and reorganize packages per ADR-0026/0027/0028

[wmadden-electric]

Implements the package rename, consolidation, and reorganization designed in ADR-0026, ADR-0027, and ADR-0028. Carries #59's ADR-0027/0028 docs (cherry-picked; this PR subsumes #59).

The workspace shape (ADR-0028)

packages/
  0-framework/
    0-foundation/   @internal/foundation (casts, assertions), @internal/tsdown-config
    1-core/         @internal/core (module(), graph, config params, deploy)
    2-authoring/    @internal/rpc, @internal/node, @internal/nextjs
    3-tooling/      @internal/assemble, @internal/cli
  1-prisma-cloud/
    0-lowering/     @internal/lowering (the Alchemy provider, ex @prisma/alchemy)
    1-extensions/   @internal/prisma-cloud (compute(), postgres(), target descriptor)
    2-modules/      @internal/cron
  9-public/
    compose/              → @prisma/compose
    compose-prisma-cloud/ → @prisma/compose-prisma-cloud

All internals are @internal/* + "private": true. Exactly two publishable packages, verified by the publish gate (check:publish-deps finds exactly 2) and npm pack --dry-run on each (no @internal/* in any published dependency field or dist import).

Public surface (ADR-0027)

• @prisma/compose: prisma-compose bin, core at root, subpaths ./config ./deploy ./testing ./casts ./assertions ./rpc ./node(/control) ./nextjs(/control). Internals inlined at build (tsdown noExternal on the @internal scope).
• @prisma/compose-prisma-cloud: target at root + ./control ./prisma-next ./testing ./cron(/scheduler-entrypoint). Cloud internals inlined; framework imports rewritten to @prisma/compose subpaths and left external (resolve hook + post-build dts rewrite) so one framework copy exists at runtime and type identity holds — core's node brand is a unique symbol; two bundled declaration copies would not unify (found empirically: the storefront example failed to typecheck against a bundled-framework cloud package).
• No unscoped wrapper — packages/prisma-compose deleted.
• Extension routing ids follow the public identities: @prisma/compose/node, @prisma/compose/nextjs, @prisma/compose-prisma-cloud.

Enforcement (ADR-0028)

architecture.config.json (globs → {domain, layer, plane}) + dependency-cruiser.config.mjs copied from prisma-next's shape. Downward-only across domains and layers; lateral allowed; 9-public is a sink; examples + integration tests import only 9-public; control/execution planes never import each other (ADR-0017), mapped per-entrypoint. Wired as pnpm lint:deps, in CI, and in lint-staged. Currently: ✔ no dependency violations (180 modules, 308 dependencies).

Judgment calls

• CLI stays in 0-framework/3-tooling with one declared cross-domain exception (cli → @internal/lowering): the pre-stack container-ensure step (Project/Branch resolution) is Prisma Cloud-specific today. Known debt, documented in the config's exception entry, rather than moving the CLI into the cloud domain (ADR-0027 puts the bin in @prisma/compose).
• serializer.ts classified shared, not control — the cruiser corrected the initial guess: the authoring surface (index/compute/testing) imports it.
• Internals keep their own dist builds; publics bundle from prebuilt dist + .d.mts. Building publics straight from cross-package TS sources broke rolldown-plugin-dts three different ways (anonymous default re-exports, Effect-heavy files failing isolated-declaration emit, eager segfaulting).
• @prisma/compose public exports keep ./config ./deploy ./testing ./casts ./assertions beyond ADR-0027's enumerated ./rpc ./node ./nextjs — examples and user configs (prisma-compose.config.ts imports defineConfig from @prisma/compose/config) need them.
• Core's exports-map invariant updated (casts/assertions now live in @internal/foundation); cloud's updated for cron's move.
• Artifact-sense "Prisma App" keeps (ADR-0023 and friends) — unchanged from refactor: rename to Prisma Compose across packages, CLI, and docs per ADR-0026 #57; both acceptance greps return only ADR-0023's filename, ADR-0026/0027's rename record, and the repo URL. grep "Prisma App Framework" → zero.
• bun.lock regenerated — bun doesn't resolve the nested workspace globs, so it now tracks the root only; nothing in CI uses it.
• Versions restart at 0.1.0 lockstep (old names unpublished 2026-07-12; new names never published). Not published — that's the release process's job.

Acceptance

• pnpm build (17) / typecheck (36) / test (29) / test:types (20) / lint / lint:deps — all green.
• Examples (incl. cron) build and test importing only @prisma/compose / @prisma/compose-prisma-cloud (+ subpaths) — enforced by the cruiser from now on.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/prisma/app/@prisma/compose@60

npm i https://pkg.pr.new/prisma/app/@prisma/compose-prisma-cloud@60

commit: 27f79f0