docs: infer full-fidelity capture in the user docs and upgrade entries

The contract and quickstart skills' brownfield sections state what infer
now captures (the full index matrix with managed re-detection, @@rls,
policy blocks with @@Map and verbatim bodies, the RESTRICTIVE spelling,
the skip-with-note case). Upgrade entries, both audiences: the user
skill's newly-available note covers infer fidelity, the map:-to-name:
re-detection on wire-shaped names, authorable permissive, and the legal
exact twins; the extension skill gains contract-infer-emits-full-
fidelity for packs whose contract-space generators run infer (additive
regen movement, delete out-of-band @@rls appenders). plan.md marks the
two slice-4 carry-overs landed with their commits and records the
release-notes deviation (authored at release-cut per repo convention).

Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>

Author: wmadden-electric

projects/functional-indexes/plan.md

@@ -49,10 +49,10 @@ The identity switch, done entirely beneath the authoring surface (existing `@@in
 ### 4 — `infer-round-trip`
 
 - D8 in full: index managed re-detection (recompute-and-match), `map:` fallback, policy block emission (head sanitization + dedup, `@@map` always, verbatim bodies), `@@rls` emission.
-- Slice-1 carry-over (dispatch-3 review): the authoring-time duplicate-content index guard (`validateStorageSemantics`) rejects byte-identical twins under different names. Legal in Postgres, so a database carrying them must still be signable — key the guard by name for exact-mode indexes (or equivalent) when infer starts emitting them.
-- Slice-1 carry-over: infer currently skips expression-carrying AND `where`-carrying index nodes (self-consistency — no authoring surface could hold the bodies); both skip sites are comment-marked for this slice. The Supabase reference contract re-adopts its partial indexes here.
+- Slice-1 carry-over (dispatch-3 review): the authoring-time duplicate-content index guard (`validateStorageSemantics`) rejects byte-identical twins under different names. Legal in Postgres, so a database carrying them must still be signable — key the guard by name for exact-mode indexes (or equivalent) when infer starts emitting them. **Landed** in `74117e56f` (exact entries name-identified; the named-object check carries name collisions).
+- Slice-1 carry-over: infer currently skips expression-carrying AND `where`-carrying index nodes (self-consistency — no authoring surface could hold the bodies); both skip sites are comment-marked for this slice. The Supabase reference contract re-adopts its partial indexes here. **Landed** in `8951c1345` (gates deleted, full-matrix emission) and `d4fe1f5eb` (Supabase re-adoption).
 - DoD-2 sign-the-database e2e, DoD-3 transition e2e, DoD-4 upgrade e2e; scenario A coverage completes the A–J matrix (DoD-5 sweep test list checked off here).
-- Release-notes draft for the breaking change + upgrade instructions (per the `record-upgrade-instructions` skill).
+- Release-notes draft for the breaking change + upgrade instructions (per the `record-upgrade-instructions` skill). **Deviation record:** the upgrade-instruction entries are complete (both skill clusters, 0.16-to-0.17); the committed `docs/releases/v0.17.0.md` is deliberately NOT authored in this slice — repo convention authors it at release-cut time via the `draft-release-notes` skill, which enumerates all merged PRs (spec § 7).
 
 ## Close-out (required)
 

skills/extension-author/prisma-next-extension-upgrade/upgrades/0.16-to-0.17/instructions.md

@@ -312,6 +312,27 @@ changes:
         - "PostgresPolicySchemaNode"
         - "policy_select"
       anyMatch: true
+  - id: contract-infer-emits-full-fidelity
+    summary: |
+      `contract infer` emits every non-constraint index (expression, partial `where:`,
+      unique, `type:`/`options:`) and the RLS surface (`@@rls` natively, every policy as a
+      `policy_<operation>` block with `@@map` and verbatim reprinted bodies, `permissive =
+      false` for RESTRICTIVE rows). A pack whose contract-space generator runs infer (the
+      supabase pattern) sees ADDITIVE movement on its next regeneration: previously omitted
+      partial/expression/unique indexes adopt as exact `map:` entries, and `@@rls` no longer
+      needs an out-of-band appender — delete any `applyRlsEnablement`-style post-processing
+      and regenerate through the checked-in generator; re-emit moves the storage hash. The
+      duplicate-index validation keys exact-mode entries by name, so a reference database's
+      content-identical twin indexes now validate. An index whose live name is wire-shaped
+      and whose hash recomputes re-infers as managed `name:` (real third-party names are not
+      wire-shaped, so adopted contracts stay `map:`).
+    detection:
+      glob: "**/*.{ts,mts,cts,prisma}"
+      contains:
+        - "inferPslContract"
+        - "contract infer"
+        - "@@rls"
+      anyMatch: true
 ---
 
 # 0.16 → 0.17 — Extension-author upgrade instructions

skills/prisma-next-contract/SKILL.md

@@ -354,6 +354,8 @@ pnpm prisma-next contract infer --db $DATABASE_URL --output ./src/prisma/contrac
 pnpm prisma-next contract emit
 ```
 
+Infer captures indexes at full fidelity — expression, partial (`where:`), unique non-constraint, `type:`/`options:` — adopting each under `map:` with the live name, except that a name shaped like a managed wire name whose hash recomputes from the content re-detects as managed and emits `name:` with the prefix. RLS surfaces too: `@@rls` on RLS-enabled models, and every policy as a `policy_<operation>` block with `@@map("<live name>")`, verbatim predicate reprints, and `permissive = false` for RESTRICTIVE rows (a policy whose role name can't be spelled as a PSL identifier is skipped with a comment note). Replacing an adopted `map:` with the plain managed spelling later converges via a single rename migration.
+
 ## Common Pitfalls
 
 1. **Forgetting to re-emit after an edit.** `contract.json` and `contract.d.ts` go stale; downstream typecheck and `migration plan` see the old shape. Re-emit, or install the Vite plugin (`prisma-next-build`).

skills/prisma-next-quickstart/SKILL.md

@@ -244,7 +244,7 @@ Then run the snippet from *Your first arc* above against the `User` model. When
 
 ## Workflow — Brownfield-DB (existing database, no contract)
 
-The concept: against an existing database with no PN contract, `contract infer` walks the live schema (tables, columns, indexes, constraints) and writes a PSL contract that describes it. The result is a *starting point*, not the final contract — review and clean it up, then `db sign` to record the current contract hash as the marker (instead of letting `db init` try to recreate the schema from scratch).
+The concept: against an existing database with no PN contract, `contract infer` walks the live schema (tables, columns, indexes — including expression and partial ones — constraints, and RLS enablement + policies) and writes a PSL contract that describes it. The result is a *starting point*, not the final contract — review and clean it up, then `db sign` to record the current contract hash as the marker (instead of letting `db init` try to recreate the schema from scratch).
 
 ```bash
 mkdir my-app && cd my-app

skills/upgrade/prisma-next-upgrade/upgrades/0.16-to-0.17/instructions.md

@@ -344,7 +344,7 @@ Each entry in a table's `indexes` array in `contract.json` / `contract.d.ts` now
 - `prefix` — present when the name is toolchain-managed: the physical name is then `<prefix>_<8hex>`, where the suffix is a content hash of the index definition.
 - `columns` — now optional; an index carries either `columns` or an opaque `expression` string, never both.
 
-Newly available in 0.17 (additive — no migration needed): RLS policy blocks (`policy_select` etc.) accept `@@map("physical name")` to adopt an existing live policy under its exact name — no wire-name hash, drift detection byte-compares the body against Postgres's reprint (hand-authoring the text warns with `PN_EXACT_NAME_BODY_COMPARISON`), and replacing `@@map` with the plain head later converges via a single `ALTER POLICY … RENAME`. Also newly available: both authoring surfaces accept the full index parameter matrix. PSL `@@index` and TS `constraints.index` take `expression:` (instead of a fields list; requires `name:` or `map:`), `where:` (partial-index predicate), `unique:`, `type:`/`options:` (target-registered access method), and `name:` xor `map:`. Combining `map:` with a SQL body emits the `PN_EXACT_NAME_BODY_COMPARISON` warning at build time — drift detection byte-compares hand-authored text against Postgres's reprint, so prefer `name:` unless the text was captured by `contract infer`. SQLite contracts reject `expression:`/`where:` with `CONTRACT.ARGUMENT_INVALID` (the target does not support them).
+Newly available in 0.17 (additive — no migration needed): `contract infer` captures the full index matrix (expression, partial `where:`, unique non-constraint, `type:`/`options:`) and the RLS surface (`@@rls`, every policy as a `policy_<operation>` block with `@@map` and verbatim reprinted bodies, `permissive = false` for RESTRICTIVE rows), so `infer → emit → db verify` is zero-issue on databases carrying those objects. Re-running `contract infer` therefore rewrites `contract.prisma` with more entries than 0.16 emitted; an index whose live name is wire-shaped (`<prefix>_<8hex>`, created by this toolchain) and whose hash recomputes now re-infers as managed `name:` instead of exact `map:` — both spellings verify clean, the managed one keeps renames first-class. `permissive` is an authorable policy-block property (default `true`; managed wire names for `permissive = true` policies are byte-unchanged). Contracts may also now carry two content-identical exact-named (`map:`) indexes under different names — legal twins a signed database can have. RLS policy blocks (`policy_select` etc.) accept `@@map("physical name")` to adopt an existing live policy under its exact name — no wire-name hash, drift detection byte-compares the body against Postgres's reprint (hand-authoring the text warns with `PN_EXACT_NAME_BODY_COMPARISON`), and replacing `@@map` with the plain head later converges via a single `ALTER POLICY … RENAME`. Also newly available: both authoring surfaces accept the full index parameter matrix. PSL `@@index` and TS `constraints.index` take `expression:` (instead of a fields list; requires `name:` or `map:`), `where:` (partial-index predicate), `unique:`, `type:`/`options:` (target-registered access method), and `name:` xor `map:`. Combining `map:` with a SQL body emits the `PN_EXACT_NAME_BODY_COMPARISON` warning at build time — drift detection byte-compares hand-authored text against Postgres's reprint, so prefer `name:` unless the text was captured by `contract infer`. SQLite contracts reject `expression:`/`where:` with `CONTRACT.ARGUMENT_INVALID` (the target does not support them).
 
 A contract emitted by 0.16 fails validation when a 0.17 toolchain loads it — a `Contract structural validation failed: storage.namespaces.<ns> …` error whose message contains `indexes[0].name must be a string (was missing)` and `indexes[0].unique must be boolean (was missing)` — and the storage hash moves for every contract that declares indexes. Re-emit: