docs(upgrade): move the M:N read note to the 0.13→0.14 cycle

0.13.0 shipped without the sql-orm-client M:N runtime, so the note
describing the correlated include reads belongs in the 0.13→0.14
extension-author instructions, not the now-released 0.12→0.13 doc. The
upgrade-coverage gate targets 0.13→0.14 after the release bump.

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

Author: tensordreams

skills/extension-author/prisma-next-extension-upgrade/upgrades/0.12-to-0.13/instructions.md

@@ -73,12 +73,6 @@ unchanged; no extension API change. No codemod required.
 Release bump 0.13.0 (#789): version-number changes across all workspace
 `package.json` files and `pnpm-lock.yaml` specifiers. Incidental substrate
 diff — no extension-author action required.
-
-TML-2785: the sql-orm-client runtime gained M:N correlated include
-reads — `.include()` of an N:M relation resolves child rows through the
-junction table via a correlated subquery. Internal runtime only; no
-extension API or contract-shape change beyond the TML-2784 descriptor
-above. No extension-author action required.
 -->
 
 # 0.12 → 0.13 — Extension-author upgrade instructions

skills/extension-author/prisma-next-extension-upgrade/upgrades/0.13-to-0.14/instructions.md

@@ -22,6 +22,12 @@ changes:
 ---
 
 <!--
+TML-2785: the sql-orm-client runtime gained M:N correlated include
+reads — `.include()` of an N:M relation resolves child rows through the
+junction table via a correlated subquery. Internal runtime only; no
+extension API or contract-shape change. No extension-author action
+required.
+
 TML-2838: the temporary `--no-memory-protection-keys` test-harness workaround
 has been removed from every PGlite-backed vitest config (including
 `packages/3-extensions/{postgres,supabase}`) now that the WAL-teardown crash is