[sync] T7650 fix(v2-computed): survive duplicate junction rows in link ordering and writes

.github/workflows/docker-push.yml

@@ -101,7 +101,7 @@ jobs:
 
       - uses: actions/setup-node@v4
         with:
-          node-version: 22.22.3
+          node-version: 24.19.0
 
       - name: Set up Docker Buildx
         uses: docker/setup-buildx-action@v3

.github/workflows/integration-tests.yml

@@ -22,7 +22,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        node-version: [22.22.3]
+        node-version: [24.19.0]
         e2e:
           - database-type: postgres
             shard: 1/4

.github/workflows/linting.yml

@@ -19,7 +19,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [22.22.3]
+        node-version: [24.19.0]
 
     steps:
       - uses: actions/checkout@v4

.github/workflows/manual-preview.yml

@@ -66,7 +66,7 @@ jobs:
 
       - uses: actions/setup-node@v4
         with:
-          node-version: 22.22.3
+          node-version: 24.19.0
       - name: ⚙️ Install zx
         run: npm install -g zx
 

.github/workflows/unit-tests.yml

@@ -22,7 +22,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [22.22.3]
+        node-version: [24.19.0]
 
     steps:
       - uses: actions/checkout@v4

.github/workflows/v2-benchmark-tests.yml

@@ -23,7 +23,7 @@ jobs:
 
     strategy:
       matrix:
-        node-version: [22.22.3]
+        node-version: [24.19.0]
 
     steps:
       - uses: actions/checkout@v4

.github/workflows/v2-core-tests.yml

@@ -33,10 +33,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Use Node.js 22.22.3
+      - name: Use Node.js 24.19.0
         uses: actions/setup-node@v4
         with:
-          node-version: 22.22.3
+          node-version: 24.19.0
 
       - name: 📥 Monorepo install
         uses: ./.github/actions/pnpm-install
@@ -63,10 +63,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Use Node.js 22.22.3
+      - name: Use Node.js 24.19.0
         uses: actions/setup-node@v4
         with:
-          node-version: 22.22.3
+          node-version: 24.19.0
 
       - name: 📥 Monorepo install
         uses: ./.github/actions/pnpm-install
@@ -102,10 +102,10 @@ jobs:
     steps:
       - uses: actions/checkout@v4
 
-      - name: Use Node.js 22.22.3
+      - name: Use Node.js 24.19.0
         uses: actions/setup-node@v4
         with:
-          node-version: 22.22.3
+          node-version: 24.19.0
 
       - name: 📥 Download all coverage artifacts
         uses: actions/download-artifact@v4

.npmrc

@@ -4,5 +4,5 @@ auto-install-peers=true
 lockfile=true
 # force use npmjs.org registry
 registry=https://registry.npmjs.org/
-use-node-version=22.22.3
+use-node-version=24.19.0
 save-prefix=''

Makefile

@@ -239,11 +239,17 @@ db-migration:		## Reruns the existing migration history in the shadow database i
 	@read -p "Enter name of the migration: " migration_name; \
   	make postgres-db-migration _MIGRATION_NAME=$$migration_name
 
+# The prisma CLI reads its datasource through dotenv-flow. The committed .env files carry no
+# credentials, so default NODE_ENV to development here: that loads .env.development, which
+# `switch.prisma.env` rewrites for the selected database mode. An exported PRISMA_DATABASE_URL
+# (the e2e targets above) still wins, because dotenv never overrides the environment.
 postgres.mode:		## postgres.mode
 	@cd ./packages/db-main-prisma; \
+		export NODE_ENV="$${NODE_ENV:-development}"; \
 		pnpm prisma-generate; \
 		pnpm prisma-migrate deploy --schema ./prisma/postgres/schema.prisma
 	@cd ./packages/db-data-prisma; \
+		export NODE_ENV="$${NODE_ENV:-development}"; \
 		pnpm prisma-generate; \
 		pnpm prisma-migrate deploy --schema ./prisma/schema.prisma
 # Override environment variable files based on variables

apps/nestjs-backend/.gitignore

@@ -10,4 +10,4 @@ dist
 *.pem
 .assets
 .temporary
-.webpack-cache
+.rspack-cache

apps/nestjs-backend/README.md

@@ -4,3 +4,16 @@ TODO:
 remove @valibot/to-json-schema in ai-sdk6
 remove effect in ai-sdk6
 remove @ai-sdk/provider-utils in ai-sdk6
+
+## ShareDB record recovery
+
+V2 socket snapshots retain empty cells as explicit `null` values within their
+authorized projection; ordinary record REST responses still omit empty cells.
+Version-gap recovery turns those snapshot entries into per-field set operations.
+Omitting empty cells here can advance the client version without clearing stale
+links or lookups after missed or out-of-order realtime updates. Keep clears
+explicit rather than deleting keys: hydrated record-detail views merge HTTP
+values underneath the live document and need `null` to override older values.
+
+Regression coverage: `test/record-socket-gap-recovery.e2e-spec.ts` exercises a
+retained document after unlinking, and bulk recovery of an entirely empty record.

apps/nestjs-backend/nest-cli.json

@@ -5,6 +5,11 @@
   "entryFile": "index",
   "flat": true,
   "compilerOptions": {
-    "builder": "webpack"
+    "builder": {
+      "type": "rspack",
+      "options": {
+        "configPath": "./rspack.config.js"
+      }
+    }
   }
 }