refactor(cli,fixtures,docs): migrate remaining @relation(fields:/references:) in .psl/.ts/.md to from/to

Finish the from/to migration for non-.prisma sites the .prisma-focused
passes missed: the SQL emit-command parity .psl fixture, the Postgres PSL
init template string (and its snapshot), and live authoring examples in
the SQL contract-psl README, the prisma-next-contract skill, two subsystem
docs, and ADR 121 / ADR 226 worked examples.

Deliberate legacy sites are left intact: resolver rejection tests and
diagnostic strings, parser/printer fidelity fixtures that never reach the
resolver, frozen release/upgrade history (CHANGELOG, releases, upgrade
recipe), project design records under projects/, and ADR 226 prose
explaining the legacy attribute grammar.

Signed-off-by: Alexey Orlenko's AI Agent <robot@aqrln.net>

Author: tensordreams

docs/architecture docs/adrs/ADR 121 - Contract.d.ts structure and relation typing.md

@@ -40,7 +40,7 @@ model Post {
   id        Int      @id @default(autoincrement())
   title     String
   userId    Int
-  user      User     @relation(fields: [userId], references: [id])
+  user      User     @relation(from: [userId], to: [id])
   createdAt DateTime @default(now())
 }
 ```
@@ -235,7 +235,7 @@ model User {
 
 model Profile {
   id     Int  @id
-  user   User @relation(fields: [userId], references: [id])
+  user   User @relation(from: [userId], to: [id])
   userId Int  @unique
 }
 ```
@@ -264,7 +264,7 @@ model User {
 
 model Post {
   id     Int  @id
-  user   User @relation(fields: [userId], references: [id])
+  user   User @relation(from: [userId], to: [id])
   userId Int
 }
 ```

docs/architecture docs/adrs/ADR 226 - Cross-contract foreign-key references.md

@@ -19,7 +19,7 @@ namespace public {
   model Profile {
     id     String @id @default(uuid())
     userId Uuid   @unique
-    user   supabase:auth.AuthUser @relation(fields: [userId], references: [id], onDelete: Cascade)
+    user   supabase:auth.AuthUser @relation(from: [userId], to: [id], onDelete: Cascade)
   }
 }
 ```

docs/architecture docs/subsystems/2. Contract Emitter & Types.md

@@ -31,7 +31,7 @@ model User {
 model Post {
   id     Int   @id @default(autoincrement())
   title  String
-  user   User  @relation(fields: [userId], references: [id])
+  user   User  @relation(from: [userId], to: [id])
   userId Int
   @@index([userId])
 }

docs/architecture docs/subsystems/6. Ecosystem Extensions & Packs.md

@@ -375,7 +375,7 @@ namespace public {
   model Profile {
     id     String @id @default(uuid())
     userId Uuid   @unique       // @unique makes this a 1:1 relationship
-    user   supabase:auth.AuthUser @relation(fields: [userId], references: [id], onDelete: Cascade)
+    user   supabase:auth.AuthUser @relation(from: [userId], to: [id], onDelete: Cascade)
     @@map("profile")
   }
 }

packages/1-framework/3-tooling/cli/src/commands/init/templates/code-templates.ts

@@ -126,7 +126,7 @@ model Post {
   id        Int      @id @default(autoincrement())
   title     String
   content   String?
-  author    User     @relation(fields: [authorId], references: [id])
+  author    User     @relation(from: [authorId], to: [id])
   authorId  Int
   createdAt DateTime @default(now())
   updatedAt temporal.updatedAt()

packages/1-framework/3-tooling/cli/test/commands/init/__snapshots__/templates.test.ts.snap

@@ -606,7 +606,7 @@ model Post {
   id        Int      @id @default(autoincrement())
   title     String
   content   String?
-  author    User     @relation(fields: [authorId], references: [id])
+  author    User     @relation(from: [authorId], to: [id])
   authorId  Int
   createdAt DateTime @default(now())
   updatedAt temporal.updatedAt()

packages/2-sql/2-authoring/contract-psl/README.md

@@ -51,7 +51,7 @@ Unsupported PSL constructs in v1 (strict errors):
   - Scalar lists like `String[]`
   - Enum lists and named-type lists
 - **Relation navigation lists are supported** when they can be matched to an FK-side relation:
-  - Example: `User.posts Post[]` + `Post.user User @relation(fields: [userId], references: [id])`
+  - Example: `User.posts Post[]` + `Post.user User @relation(from: [userId], to: [id])`
   - Matching may use `@relation("Name")` or `@relation(name: "Name")` when multiple candidates exist
   - Navigation list fields accept only `@relation` (name-only form); other field attributes are strict errors
 - **Implicit Prisma ORM many-to-many remains unsupported** (list navigation on both sides without explicit join model)

skills/prisma-next-contract/SKILL.md

@@ -93,7 +93,7 @@ model Post {
   id       Int    @id @default(autoincrement())
   title    String
   authorId Int
-  author   User   @relation(fields: [authorId], references: [id], onDelete: Cascade)
+  author   User   @relation(from: [authorId], to: [id], onDelete: Cascade)
 
   @@unique([title, authorId])
   @@index([authorId])
@@ -290,7 +290,7 @@ namespace public {
     id       String @id @default(uuid())
     username String
     userId   Uuid   @unique
-    user     supabase:auth.AuthUser @relation(fields: [userId], references: [id], onDelete: Cascade)
+    user     supabase:auth.AuthUser @relation(from: [userId], to: [id], onDelete: Cascade)
     @@map("profile")
   }
 }

test/integration/test/fixtures/cli/cli-integration-test-app/fixtures/emit-command/schema.parity.psl

@@ -24,7 +24,7 @@ model Post {
   userId Int
   title String
   rating Float?
-  author User @relation(fields: [userId], references: [id], onDelete: Cascade, onUpdate: Cascade)
+  author User @relation(from: [userId], to: [id], onDelete: Cascade, onUpdate: Cascade)
   @@index([userId])
   @@unique([title, userId])
 }