chore: resolve the rc.13 runtime from the registry

Solid 2.0.0-rc.13 is published; rc.12 never was (npm goes rc.11 -> rc.13).
The peer floor is the lowest published version carrying both features this
branch depends on — OBSERVE.include (solidjs/solid#3705) and the "request"
call record / CallRequestEvent / subscribe(..., { bodies: true })
(solidjs/solid#3708). rc.11's @solidjs/web types have neither; rc.13's do.
So peers and devDeps move to ^2.0.0-rc.13 and @solidjs/compiler pins
2.0.0-rc.13.

pnpm-lock.yaml is regenerated from the registry (no link: overrides; the
branch was developed against local links that were never committed).
pnpm added the rc.13 Solid packages (solid-js, @solidjs/web,
@solidjs/signals, @solidjs/compiler and its platform binaries) to
minimumReleaseAgeExclude so the fresh release installs.

Re-run against the published packages: vitest 96/96, tsc clean, build
emits only _$$click, playwright 8/8, publint + attw clean.

Author: ryansolid

package.json

@@ -52,17 +52,17 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@solidjs/web": "^2.0.0-rc.12",
-    "solid-js": "^2.0.0-rc.12"
+    "@solidjs/web": "^2.0.0-rc.13",
+    "solid-js": "^2.0.0-rc.13"
   },
   "devDependencies": {
     "@arethetypeswrong/cli": "^0.18.5",
     "@changesets/cli": "^2.30.0",
     "@jridgewell/trace-mapping": "^0.3.31",
     "@playwright/test": "^1.62.1",
-    "@solidjs/compiler": "2.0.0-rc.12",
+    "@solidjs/compiler": "2.0.0-rc.13",
     "@solidjs/vite-plugin": "3.0.0-next.46",
-    "@solidjs/web": "^2.0.0-rc.12",
+    "@solidjs/web": "^2.0.0-rc.13",
     "@types/node": "^24.0.0",
     "error-stack-parser-es": "^2.0.1",
     "html-to-image": "^1.11.13",
@@ -72,7 +72,7 @@
     "rolldown-plugin-dts": "^0.28.2",
     "seroval": "^1.6.0",
     "shiki": "^4.3.1",
-    "solid-js": "^2.0.0-rc.12",
+    "solid-js": "^2.0.0-rc.13",
     "terracotta": "2.0.0-next.9",
     "typescript": "^7.0.2",
     "vite": "^8.2.1",