Upgrade alchemy to beta.81 and use effect ^4.0.0, dropping the @effect/vitest runtime dependency

[wmadden-electric]

@prisma/composer no longer lists @effect/vitest, a test library, as a runtime dependency:

 "dependencies": {
-  "@effect/sql-d1": "4.0.0-rc.115",
-  "@effect/sql-sqlite-do": "4.0.0-rc.115",
-  "@effect/vitest": "4.0.0-rc.115",
-  "alchemy": "2.0.0-beta.78",
+  "alchemy": "2.0.0-beta.81",
-  "effect": "4.0.0-rc.115",
+  "effect": "^4.0.0",

Decision: upgrade alchemy to its latest release (2.0.0-beta.81) and declare effect with alchemy's own range, ^4.0.0. Drop every @effect/* pin that only existed to steer npm.

Why the pins existed

Until now, alchemy listed effect and several @effect/* packages as dependencies with open-ended ranges. @effect/vitest was one of them. We were on effect release candidates (4.0.0-rc.115). A caret range like ^4.0.0 doesn't match release candidates. So the only way to keep npm on a single effect was to pin effect and every companion package exactly. Composer never imported @effect/vitest, @effect/sql-d1 or @effect/sql-sqlite-do. They were listed only so a consumer's npm would pick our versions.

What changed upstream

effect 4.0.0 is out (latest is 4.0.2). From 2.0.0-beta.80, alchemy declares effect as a ^4.0.0 peer, depends on @effect/sql-* with ^4.0.0, and makes @effect/vitest an optional peer, so npm no longer installs it. With a stable effect, normal semver ranges work and the exact pins aren't needed.

What this PR does

• Upgrades alchemy from 2.0.0-beta.78 to 2.0.0-beta.81 everywhere. It stays exact because it's a beta and its API moves.
• Changes effect from 4.0.0-rc.115 to ^4.0.0 everywhere.
• Drops @effect/vitest, @effect/sql-d1, @effect/sql-sqlite-do and @effect/platform-node-shared.
• Keeps @effect/platform-node (lowering imports it) and @effect/platform-bun, both now ^4.0.0. alchemy loads the platform package for its runtime, and its CLI re-runs itself under Bun when started from Bun. Removing @effect/platform-bun made alchemy exit under bun test, so it's a real runtime dependency.
• Bumps @distilled.cloud/prisma to 1.0.0-rc.13, the exact version alchemy beta.81 depends on, so npm installs one copy.
• Code: effect 4.0 moved effect/unstable/http/* to effect/http/*. Six imports changed. No other API breakage.
• scripts/check-npm-effect-resolution.mjs no longer requires effect to be an exact version. It still checks that a bare npm install resolves exactly one effect and that alchemy resolves that same copy, and that the adversarial tree still fails.
• The deploy guide, the core-concepts skill and the upgrade-alchemy-effect skill now describe effect 4.x instead of an exact pin.

Verification

• pnpm typecheck, pnpm lint, and pnpm test (66/66 tasks) pass.
• pnpm check:npm-effect-resolution: all three healthy npm installs (including npm 10) resolve a single effect@4.0.2, and the adversarial tree fails to import alchemy as expected.
• check:family-static-graph, check:cli-engine-pin, check:publish-deps, check:skill-packaging and test:scripts pass.
• alchemy, alchemy/Output, /Provider, /Stack and /Prisma load, and a bare import('alchemy') registers no signal listeners.
• Not yet verified: the E2E deploy jobs in CI. alchemy is the deploy engine, so those are the real test of this upgrade.

Alternatives considered

• Delete only the @effect/vitest line and stay on alchemy beta.78. Rejected: beta.78 still depends on @effect/vitest with an open range. npm would pick @effect/vitest@4.0.2, which needs effect ^4.0.2, which conflicts with the rc.115 pin. That's the second-effect and npm-backtracking failure the pin was added to prevent (2026-09-11).
• Make effect a peer dependency instead of a dependency. Not done: Composer imports effect directly, and a regular dependency with alchemy's range dedupes to one copy just as well, as the npm check shows.

Agent: penelope-12

🤖 Generated with Claude Code

[prisma-gizmo]

✅ Gizmo reviewed 20dd776 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

The incremental delta updates skills/prisma-composer-core-concepts/SKILL.md:358, the core-concepts skill's description of the deploy engine. The prose "exactly-pinned npm dependency of @prisma/composer" now cites alchemy 2.0.0-beta.81 instead of 2.0.0-beta.78, keeping the documentation in sync with the dependency upgrade that is the heart of this PR.

The new version string matches the actual pin in packages/9-public/composer/package.json:37, where alchemy is declared at exactly 2.0.0-beta.81 — so the "exactly-pinned" phrasing stays accurate; alchemy remains a beta with a moving API and is deliberately not given a caret range. The adjacent sentence, "alchemy is why Composer depends on effect 4.x," also remains correct under the new ^4.0.0 range now declared in the same manifest. This line was the last documentation reference left describing the old engine version, so after this change the core-concepts skill, the deploy guide, and the upgrade-alchemy-effect skill all consistently describe alchemy beta.81 running on effect 4.x. The change is documentation-only with no runtime or packaging effect; the operational guidance around it (generated stack files, bisection via the alchemy CLI, destroy semantics, public-URL rules) is untouched and still matches the code paths it describes.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 260a644c-3060-4b23-a924-faa1b732fd23

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

_{Comment @coderabbitai help to get the list of available commands.}

[pkg-pr-new]

Open in StackBlitz

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

npm i https://pkg.pr.new/@prisma/composer-cli@348

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

commit: 20dd776

[prisma-gizmo]

New findings: 🟡 1 minor · trace

Findings outside the diff

• 🟡 Minor · consistency skills/prisma-composer-core-concepts/SKILL.md — Core-concepts skill still cites alchemy 2.0.0-beta.78
  The PR updates every other alchemy version citation in the repo (glossary, deploy guide, both skills) to 2.0.0-beta.81, but the engine-overview paragraph in the core-concepts skill still reads "an ordinary, exactly-pinned npm dependency of @prisma/composer (2.0.0-beta.78 at this library version)". A reader cross-checking this line against the manifests sees a version that no longer matches. The "exactly-pinned" claim itself is still accurate; only the version in parentheses is stale. The stale sentence sits on line 358, outside this PR's diffed hunks in the file, so it is recorded here without a line anchor.
  Recommended fix: Update the parenthetical to (2.0.0-beta.81 at this library version).

[prisma-gizmo]

No critical or major Gizmo finding is open and the head commit has been reviewed. Approving.

[prisma-gizmo]

New findings: none · trace

[prisma-gizmo]

No critical or major Gizmo finding is open and the head commit has been reviewed. Approving.