fix: address CodeRabbit review on the 0.17 upgrade

- Restore the pre-0.17 package names in historical CHANGELOG entries —
  release notes describe the dependencies of their own release, and the
  0.17 rename lands via the changeset, not by rewriting history.
- Drop the 'as unknown as Contract' assertion in the PSL interpretation
  test: on 0.17 the descriptor's contractJson is directly assignable to
  the interpreter's composedExtensionContracts map, so the cast (and the
  Contract import) were dead weight.
- Document the ./codec-types and ./operation-types subpaths in the
  README export table — generated contract.d.ts files import them, so
  they are public surface. No require entries added: the package (like
  the whole @prisma/orm-* 0.17 surface it plugs into) is ESM-only, and
  was before this PR.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

Author: wmadden-electric

packages/stack-prisma/CHANGELOG.md

@@ -102,7 +102,7 @@
     - Every v3 codec id registers a control-plane `expandNativeType` hook that strips the `public.` qualifier — `prisma-next migration plan` now renders `CREATE TABLE` columns as bare domain names (`eql_v3_bigint_ord`), matching what introspection reports, with **no `add_search_config` ops** (v3 domains carry their own index metadata). No `onFieldEvent` is registered for v3.
     - The v3 bundle baseline migration op is reclassified `data` (it is a contract-shape-neutral self-edge; the aggregate integrity checker rejects self-edges without a data-class op), unblocking `prisma-next migration plan` / `migrate` in consuming apps.
 
-- d6d23be: Upgrade to Prisma Next 0.14.0 (from 0.8.0). Every `@prisma/orm-*` dependency is now pinned at 0.14.0; consuming apps must run Prisma Next 0.14 to use this release.
+- d6d23be: Upgrade to Prisma Next 0.14.0 (from 0.8.0). Every `@prisma-next/*` dependency is now pinned at 0.14.0; consuming apps must run Prisma Next 0.14 to use this release.
 
   Highlights of the upgrade:
 
@@ -113,7 +113,7 @@
 
 - b7fa61f: Upgrade the Prisma Next integration to Prisma Next 0.16.
 
-  All `@prisma/orm-*` dependencies move from `0.14.0` to `0.16.0`, in lockstep. The
+  All `@prisma-next/*` dependencies move from `0.14.0` to `0.16.0`, in lockstep. The
   CipherStash encryption surface is unchanged — column types, envelopes, the `eql*`
   operators, `cipherstashFromStack`, and every subpath export behave exactly as before.
 
@@ -282,7 +282,7 @@ not a function`. The bundled `stash-prisma` skill documents this too.
 - d2772b0: Renamed `@cipherstash/prisma-next` to **`@cipherstash/stack-prisma`** (#842),
   matching the `@cipherstash/stack-drizzle` / `@cipherstash/stack-supabase`
   adapter naming. Only the npm name changes: the `prisma-next` CLI,
-  `prisma-next.config.ts`, and the `@prisma/orm-*` framework packages are the
+  `prisma-next.config.ts`, and the `@prisma-next/*` framework packages are the
   Prisma Next framework's own surface and keep their names. Update imports
   (`@cipherstash/prisma-next/stack` → `@cipherstash/stack-prisma/stack`, and the
   other subpaths likewise) and the `extensionPacks` import in
@@ -703,7 +703,7 @@ not a function`. The bundled `stash-prisma` skill documents this too.
 
 ### Minor Changes
 
-- d6d23be: Upgrade to Prisma Next 0.14.0 (from 0.8.0). Every `@prisma/orm-*` dependency is now pinned at 0.14.0; consuming apps must run Prisma Next 0.14 to use this release.
+- d6d23be: Upgrade to Prisma Next 0.14.0 (from 0.8.0). Every `@prisma-next/*` dependency is now pinned at 0.14.0; consuming apps must run Prisma Next 0.14 to use this release.
 
   Highlights of the upgrade:
 
@@ -787,7 +787,7 @@ not a function`. The bundled `stash-prisma` skill documents this too.
 
 ### Minor Changes
 
-- f2aca22: Upgrade `@prisma/orm-*` peer/runtime stack from `0.6.0-dev.8` to `0.8.0`.
+- f2aca22: Upgrade `@prisma-next/*` peer/runtime stack from `0.6.0-dev.8` to `0.8.0`.
 
   `@prisma-next/sql-runtime@0.8` reordered the SQL execution pipeline so the `beforeExecute` middleware chain fires _before_ `encodeParams`. `bulkEncryptMiddleware` now mutates params via `replaceValues(...)` ahead of encode, which means `CipherstashCellCodec.encode` is invoked with the wire-format string rather than the original `EncryptedEnvelopeBase`. The cell codec now short-circuits string values through unchanged; the envelope path is preserved for direct (non-runtime) callers such as the codec unit tests.
 

packages/stack-prisma/README.md

@@ -108,6 +108,8 @@ See the [full documentation](https://cipherstash.com/docs/stack/cipherstash/encr
 | `./runtime`      | Envelope classes + `CipherstashSdk` + v3 codec runtime + `decryptAll` + `bulkEncryptMiddlewareV3`      |
 | `./pack`         | `cipherstashPackMeta` for TS contract authoring                                                        |
 | `./column-types` | The v3 domain factories: `text` / `textSearch` / `integerOrd` / `bigIntOrd` / `date` / `boolean` / `json` / … |
+| `./codec-types`  | `CodecTypes` — the codec-id-keyed type map generated `contract.d.ts` files import                      |
+| `./operation-types` | `QueryOperationTypes` — the `eql*` operator type surface generated `contract.d.ts` files import     |
 
 `./control` and `./runtime` are tree-shakable. `./stack` sits on top of `./runtime` and additionally pulls in `@cipherstash/stack`; consumers who implement `CipherstashSdk` against a different KMS skip `./stack` and pay no `@cipherstash/stack` bundle cost.
 

packages/stack-prisma/test/psl-interpretation.test.ts

@@ -16,7 +16,6 @@
 import { interpretPslDocumentToSqlContract } from '@prisma/orm-family-sql/contract-psl'
 import type { AuthoringTypeNamespace } from '@prisma/orm-framework/components/authoring'
 import { collectScalarTypeConstructors } from '@prisma/orm-framework/components/authoring'
-import type { Contract } from '@prisma/orm-framework/contract/types'
 import { buildSymbolTable } from '@prisma/orm-framework/psl-parser'
 import { parse } from '@prisma/orm-framework/psl-parser/syntax'
 import { postgresCreateNamespace } from '@prisma/orm-target-postgres/target/types'
@@ -79,10 +78,7 @@ function interpret(schema: string) {
     ),
     composedExtensions: [cipherstashControl.id],
     composedExtensionContracts: new Map([
-      [
-        cipherstashControl.id,
-        cipherstashControl.contractSpace!.contractJson as unknown as Contract,
-      ],
+      [cipherstashControl.id, cipherstashControl.contractSpace!.contractJson],
     ]),
     authoringContributions: { type: authoringTypes, field: {} },
     createNamespace: postgresCreateNamespace,