feat!: rename framework Prisma Compose → Prisma Composer

[wmadden-electric]

Renames the framework Prisma Compose → Prisma Composer across the whole surface. One atomic mechanical rename; pre-GA.

What moved

• Packages: @prisma/compose* → @prisma/composer* (dirs packages/9-public/composer + composer-prisma-cloud, bin: prisma-composer, the cloud package's dep on @prisma/composer).
• Config file: prisma-compose.config.ts → prisma-composer.config.ts (6 files, git mv).
• Scratch dir .prisma-compose/ → .prisma-composer/; workspace root prisma-compose-ws → prisma-composer-ws.
• Docs: proper-noun and product-noun "Compose" → "Composer" across living docs. agent-os/product/naming.md's rationale section is rewritten (not just token-swapped) so it correctly states Composer reduces the Compute collision instead of accepting it.

Why

"Compose" collides audibly with the Compute product (two syllables, same stress, one vowel apart) and reads as a bare imperative verb where a tool wants an agent noun. "Composer" separates from Compute (third syllable, distinct stressed vowel) and joins the compiler/bundler/linter family, while the verb compose, the property composability, and composition keep the shared root. Accepted trade-off, eyes open: an external same-category name-share with AWS Infrastructure/Application Composer, always vendor-prefixed. Full reasoning in agent-os/product/naming.md. No ADR (operator decision).

Deliberately NOT changed

• The verb compose, plus composability, composition, docker-compose, Jetpack Compose.
• Historical ADR-0026 / ADR-0027 — they record the earlier App→Compose decision and stay as the historical record.
• The COMPOSE_ deploy-time env-var prefix — that's a wire-format/behavior change, tracked as a separate follow-up PR.

Verification

• pnpm build 24/24 · pnpm typecheck 50/50 · pnpm test 41/41 · pnpm lint (biome) clean · lint:deps / framework-vocabulary / lint:rules:symlinks / lint:casts all green.
• Word-boundary completeness grep returns only the two excluded ADRs.
• Independent review pass (separate agent): no over-replacement of the verb, git mv preserved history, exclusions honored, .agents/rules/*.mdc correctly rewritten.

npm cutover

Old @prisma/compose* were already unpublished; @prisma/composer* are free. Publish is manual, after merge, with pnpm build then pnpm --filter @prisma/composer publish … (pnpm, not npm — the cloud package's workspace: dep needs rewriting), the core package first.

Coordinating with open PRs

• docs: names reference — how Compose and Module were chosen #67 ("names reference — how Compose was chosen") documents a now-dead name → needs reword + rebase to Composer.
• Dependabot chore(deps)(deps): Bump the runtime-deps group across 1 directory with 2 updates #73 / chore(deps-dev)(deps-dev): Bump the dev-deps group across 1 directory with 3 updates #74 / chore(deps)(deps): Bump @effect/platform-bun from 4.0.0-beta.92 to 4.0.0-beta.93 #65 / chore(deps)(deps): Bump effect from 4.0.0-beta.92 to 4.0.0-beta.93 #66 touch package.json + lockfiles → will conflict on this diff; simplest to let them rebound after merge.
• docs(drive): datahub-port close-out — plan status + slice spec #47, refactor(storage): drop the service.mjs naming workaround (#71 handles it) #77 rebase after.

🤖 Generated with Claude Code

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/prisma/composer/@prisma/composer@80

npm i https://pkg.pr.new/prisma/composer/@prisma/composer-prisma-cloud@80

commit: 01e9520