Port prisma functional wave 2: mongo composites, relationMode matrices, issue regressions (229 accounted)

Second porting wave for the port-all-tests project, +229 checklist boxes accounted (488 → 717).

Ported & passing:
- mongo composites/list + composites/object (withMongoPort): create/createMany/delete/deleteMany/findFirst/findMany/update/upsert
- relationMode foreignKeys referential-action matrices: 1-to-1, 1-to-n, m-to-n (Cascade/NoAction/Restrict/SetNull; @Map + nomap), plus 17255 same/mixed-action disconnect
- issue regressions: 5952 decimal, 14954 date, 21631 batching-in-tx (Promise.all forms), 29174 jsonb, 13089 dollar-in-search (mongo)

Ported & failing (test.fails, faithful gap):
- 29267 Uint8Array-in-JSON serialization; required-composite null; implicit default onUpdate (NoAction vs Prisma Cascade)
- relation-mode-gh-m-to-n @Map variants: prisma-next rejects the mapped join-table auto-index name (>54-char prefix limit, #1047); Prisma truncates/hashes. Tracked as it.fails that flips green when fixed.

Non-portable (recorded per-test in non-ported/):
- relationLoadStrategy, relationMode=prisma emulation, implicit embedded mongo m2m, array-batch $transaction([...]), embedded-subfield select / composite where operators / read-side aggregate+count in mongo ORM

Built against current main: fixtures emitted with the new indexes[].unique contract shape (#1047); count-only ORM terminals renamed to createAndCount/updateAndCount/deleteAndCount (#1044).

Corpus: 69 files, 476 passed | 52 expected-fail, typecheck + lint clean. failing.md matches the test.fails markers; non-ported ledgers mirror functional/<suite>/. All dispositions reviewer-gated.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Signed-off-by: Serhii Tatarintsev <tatarintsev@prisma.io>

Author: SevInf

projects/port-all-tests/briefs/implementer.md

@@ -45,7 +45,7 @@ A faithful port reproduces the SAME upstream test: same schema, logically the sa
 ## Per-suite recipe
 1. Read the source `_matrix.ts`, `prisma/_schema.ts`, `tests.ts`. Determine provider applicability; port the **postgres** matrix entry. A suite exclusive to an unsupported DB (mysql/sqlserver/cockroachdb/sqlite) → `non-ported` lines (one per test). A **MongoDB**-applicable suite ports against the mongo ORM (`withMongoPort`) — do NOT mark mongo tests non-ported for being mongo.
 2. Each suite is its OWN directory `test/integration/test/ports/prisma/functional/<suite>/` holding both the test and its co-located fixture. Author the fixture as **PSL** (not TS builders): `prisma/functional/<suite>/_fixture/contract.prisma` — a faithful translation of the upstream `prisma/_schema.ts` (postgres branch). **The DB schema MUST match the original test exactly**: every model, field, scalar + native type (`@db.*`), nullability, list-ness, `@id`/`@@id`, `@unique`/`@@unique`, `@default`, `@map`/`@@map`, `@relation` (fields/references/onDelete/onUpdate), `@@index`, and enums. Do NOT drop or weaken any field/type/constraint/relation to dodge a prisma-next gap — if the faithful schema can't be authored or pushed, the affected tests are `non-ported`/`it.fails`, not a green on a simplified schema. Add `prisma/functional/<suite>/_fixture/prisma-next.config.ts`:
-   `import { defineConfig } from '@prisma-next/postgres/config'; export default defineConfig({ contract: './contract.prisma', outputPath: 'generated' });`
+   `import { defineConfig } from '@prisma-next/postgres/config'; export default defineConfig({ contract: './contract.prisma', output: 'generated' });`
    (mongo: `@prisma-next/mongo/config`, mongodb-provider PSL.) Emit:
    `node packages/1-framework/3-tooling/cli/dist/cli.js contract emit --config test/integration/test/ports/prisma/functional/<suite>/_fixture/prisma-next.config.ts`
    Commit the generated `contract.json` + `contract.d.ts` (leave them on disk). If a suite genuinely needs several schemas (e.g. a mapTable matrix), nest them under `_fixture/<variant>/`; if two suites truly share one schema, duplicate the `_fixture/` into each suite's directory so every suite stays self-contained.

projects/port-all-tests/checklists/prisma-functional-0-l.md

@@ -38,3 +38,26 @@ Every entry here corresponds one-to-one with a `test.fails` marker in the corpus
 - `test/ports/prisma/functional/multi-schema/multi-schema.test.ts` › `ports/prisma/functional/multi-schema (mapTable=IDENTICAL_NAMES)` › `multischema: update` — same gap as `read`: `posts.some()` with identical cross-namespace table names returns 0 rows in the read-back step; ORM emits an unqualified table name in the relation-filter subquery, which is ambiguous across the two namespaces
 - `test/ports/prisma/functional/methods-createManyAndReturn/methods-createManyAndReturn.test.ts` › `include _count should fail` — createManyAndReturn rejects `include: { _count: true }` — prisma-next type-rejects `include('_count')` (inline `@ts-expect-error` holds) but ignores the unknown relation at runtime instead of throwing, so the `.rejects.toThrow()` assertion fails
 - `test/ports/prisma/functional/methods-updateManyAndReturn/methods-updateManyAndReturn.test.ts` › `include _count should fail` — updateManyAndReturn rejects `include: { _count: true }` — prisma-next type-rejects `include('_count')` (inline `@ts-expect-error` holds) but ignores the unknown relation at runtime instead of throwing, so the `.rejects.toThrow()` assertion fails
+- `test/integration/test/ports/prisma/functional/composites-object-createMany/composites-object-createMany.test.ts` › `required content` › `set null` — createMany with null on a required embedded `content` field — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-object-createMany/composites-object-createMany.test.ts` › `required content` › `set null shorthand` — same as `set null` for the required variant — type-rejected but no runtime throw
+- `test/integration/test/ports/prisma/functional/composites-object-upsert-create/composites-object-upsert-create.test.ts` › `required content` › `set null` — upsert (create path) with null on a required embedded `content` field — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-object-upsert-create/composites-object-upsert-create.test.ts` › `required content` › `set null shorthand` — same as `set null` for the required variant — type-rejected but no runtime throw
+- `test/integration/test/ports/prisma/functional/composites-list-create/composites-list-create.test.ts` › `set null` — create with null on a required embedded `contents` list — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-list-create/composites-list-create.test.ts` › `set null shorthand` — same as `set null` for the required list — type-rejected but no runtime throw
+- `test/integration/test/ports/prisma/functional/composites-list-createMany/composites-list-createMany.test.ts` › `set null` — createMany with null on a required embedded `contents` list — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-list-createMany/composites-list-createMany.test.ts` › `set null shorthand` — same as `set null` for the required list — type-rejected but no runtime throw
+- `test/integration/test/ports/prisma/functional/composites-list-update/composites-list-update.test.ts` › `set null` — update with null on a required embedded `contents` list — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-list-update/composites-list-update.test.ts` › `set null shorthand` — same as `set null` for the required list — type-rejected but no runtime throw
+- `test/integration/test/ports/prisma/functional/composites-list-upsert-create/composites-list-upsert-create.test.ts` › `set null` — upsert (create path) with null on a required embedded `contents` list — type-rejects it (inline `@ts-expect-error` holds) but mongo has no runtime validation, so it does not throw (Prisma throws "Argument `set` must not be null")
+- `test/integration/test/ports/prisma/functional/composites-list-upsert-create/composites-list-upsert-create.test.ts` › `set null shorthand` — same as `set null` for the required list — type-rejected but no runtime throw
+- `test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts` › `serializes Uint8Array nested in object as base64` — prisma-next's JSON codec (`packages/3-extensions/arktype-json/src/core/arktype-json-codec.ts`, `serializeWire = JSON.stringify`) serialises a `Uint8Array` to an index-keyed object (`{"0":72,...}`), not base64; no Uint8Array→base64 hook
+- `test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts` › `serializes Uint8Array nested in array as base64` — same gap: JSON codec `JSON.stringify` renders a `Uint8Array` as an index-keyed object, not base64
+- `test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts` › `serializes Uint8Array directly as base64` — same gap: JSON codec `JSON.stringify` renders a `Uint8Array` as an index-keyed object, not base64
+- `test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts` › `serializes deeply nested Uint8Array as base64` — same gap: JSON codec `JSON.stringify` renders a `Uint8Array` as an index-keyed object, not base64
+
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/update.test.ts` › `onUpdate DEFAULT/SetNull (map=false) › [update] post id` — updating a referenced parent post id under the DEFAULT/SetNull m:n schema — prisma-next's implicit default `onUpdate` (no action line) is NO ACTION, so the FK-referenced parent-id update throws instead of cascading (Prisma's implicit default for a required relation is Cascade).
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/update.test.ts` › `onUpdate DEFAULT/SetNull (map=false) › [update] category id` — same gap, category side.
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/emit-map.test.ts` › `[emit @map] (index-name-length gap) › default-map › emitting the faithful @map contract succeeds` — emitting the DEFAULT/SetNull @map m:n schema — prisma-next #1047 rejects the mapped m:n join-table auto-index name `CategoriesOnPostsManyToMany_AtAtMap_categoryId_AtMap_idx` (>54-char prefix limit); the faithful @map schema is not emittable. Prisma truncates/hashes long index names. Blocks the m-to-n @map matrix variants.
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/emit-map.test.ts` › `[emit @map] (index-name-length gap) › cascade-map › emitting the faithful @map contract succeeds` — emitting the Cascade @map m:n schema — prisma-next #1047 rejects the mapped m:n join-table auto-index name `CategoriesOnPostsManyToMany_AtAtMap_categoryId_AtMap_idx` (>54-char prefix limit); the faithful @map schema is not emittable. Prisma truncates/hashes long index names. Blocks the m-to-n @map matrix variants.
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/emit-map.test.ts` › `[emit @map] (index-name-length gap) › noaction-map › emitting the faithful @map contract succeeds` — emitting the NoAction @map m:n schema — prisma-next #1047 rejects the mapped m:n join-table auto-index name `CategoriesOnPostsManyToMany_AtAtMap_categoryId_AtMap_idx` (>54-char prefix limit); the faithful @map schema is not emittable. Prisma truncates/hashes long index names. Blocks the m-to-n @map matrix variants.
+- `test/ports/prisma/functional/relation-mode-gh-m-to-n/emit-map.test.ts` › `[emit @map] (index-name-length gap) › restrict-map › emitting the faithful @map contract succeeds` — emitting the Restrict @map m:n schema — prisma-next #1047 rejects the mapped m:n join-table auto-index name `CategoriesOnPostsManyToMany_AtAtMap_categoryId_AtMap_idx` (>54-char prefix limit); the faithful @map schema is not emittable. Prisma truncates/hashes long index names. Blocks the m-to-n @map matrix variants.

projects/port-all-tests/checklists/prisma-functional-issues.md

@@ -0,0 +1,36 @@
+// Port of prisma/prisma@a6d0155 packages/client/tests/functional/composites/list
+// prisma/_schema.ts (mongodb matrix entry).
+//
+// Upstream schema:
+//   model CommentRequiredList {
+//     id       String   @id @default(auto()) @map("_id") @db.ObjectId
+//     country  String?
+//     contents CommentContent[]
+//   }
+//   type CommentContent {
+//     text    String
+//     upvotes CommentContentUpvotes[]
+//   }
+//   type CommentContentUpvotes {
+//     vote   Boolean
+//     userId String
+//   }
+//
+// MongoDB PSL `type` blocks become value objects in the contract.
+
+type CommentContentUpvotes {
+  vote   Boolean
+  userId String
+}
+
+type CommentContent {
+  text    String
+  upvotes CommentContentUpvotes[]
+}
+
+model CommentRequiredList {
+  id       ObjectId @id @map("_id")
+  country  String?
+  contents CommentContent[]
+  @@map("comment_required_list")
+}