diff --git a/.changeset/pre.json b/.changeset/pre.json
index b56c6f7dc..c2e5c00ea 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -27,6 +27,7 @@
   },
   "changesets": [
     "a28-writes-visible-at-flush",
+    "abandoned-loading-pass-yields-fragment",
     "abortsignal-types-no-dom",
     "absorb-expressions",
     "accept-empty-server-function-posts",
@@ -47,6 +48,7 @@
     "adopt-runtime-wire-protocols",
     "adopted-recall-claim-gate",
     "adopted-slot-range-stays-live",
+    "adopted-zombie-follows-lane",
     "affects-captured-proxy-scope",
     "affects-single-key",
     "afraid-queens-divide",
@@ -80,11 +82,15 @@
     "audit-driver-family-decline-multi-slot",
     "avoid-reconcile-key-recompute",
     "awaitable-refresh",
+    "babel-plugin-ssr-hoist-props-ts-types",
     "bare-client-source-suspends-as-final-hole",
     "behavior-claims-delegate-glue",
     "behavior-claims-props",
     "bind-get-grants-to-function-identity",
+    "binding-slot-execution",
+    "binding-slot-text-positions",
     "body-end-visibility",
+    "born-held-effect-lane-run-restages",
     "born-held",
     "bound-body-by-bytes-received",
     "bound-server-function-requests",
@@ -106,6 +112,7 @@
     "bump-dom-expressions-next-5",
     "bump-dom-expressions-next-8",
     "carry-live-get-grant-across-dev-rebind",
+    "chunk-reader-hardening",
     "clarify-invoke-wrapper-contract",
     "clean-bikes-teach",
     "cleanup-unwind-order",
@@ -121,17 +128,26 @@
     "commit-clears-transition-stamp",
     "companion-oracle-census",
     "companion-shadow-redesign",
+    "compiler-clippy-rustfmt-cleanup",
     "compiler-component-names",
+    "compiler-coverage-pragmas",
     "compiler-loader-accepts-patch-driver",
     "compiler-loader-prefer-local-build",
     "compiler-server-components-attribute-slot-positions",
+    "compiler-source-locations",
     "compiler-source-names-bindings",
     "compiler-source-names-option",
     "compiler-source-names-primitives",
     "compiler-spread-sources-array",
+    "compiler-ssr-capture-source-locations",
+    "compiler-ssr-hoist-props-ts-types",
+    "compiler-unicode-diagnostics",
+    "compiler-wasi-android-root",
     "composed-header-bounds-transport",
+    "const-effect-tuple-inference",
     "contain-flight-collector-errors",
     "container-tier-projection-traces",
+    "container-trace-claim-reads-snapshot",
     "context-default-less-throws",
     "continue-tsrx-semantic-ir",
     "core-hot-path-shape-alignment",
@@ -150,7 +166,13 @@
     "deprecate-create-tracked-effect",
     "deprecate-dynamic-component",
     "deprecate-server-writes",
+    "derive-reads-held-key-joins",
+    "derived-optimistic-writer-frame",
+    "derived-store-retained-draft-row",
+    "derived-writes-apply-before-derivations",
     "dev-artifact-naming",
+    "dev-cost-checks-plumbing-exempt",
+    "dev-cost-checks-tracks-records-only",
     "dev-error-invalid-refresh-target",
     "dev-error-non-function-component",
     "dev-error-untracked-async-read",
@@ -163,6 +185,7 @@
     "diagnostic-code-consolidation",
     "diagnostic-code-prefix",
     "diagnostic-console-footers",
+    "diagnostic-guide-sections",
     "diagnostics-console-addressability",
     "diagnostics-engine-release-token",
     "diagnostics-fanout-repair-projection",
@@ -187,6 +210,7 @@
     "dynamic-factory-redesign",
     "dynamic-remount-latest-address",
     "dynamic-run-hydration-events",
+    "dynamic-spread-attributes-before-children",
     "dynamic-static-source",
     "dynamic-xmlns-namespace",
     "effect-cleanup-unwind-order",
@@ -205,6 +229,7 @@
     "enforce-provide-event-single-invocation",
     "error-hook-thrower-path",
     "errored-fallback-thunk-scope",
+    "errored-pass-tail-still-observes",
     "export-memo-options",
     "expose-enableExternalSource-loading-on",
     "extract-nested-server-function-declarations",
@@ -213,6 +238,7 @@
     "feedback-findings",
     "fetch-option-retry-contract",
     "fill-cleanup-occurrence-scope",
+    "first-load-lands-into-hold",
     "fix-absorbed-compiler-parity",
     "fix-action-falsy-generator-throw",
     "fix-action-thenable-await",
@@ -299,6 +325,7 @@
     "fix-frames-web-path-mapping",
     "fix-get-grant-lifetime-and-read-folding",
     "fix-get-request-event-cross-request",
+    "fix-graph-growth-initial-declaration",
     "fix-halt-error-swallow",
     "fix-held-conditional-effect",
     "fix-held-conditional-memo",
@@ -312,6 +339,7 @@
     "fix-hydration-and-signals-baseline",
     "fix-hydration-latched-divergence-lost",
     "fix-hydration-trace-foreign-iterable",
+    "fix-hydration-trace-promise-statics",
     "fix-insert-sibling-rerender",
     "fix-insert-text-node-reuse",
     "fix-ispending-dev-prod-divergence",
@@ -372,6 +400,7 @@
     "fix-optimistic-move-duplicate-3548",
     "fix-optimistic-override-premature-revert",
     "fix-optimistic-read-lane-not-transaction",
+    "fix-optimistic-removed-prop-read",
     "fix-optimistic-same-value-overlap",
     "fix-optimistic-settle-verdicts",
     "fix-optimistic-store-layer-scope",
@@ -383,6 +412,7 @@
     "fix-override-supersession-on-arrival",
     "fix-owned-write-guard-docs",
     "fix-ownerless-conditional-memos",
+    "fix-parenthesized-tsrx-keys",
     "fix-pending-autodispose-release",
     "fix-pending-companion-lane-parent",
     "fix-pending-gated-landing-replay",
@@ -467,6 +497,7 @@
     "fix-ssr-escape-function-results",
     "fix-ssr-loading-errored-hydration",
     "fix-ssr-memo-promise-notready",
+    "fix-ssr-nullish-attributes",
     "fix-ssr-owner-id-parity",
     "fix-ssr-owner-pool-stale-links",
     "fix-ssr-post-render-rejection-3570",
@@ -478,6 +509,7 @@
     "fix-ssr-spread-children-read-once",
     "fix-ssr-stream-bare-child-rejection-3569",
     "fix-ssr-stream-rejected-fragment-hang",
+    "fix-ssr-style-object-separators",
     "fix-ssr-sync-memo-child-id-leak",
     "fix-ssr-text-separators-resolved",
     "fix-ssr-textarea-spread-value",
@@ -516,10 +548,12 @@
     "fix-tsrx-index-loop-mode",
     "fix-tsrx-lazy-update-rewrites",
     "fix-tsrx-release-expansion-stack",
+    "fix-tsrx-setup-semicolon",
     "fix-universal-text-escaping",
     "fix-usehead-prelude-hydration-walk",
     "fix-usehead-stylesheet-hydration",
     "fix-validate-document-shell",
+    "fix-verdict-lane-flush-loop",
     "fix-version-skew-label-before-gate",
     "fix-zombie-flag-survives-recompute",
     "flash-falsy-nojs-outcomes",
@@ -532,24 +566,55 @@
     "format-ssr-hydration-followups",
     "fragment-ledger-one-reveal-owner",
     "fragment-reveal-policy-registry",
+    "fragment-stylesheet-gate",
     "frame-conditional-reconnect",
     "frame-scope-projection-pump",
     "frame-teardown-on-disconnect",
+    "frames-a1b-stage-deletion-s-ref",
+    "frames-a3-reveal-applies-its-range",
+    "frames-a4-declared-slot-records",
+    "frames-a5-fragment-ownership-by-rendering",
+    "frames-a7-error-throws-reset-reasks",
+    "frames-address-source",
+    "frames-assets-tier",
     "frames-attribute-slots",
+    "frames-bind-tier",
+    "frames-c12-fragment-error-outcome",
+    "frames-c13-sweep-ops-chunk",
+    "frames-claim-through-hydrate-window",
     "frames-client-externalize-wire-layer",
     "frames-consume-live",
+    "frames-data-response-scoped",
+    "frames-drop-dead-slot-nodes-writes",
     "frames-dynamic-handoff",
     "frames-element-seams",
+    "frames-fragment-rejection-report",
+    "frames-hold-is-pending-boundary",
     "frames-identity-split",
     "frames-lazy-codec-and-op-log-compaction",
     "frames-live-document-face",
     "frames-live-slot-props-binding",
+    "frames-live-wire-tier",
+    "frames-plain-response-bound",
+    "frames-rebind-in-the-pass",
+    "frames-refetch-lands-at-commit",
+    "frames-regions-tier",
+    "frames-residue-1-d-list",
+    "frames-residue-1-have-constants",
+    "frames-residue-1-lean-reask",
+    "frames-residue-3-every-fill-through-insert",
+    "frames-residue-4-sref-table",
     "frames-server-components-experimental",
     "frames-showing-refetch-settles-on-apply",
     "frames-single-flight-wiring",
+    "frames-slot-arg-abandoned-flights",
     "frames-slot-claim-handover",
     "frames-slot-type",
+    "frames-tier-mechanism",
+    "frames-trace-update-site-wait",
+    "frames-traces-tier",
     "freeze-awaited-render-head",
+    "fresh-loading-fallback-in-flush",
     "fuzzy-queens-retire",
     "gate-child-companion-walk",
     "gate-invariants-to-test-builds",
@@ -562,6 +627,7 @@
     "guard-error-carried-failure-channels",
     "guard-failures-iterative-walk",
     "guard-getter-and-map-key-channels",
+    "h-rematerialize-without-mutating-props",
     "halt-reactivity-on-uncaught-error",
     "handle-async-setter-errors",
     "head-shell-hold-probe-seam",
@@ -573,12 +639,16 @@
     "hold-consistency-batch-2",
     "hot-scope-fanout-aggregation",
     "html-braced-comments",
+    "html-component-on-prop-getters",
     "html-element-claims",
+    "html-self-closing-raw-text",
     "hydrate-claim-path",
     "hydrating-root-snapshot-scope",
     "hydrating-store-engine-seam",
     "hydration-latch-outside-pending-boundaries",
+    "hydration-late-claim-keeps-nodes-in-place",
     "hydration-null-owner-hybrid-latch",
+    "hydration-payload-owns-record-rejections",
     "hydration-primitive-wrappers",
     "hydration-write-time-snapshot",
     "identity-keyed-server-function-ids",
@@ -588,6 +658,7 @@
     "improve-tsrx-lazy-destructuring",
     "include-web-cookie-declarations",
     "initial-route-declaration",
+    "interaction-frame-per-event",
     "internal-surface-followup",
     "internal-view-protocol-surface",
     "inv2-active-override-assertion",
@@ -599,13 +670,22 @@
     "iterate-bare-step-tolerance",
     "iterator-supersede-eager-close",
     "jfb-driver-and-write-bound",
+    "joined-slot-adopts-answer",
     "jsx-key-intrinsic-typing",
     "keep-ambient-batch-on-stash",
     "keep-negative-zero-off-the-json-fast-path",
+    "l2-fuzz-existing-rules",
     "label-version-skew-404",
+    "landing-rejudges-parked-transactions",
     "lane-drop-dead-companion-refresh",
     "lane-frame-children-3662",
     "lane-hold-on-observation",
+    "lane-holds-through-boundary-content",
+    "lane-mount-binding-reads-screen",
+    "lane-mount-boundary-over-flight",
+    "lane-node-in-held-frame-stays-the-lanes",
+    "lane-stale-reader-unheld-lane",
+    "lane-takeover-held-effect",
     "late-boundary-held-fragment-wait",
     "latest-lazy-companion-backfill",
     "latest-probe-order-independence",
@@ -633,6 +713,7 @@
     "live-retryable-4xx-and-retry-after",
     "live-return-completes-nested",
     "live-source-auto-hybrid",
+    "live-takeover-streaming-value",
     "live-takeover-yields-adopted-value",
     "loading-errored-composition-escape",
     "loading-on-follows-frame",
@@ -646,6 +727,7 @@
     "loading-window-verdict-quiet-through-hydration",
     "lone-spread-no-merge",
     "long-hold-and-stricter-thresholds",
+    "lowercase-on-is-attribute",
     "maparray-nonkeyed-store-stale-row",
     "maparray-small-move-fast-path",
     "maparray-swap-commit",
@@ -684,6 +766,8 @@
     "optimistic-lists-drivable",
     "optimistic-mask-effective-writes-only",
     "optimistic-mask-ispending",
+    "optimistic-over-held-row",
+    "optimistic-retained-draft-row",
     "optimistic-reverted",
     "optimistic-store-first-flight-no-transaction",
     "optimistic-undeclared-flight-owner",
@@ -762,6 +846,7 @@
     "reconcile-array-object-shape-guard",
     "reconcile-default-id-positional-null",
     "reconcile-symbol-keyed-nodes",
+    "reconcile-unchanged-presence-no-hold",
     "reconcile-walk-guard-hoist",
     "recover-from-halt-in-dev-workflows",
     "recover-tsrx-editor-snapshots",
@@ -798,6 +883,7 @@
     "remove-create-effect-single-argument-overload",
     "remove-derived-initial-values",
     "remove-dist-exports-and-fix-dual-types",
+    "remove-empty-signals-reexport",
     "remove-initial-ssr-source",
     "remove-isrefreshing-api",
     "remove-loading-notify-through-remap",
@@ -814,11 +900,13 @@
     "renderer-owned-jsx-types",
     "repeat-disjoint-window",
     "republish-fresh-signals-build",
+    "request-failure-report",
     "require-client-source-commit-zero",
     "require-seroval-1-5-4",
     "require-seroval-1-6",
     "response-head-lifecycle",
     "responsive-preload-links",
+    "restaged-effect-no-early-run",
     "reveal-order-prop",
     "reveal-ssr-streaming-support",
     "reveal-string-ssr-collapsed",
@@ -836,6 +924,7 @@
     "scope-property-read-holes",
     "serialization-decode-entry",
     "serve-one-slow-selection",
+    "server-async-iterable-slot-memory",
     "server-boundary-records",
     "server-component-context-barrier",
     "server-dev-build",
@@ -865,6 +954,7 @@
     "server-store-replacement-optimistic-noop",
     "server-trace-context",
     "setter-row-ops-tentative-lists",
+    "settle-fast-path",
     "settle-superseded-flight-dependents",
     "settle-unchanged-pending-branches",
     "settle-walk-dev-invariant",
@@ -886,6 +976,30 @@
     "simplify-render-wrappers",
     "single-flight-keyed-envelope-only",
     "single-flight-protocol-bridge",
+    "single-flight-settle-streamed-slices",
+    "size-affects-on-l2",
+    "size-attribution-on-l2",
+    "size-audit-l2-hold-model",
+    "size-carve-lane-layer",
+    "size-lane-layer-s0",
+    "size-lane-layer-s1",
+    "size-lane-layer-s2",
+    "size-spec-l2-hold-model",
+    "size-store-bench-fixes-2",
+    "size-store-bench-fixes",
+    "size-store-container-node-escape-hatch",
+    "size-store-prebatch-backing",
+    "size-stores-on-l2-s3c",
+    "size-stores-qd-parity",
+    "size-stores-qd-provenance",
+    "size-stores-s1-plain",
+    "size-stores-s2-holds",
+    "size-stores-s3a-projections",
+    "size-stores-s3b-held-derived",
+    "size-stores-s4-optimistic",
+    "size-stores-s4-seam-trim",
+    "size-stores-s5-affects",
+    "size-stores-su-utils",
     "skip-sync-noop-status-work",
     "slot-jsx-convention-docs",
     "slot-signal-creation-diet",
@@ -900,6 +1014,7 @@
     "spread-direct-sources",
     "spread-fewer-nodes",
     "ssr-boundary-resolve-scope-3414",
+    "ssr-capture-source-locations",
     "ssr-component-names",
     "ssr-element-attrs-and-merge-read-path",
     "ssr-element-join-in-place",
@@ -908,12 +1023,17 @@
     "ssr-falsy-rejections-and-thenables",
     "ssr-hole-id-scopes",
     "ssr-props-hoisted-constructors",
+    "ssr-response-settles-pre-shell",
+    "ssr-response-teardown-on-cancel-and-redirect",
     "ssr-retry-robustness",
     "ssr-scope-lazy-id",
     "ssr-shared-async-sources",
+    "ssr-shell-suspend-retry",
+    "ssr-shell-suspend-serializer-flush",
     "ssr-spread-static-tail",
     "ssr-spread-static-text-escape",
     "ssr-spread-walk-hot-path",
+    "ssr-validate-dynamic-names",
     "ssrSource-effects-and-fix-server-createEffect",
     "ssrsource-async-iterables",
     "staged-reporter-deps-tail",
@@ -927,6 +1047,7 @@
     "store-descriptor-trap-subscribes",
     "store-enumerator-presence-nodes-3664",
     "store-first-read-diet",
+    "store-fold-queue-prebatch-record",
     "store-hold-visible",
     "store-hot-path-trims",
     "store-next-settled-visibility",
@@ -991,6 +1112,7 @@
     "universal-renderer-effect-names",
     "universal-spread-sources",
     "unstable-list-identity",
+    "unstable-memo-symbol-keys",
     "until-flip-entanglement",
     "until-live-source-ack",
     "untracked-async-handler",
@@ -1012,13 +1134,19 @@
     "update-signals-bugfix-baseline",
     "validate-malformed-html-error",
     "validate-prepare-request-return",
+    "verdict-mount-first-pass-mainline",
+    "verdict-pull-outside-window",
+    "verdict-reader-first-observer-holds-the-flight",
+    "verdict-reader-silent-landing",
     "view-table-on-enumeration",
     "violet-stingrays-end",
     "wait-asset-seam",
     "wake-synchronously-settled-transactions",
     "warm-doors-flow",
+    "wasted-recompute-undefined-output",
     "wasted-recompute",
     "web-commit-event-response",
+    "web-dynamic-component",
     "web-feature-folders",
     "web-http-declaration-ledger",
     "web-lazy-serializer-split",
@@ -1027,6 +1155,7 @@
     "web-request-event-locals",
     "web-serialization-create-plugin",
     "web-server-dist-prod-mode",
+    "web-server-entry-treeshaking",
     "why-did-this-run-attribution",
     "woken-transaction-staged-bump",
     "write-proposals-3494",
diff --git a/examples/todos-server/CHANGELOG.md b/examples/todos-server/CHANGELOG.md
index eaf4a66e7..864751225 100644
--- a/examples/todos-server/CHANGELOG.md
+++ b/examples/todos-server/CHANGELOG.md
@@ -1,5 +1,70 @@
 # todos-server-example
 
+## 0.0.1-rc.2
+
+### Patch Changes
+
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9a213bb]
+- Updated dependencies [721eb06]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [365f37d]
+- Updated dependencies [da84bd9]
+- Updated dependencies [98d35b9]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [759a9b6]
+- Updated dependencies [e345dc7]
+- Updated dependencies [4f67697]
+- Updated dependencies [41fdf96]
+- Updated dependencies [87a3862]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - solid-js@2.0.0-rc.14
+  - @solidjs/web@2.0.0-rc.14
+
 ## 0.0.1-rc.1
 
 ### Patch Changes
diff --git a/examples/todos-server/package.json b/examples/todos-server/package.json
index 7c362608f..199daa9d2 100644
--- a/examples/todos-server/package.json
+++ b/examples/todos-server/package.json
@@ -1,7 +1,7 @@
 {
   "name": "todos-server-example",
   "description": "TodoMVC as a Solid Server Component — the list is server markup, and every optimistic behavior (toggle, remove, pending/error/retry, counts, filters) is a client fill over slot args and createOptimisticStore state: binding slots the server template reads at positions, a shared TodoRow on both sides, one markup slot for pending adds",
-  "version": "0.0.1-rc.1",
+  "version": "0.0.1-rc.2",
   "private": true,
   "author": "Ryan Carniato",
   "license": "MIT",
diff --git a/packages/babel-plugin/CHANGELOG.md b/packages/babel-plugin/CHANGELOG.md
index 67a3ab4e6..6ec6a26c1 100644
--- a/packages/babel-plugin/CHANGELOG.md
+++ b/packages/babel-plugin/CHANGELOG.md
@@ -1,5 +1,22 @@
 # @solidjs/babel-plugin
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- 59fb244: SSR `hoistProps` skips TypeScript type positions when collecting captures, so on authored TSX (types parsed, stripped later) a `typeof x` query or a type named like a value no longer captures that value, or forces the literal fallback when it is reassigned (#3828).
+- 3c1f809: Preserve `/* istanbul ignore … */` and `/* c8 ignore … */` block comments written as JSX children on the generated component `children` getter. Line comments are not carried.
+- 98b916d: Fix compiled SSR output that renders `style=""` or `class=""` for `null` and `undefined`. Babel and the native compiler now omit these attributes on elements without a spread.
+- 98d35b9: Fix computed keys in compiled SSR `style` objects (builds without `serverComponents`). A computed key's name got no `;`, so `style={{ color: "red", [k]: v }}` rendered `color:redtop:1px` and the browser dropped both declarations. Hydration keeps the server's inline style, so they stayed dropped. A nullish first value also no longer leaves a leading `;`. Both compilers now pass a multi-entry object to a new `ssrStyleProperties(name, value, …)` helper, which writes the separator only between the entries it writes; a single entry keeps `ssrStyleProperty`.
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
+- 7513131: Preserve the source location of captured references in SSR props constructors so source maps point to the authored expression, including dynamic TSRX tags.
+
 ## 2.0.0-rc.13
 
 ## 2.0.0-rc.12
diff --git a/packages/babel-plugin/package.json b/packages/babel-plugin/package.json
index 779917d3d..e474d1fa8 100644
--- a/packages/babel-plugin/package.json
+++ b/packages/babel-plugin/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/babel-plugin",
   "description": "Babel compiler plugin for Solid templates",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "repository": {
diff --git a/packages/compiler/CHANGELOG.md b/packages/compiler/CHANGELOG.md
index f7e2f9518..5b7285c9e 100644
--- a/packages/compiler/CHANGELOG.md
+++ b/packages/compiler/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @solidjs/compiler
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- ba8c593: Restore Clippy and rustfmt checks for the native compiler and apply the resulting lint and formatting cleanups
+- 3c1f809: Preserve `/* istanbul ignore … */` and `/* c8 ignore … */` block comments written as JSX children on the generated component `children` getter. Line comments are not carried.
+- 5dbe29a: Count all JavaScript line terminators in scoped style and refresh locations and DOM and server-function diagnostics. Report diagnostic columns in UTF-16 units.
+- a8c98bd: Preserve the source location of captured references in SSR props constructors so source maps point to the authored expression instead of the start of the JSX element, matching `@solidjs/babel-plugin`.
+- 59fb244: SSR `hoistProps` no longer captures names in TypeScript type positions (type parameters, annotations, `as`/`satisfies` targets, type arguments, `typeof x` queries, local `type`/`interface` declarations, `implements`/`extends` heritage) as constructor arguments, which threw `ReferenceError` once the types were stripped (#3828). A `type` or `interface` that shares a value's name no longer makes that value count as redeclared, so its site still hoists.
+- ab57910: Report correct TSRX diagnostic positions after Unicode line separators and carriage returns, preserving UTF-16 columns and treating CRLF as one line break.
+- 41be120: The `@solidjs/compiler-wasm32-wasi` fallback loads on Android (Termux), where the filesystem root cannot be opened: its generated loader no longer preopens `/` there (it failed with `UVWASI_EACCES, uvwasi_init`). The loader is regenerated by `@napi-rs/cli` 3.10.6, which maps the WASI root to the working directory on Android.
+- c8aac88: Fix native TSRX compilation of parenthesized keys, iterables, and conditions, including annotated `@for` loops used directly in a component body. Map comments back to the authored source to prevent invalid JavaScript and Unicode panics when source maps are enabled.
+- 98b916d: Fix compiled SSR output that renders `style=""` or `class=""` for `null` and `undefined`. Babel and the native compiler now omit these attributes on elements without a spread.
+- 98d35b9: Fix computed keys in compiled SSR `style` objects (builds without `serverComponents`). A computed key's name got no `;`, so `style={{ color: "red", [k]: v }}` rendered `color:redtop:1px` and the browser dropped both declarations. Hydration keeps the server's inline style, so they stayed dropped. A nullish first value also no longer leaves a leading `;`. Both compilers now pass a multi-entry object to a new `ssrStyleProperties(name, value, …)` helper, which writes the separator only between the entries it writes; a single entry keeps `ssrStyleProperty`.
+- ea5f1da: Fix native TSRX compilation when a setup statement has no semicolon before markup.
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
 ## 2.0.0-rc.13
 
 ## 2.0.0-rc.12
diff --git a/packages/compiler/npm/darwin-arm64/package.json b/packages/compiler/npm/darwin-arm64/package.json
index 315b88ceb..7c6e56153 100644
--- a/packages/compiler/npm/darwin-arm64/package.json
+++ b/packages/compiler/npm/darwin-arm64/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-darwin-arm64",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "cpu": [
     "arm64"
   ],
@@ -19,4 +19,4 @@
   "os": [
     "darwin"
   ]
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/npm/darwin-x64/package.json b/packages/compiler/npm/darwin-x64/package.json
index 761629a22..d5d08d134 100644
--- a/packages/compiler/npm/darwin-x64/package.json
+++ b/packages/compiler/npm/darwin-x64/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-darwin-x64",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "cpu": [
     "x64"
   ],
@@ -19,4 +19,4 @@
   "os": [
     "darwin"
   ]
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/npm/linux-arm64-gnu/package.json b/packages/compiler/npm/linux-arm64-gnu/package.json
index b3b8ced9d..92d43bdc0 100644
--- a/packages/compiler/npm/linux-arm64-gnu/package.json
+++ b/packages/compiler/npm/linux-arm64-gnu/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-linux-arm64-gnu",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "cpu": [
     "arm64"
   ],
@@ -22,4 +22,4 @@
   "libc": [
     "glibc"
   ]
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/npm/linux-x64-gnu/package.json b/packages/compiler/npm/linux-x64-gnu/package.json
index 262baa254..c8fbcaa6b 100644
--- a/packages/compiler/npm/linux-x64-gnu/package.json
+++ b/packages/compiler/npm/linux-x64-gnu/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-linux-x64-gnu",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "cpu": [
     "x64"
   ],
@@ -22,4 +22,4 @@
   "libc": [
     "glibc"
   ]
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/npm/wasm32-wasi/package.json b/packages/compiler/npm/wasm32-wasi/package.json
index 5bbbf6b3c..717f691bc 100644
--- a/packages/compiler/npm/wasm32-wasi/package.json
+++ b/packages/compiler/npm/wasm32-wasi/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-wasm32-wasi",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "main": "compiler.wasi.cjs",
   "files": [
     "compiler.wasm32-wasi.wasm",
@@ -26,4 +26,4 @@
     "@emnapi/core": "1.11.3",
     "@emnapi/runtime": "1.11.3"
   }
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/npm/win32-x64-msvc/package.json b/packages/compiler/npm/win32-x64-msvc/package.json
index a4de0ee94..8e6b97c6c 100644
--- a/packages/compiler/npm/win32-x64-msvc/package.json
+++ b/packages/compiler/npm/win32-x64-msvc/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/compiler-win32-x64-msvc",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "cpu": [
     "x64"
   ],
@@ -19,4 +19,4 @@
   "os": [
     "win32"
   ]
-}
\ No newline at end of file
+}
diff --git a/packages/compiler/package.json b/packages/compiler/package.json
index b84923f19..917ed2b1a 100644
--- a/packages/compiler/package.json
+++ b/packages/compiler/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/compiler",
   "description": "Solid's native Oxc JSX compiler",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "repository": {
@@ -62,11 +62,11 @@
     "emnapi": "^1.11.3"
   },
   "optionalDependencies": {
-    "@solidjs/compiler-darwin-x64": "2.0.0-rc.13",
-    "@solidjs/compiler-darwin-arm64": "2.0.0-rc.13",
-    "@solidjs/compiler-linux-x64-gnu": "2.0.0-rc.13",
-    "@solidjs/compiler-linux-arm64-gnu": "2.0.0-rc.13",
-    "@solidjs/compiler-win32-x64-msvc": "2.0.0-rc.13",
-    "@solidjs/compiler-wasm32-wasi": "2.0.0-rc.13"
+    "@solidjs/compiler-darwin-x64": "2.0.0-rc.14",
+    "@solidjs/compiler-darwin-arm64": "2.0.0-rc.14",
+    "@solidjs/compiler-linux-x64-gnu": "2.0.0-rc.14",
+    "@solidjs/compiler-linux-arm64-gnu": "2.0.0-rc.14",
+    "@solidjs/compiler-win32-x64-msvc": "2.0.0-rc.14",
+    "@solidjs/compiler-wasm32-wasi": "2.0.0-rc.14"
   }
 }
diff --git a/packages/diagnostics/CHANGELOG.md b/packages/diagnostics/CHANGELOG.md
index 37ebea4ea..f5197c66e 100644
--- a/packages/diagnostics/CHANGELOG.md
+++ b/packages/diagnostics/CHANGELOG.md
@@ -1,5 +1,127 @@
 # @solidjs/diagnostics
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [0c550fd]
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [b07fed5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [fa371c3]
+- Updated dependencies [96c5e19]
+- Updated dependencies [9a213bb]
+- Updated dependencies [721eb06]
+- Updated dependencies [721eb06]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [365f37d]
+- Updated dependencies [b07fed5]
+- Updated dependencies [bc51ada]
+- Updated dependencies [eaddda4]
+- Updated dependencies [da84bd9]
+- Updated dependencies [d231b99]
+- Updated dependencies [98d35b9]
+- Updated dependencies [3086f1b]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [09eadfe]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [759a9b6]
+- Updated dependencies [fd9f381]
+- Updated dependencies [b07fed5]
+- Updated dependencies [fff1615]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b0bad02]
+- Updated dependencies [0c550fd]
+- Updated dependencies [2317623]
+- Updated dependencies [e345dc7]
+- Updated dependencies [4f67697]
+- Updated dependencies [2317623]
+- Updated dependencies [d1309ad]
+- Updated dependencies [924d909]
+- Updated dependencies [6be6c51]
+- Updated dependencies [41fdf96]
+- Updated dependencies [7acc039]
+- Updated dependencies [87a3862]
+- Updated dependencies [bde4299]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [1a3f87f]
+- Updated dependencies [5622be8]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0bad02]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0c8489]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - solid-js@2.0.0-rc.14
+  - @solidjs/signals@2.0.0-rc.14
+  - @solidjs/web@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/diagnostics/package.json b/packages/diagnostics/package.json
index 2d90d79c1..472017b88 100644
--- a/packages/diagnostics/package.json
+++ b/packages/diagnostics/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/diagnostics",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "description": "Agent-consumable diagnostics harness for Solid: capture the dev-mode diagnostic and attribution channels as structured artifacts, with assertion helpers for tests and agent loops.",
   "author": "Ryan Carniato",
   "license": "MIT",
@@ -52,11 +52,11 @@
     "test:watch": "vitest watch tests"
   },
   "dependencies": {
-    "@solidjs/signals": "^2.0.0-rc.13"
+    "@solidjs/signals": "^2.0.0-rc.14"
   },
   "peerDependencies": {
-    "@solidjs/web": "^2.0.0-rc.13",
-    "solid-js": "^2.0.0-rc.13",
+    "@solidjs/web": "^2.0.0-rc.14",
+    "solid-js": "^2.0.0-rc.14",
     "vitest": ">=2.0.0"
   },
   "peerDependenciesMeta": {
diff --git a/packages/element/CHANGELOG.md b/packages/element/CHANGELOG.md
index 4b4baf41b..594c728e5 100644
--- a/packages/element/CHANGELOG.md
+++ b/packages/element/CHANGELOG.md
@@ -1,5 +1,70 @@
 # solid-element
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9a213bb]
+- Updated dependencies [721eb06]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [365f37d]
+- Updated dependencies [da84bd9]
+- Updated dependencies [98d35b9]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [759a9b6]
+- Updated dependencies [e345dc7]
+- Updated dependencies [4f67697]
+- Updated dependencies [41fdf96]
+- Updated dependencies [87a3862]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - solid-js@2.0.0-rc.14
+  - @solidjs/web@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/element/package.json b/packages/element/package.json
index d79f7ff53..b29db52e6 100644
--- a/packages/element/package.json
+++ b/packages/element/package.json
@@ -3,7 +3,7 @@
   "description": "Webcomponents wrapper for Solid",
   "author": "Ryan Carniato",
   "license": "MIT",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "homepage": "https://github.com/solidjs/solid/blob/main/packages/element#readme",
   "repository": {
     "type": "git",
@@ -30,8 +30,8 @@
     "component-register": "^0.8.7"
   },
   "peerDependencies": {
-    "solid-js": "^2.0.0-rc.13",
-    "@solidjs/web": "^2.0.0-rc.13"
+    "solid-js": "^2.0.0-rc.14",
+    "@solidjs/web": "^2.0.0-rc.14"
   },
   "devDependencies": {
     "solid-js": "workspace:*",
diff --git a/packages/h/CHANGELOG.md b/packages/h/CHANGELOG.md
index 3b644fa59..f17a18c8a 100644
--- a/packages/h/CHANGELOG.md
+++ b/packages/h/CHANGELOG.md
@@ -1,5 +1,72 @@
 # @solidjs/h
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: `STRICT_READ_UNTRACKED`, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through `assign`, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason `tuple`) instead of being flattened; only `ref` merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.
+
+  Breaking: `AttributeSlot` is renamed `BindingSlot`, with no alias, and its return is constrained (`SlotOutput<J>` / `SlotError<M>`, both exported) so an array, DOM node, function, async value or `$`-prefixed key is a type error on both sides. The diagnostic code `ATTRIBUTE_SLOT_POSITION` is renamed `BINDING_SLOT_POSITION`. The fill-shape finding also names async values.
+
+- 9e85a09: `h()` no longer writes to the caller's props object, so an element can be materialized again (a `Show` re-showing children whose own children are `h()` elements threw "Cannot set property children … which has only a getter"). An `h()` element returned from an accessor child is now created in the insert's tracking pass rather than re-created whenever its output changes (an accessor returning `h(Loading, …)` over async children never settled). A function `class` on a tag with static classes (`h("span.a", { class: () => … })`) keeps the static classes. `h(...)` with element/component arguments is typed as `HyperElement`, so `render(h(App), el)` — the documented root form, now corrected in the README — type-checks.
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [721eb06]
+- Updated dependencies [365f37d]
+- Updated dependencies [98d35b9]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [4f67697]
+- Updated dependencies [41fdf96]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - @solidjs/web@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/h/package.json b/packages/h/package.json
index b253d3999..2bddf4480 100644
--- a/packages/h/package.json
+++ b/packages/h/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/h",
   "description": "Hyperscript / h() factory for Solid — write components without compiled JSX.",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "homepage": "https://solidjs.com",
@@ -58,7 +58,7 @@
     "test": "vitest run"
   },
   "peerDependencies": {
-    "@solidjs/web": "^2.0.0-rc.13"
+    "@solidjs/web": "^2.0.0-rc.14"
   },
   "devDependencies": {
     "@solidjs/web": "workspace:*",
diff --git a/packages/html/CHANGELOG.md b/packages/html/CHANGELOG.md
index c54434c72..17346b84c 100644
--- a/packages/html/CHANGELOG.md
+++ b/packages/html/CHANGELOG.md
@@ -1,5 +1,69 @@
 # @solidjs/html
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- a5d0e76: Zero-argument functions passed to component props named `on`, `only`, `once`, etc. are now wrapped in getters like any other dynamic prop (#3728). The `on*` exemption on components now covers only `onXxx` handler names (an uppercase letter after `on`), so `<${Loading} on=${() => key()}>` re-keys the boundary when `key()` changes. Native elements are unchanged: every `on*` prop is still passed through as an event handler. A lowercase `onclick` passed to a component is now wrapped in a getter; name it `onClick` or give the handler a parameter.
+- 6be8486: Fix the tokenizer staying in raw text mode after a self-closing raw text element such as `<textarea />`, which swallowed the rest of the template as text.
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [721eb06]
+- Updated dependencies [365f37d]
+- Updated dependencies [98d35b9]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [4f67697]
+- Updated dependencies [41fdf96]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - @solidjs/web@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/html/package.json b/packages/html/package.json
index f3bff004e..e2d2e5ab7 100644
--- a/packages/html/package.json
+++ b/packages/html/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/html",
   "description": "Tagged-template-literal templating for Solid — write components with no build step.",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "homepage": "https://solidjs.com",
@@ -42,7 +42,7 @@
     "test": "vitest run"
   },
   "peerDependencies": {
-    "@solidjs/web": "^2.0.0-rc.13"
+    "@solidjs/web": "^2.0.0-rc.14"
   },
   "devDependencies": {
     "@solidjs/web": "workspace:*",
diff --git a/packages/signals/CHANGELOG.md b/packages/signals/CHANGELOG.md
index 340a5de51..2fd33b710 100644
--- a/packages/signals/CHANGELOG.md
+++ b/packages/signals/CHANGELOG.md
@@ -1,5 +1,89 @@
 # @solidjs/signals
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- 0c550fd: A render effect still on screen while an action holds its removal follows the lane's re-derivation of a memo it reads, as its direct `latest()` twin does (fuzzer adopted-staging case)
+- ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: `STRICT_READ_UNTRACKED`, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through `assign`, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason `tuple`) instead of being flattened; only `ref` merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.
+
+  Breaking: `AttributeSlot` is renamed `BindingSlot`, with no alias, and its return is constrained (`SlotOutput<J>` / `SlotError<M>`, both exported) so an array, DOM node, function, async value or `$`-prefixed key is a type error on both sides. The diagnostic code `ATTRIBUTE_SLOT_POSITION` is renamed `BINDING_SLOT_POSITION`. The fill-shape finding also names async values.
+
+- b07fed5: A born-held render effect re-run as lane work (a `latest()` reader remounted during an action's hold) re-stages its value, so the commit applies the latest pass instead of the stale born-held one (fuzzer F13).
+- 21ff8f8: Infer `createEffect` and `createRenderEffect` compute results as const so inline tuple results retain their element types without a type argument or `as const`.
+- 1b9ceb6: Size audit (measurement branch): a derived store's derive reading a key (or container) a transaction holds through its draft — a user's write inside an action, held with it — joins that transaction, so the derive's whole result reveals with the action rather than key by key (core R31 / #3733: "under the transaction and revealed with it"; the `derived-write-then-derivation-3733` action-hold pin). A user setter reading its own draft is no pass and joins nothing.
+- fa371c3: Compare optimistic store writes against the committed backing frame of chained stores, so a writable derived store's held staging cannot suppress an optimistic override.
+- 96c5e19: A derived store that returns rows from its own draft no longer recurses forever when its source refreshes: the projection draft wrapper resolves to its store proxy wherever the result carries it, so a retained row keeps its identity and stays readable, and an equivalent refresh doesn't re-notify its readers.
+- 9a213bb: Derived writes apply first, then derivations re-run. A manual write to a writable derived value (`createSignal(fn)`, `createStore(fn)`) lands at once; when one of its sources changes — in the same update or later, inside or outside an action, across async holds — the function re-runs and receives the write as `prev` (or as the draft for `createStore(fn)`), and decides what to keep. A write on its own never re-runs the function.
+
+  This reverses beta.11's same-tick precedence (#2692), where a write beat a source change in the same flush: a function that ignores `prev` now discards a write made in the same update as a source change, and a same-value write no longer holds against it. To keep a local value across source changes, carry it in the data as a flag the function honors. It also fixes #3733 (a write inside an action blocked later source changes for the whole hold, a regression since #2692) and supersedes the frame-scoped mask from #3740, whose changeset this replaces.
+
+- 721eb06: Attribution cost checks judge only what the scope's author can act on (#3739). `WIDE_SCOPE_DEPS` no longer counts HMR plumbing sources (the `solid-js/refresh` memo per component instance), skips framework scopes marked with the new internal dev-only `_wide` option (`CONFIG_WIDE`; not public API), and its `wideDeps` default rises from 30 to 200. The engine-side `HUGE_FAN_OUT` (`fanOut`) no longer counts plumbing subscribers. The always-on `HUGE_FAN_IN` and core `HUGE_FAN_OUT` (2000) keep no exceptions.
+- b07fed5: A render reader whose pass errored (NotReady included) before reaching a flight it read last time still holds that flight's transaction: a write no longer shows beside a reader still derived from the previous value while the flight is in the air (fuzzer F4).
+- bc51ada: A new async memo created over a held update now waits for it (#3800). A memo created while a transition holds a value, whose first pass reads that value and returns a promise, lands its first answer into the transition and reveals at its commit, as the same memo with a synchronous first answer already did. Before, the promise landed on its own and its readers showed the new value beside the rest of the page still on the old one. The transition never waits for the new memo's first load: if it lands after the transition commits, it is its own commit.
+- eaddda4: Fix false `GRAPH_GROWTH` warnings caused by the initial route declaration, which runs before page content mounts. The detector now compares completed visits while still emitting the initial graph record.
+- d231b99: An optimistic store over a store reads a property the inner store's reconcile removed as `undefined` instead of its last value (#3883)
+- 3086f1b: Fix an infinite flush loop ("Potential Infinite Loop Detected") when a `latest()`-gated `Show` mounts a fresh `Loading` under an action hold: lane work that reads a node born staged is no longer re-queued to re-derive on a committed value it doesn't have.
+- 3c7631a: ABANDONED_FLIGHTS no longer fires for a frames slot arg that every re-shipped record re-reads while it is still pending (#3852). Dev builds mark the per-key slot-arg memo with an internal option that the check skips; the memo's flights are still recorded and still counted in `feedback()`.
+- 09eadfe: A fresh `Loading` mounted over a held value shows its fallback in a flush too (#3540 under L2): a first pass a loading boundary that has not shown content catches is the boundary's, not the tick's, so the mount publishes and the content reveals at the commit. Content bound by a render effect under the boundary is collected, so the boundary no longer reveals empty content.
+- be82cf3: Observe: one interaction frame per event, not per listener. `InteractionRef` takes an optional `event`; frames with the same `event` re-enter one interaction record, which stays joinable for the event's dispatch and is recorded at the next task. The web runtime keys its frames by the DOM event, and `@solidjs/web` exports `dispatchAsInteraction(e, fn)` so a listener outside the runtime (a router's `document` click handler) joins the frame of the same event — `fn()` in production builds. One anchor click is now one interaction record carrying both the `onClick` work and the navigation (#3754).
+- fd9f381: Fix L2 lane regressions found by the semantic fuzzer: a lane dissolving with a node still in flight marks it as committed beneath published inputs, so a mount or verdict reader observes the flight instead of being served a value that tears against them; a correction of a blocked lane drops the re-guess runs it parked instead of releasing them; and a lane pass's pending propagation no longer lists a born-held or mid-pass mainline render effect on the lane, so a mount over a memo of a lane flight is born held, control and content together.
+- b07fed5: A landing whose commits dispose a zombie re-judges the transactions parked at the same seam: a write held only because that zombie observed its flight now lands with the commit that disposes it instead of staying unpublished until an unrelated flush (fuzzer F3).
+- fff1615: A lane now holds through a `Loading` boundary showing content: a boundary output forwarding its tree's pending counts as a frame reader, so `latest()` no longer reveals beside the boundary's stale content (A33). An output that never committed — a mount the frame has not revealed — holds nothing. A corrected guess that never showed is void at the correction: untracked reads return the committed value (A18 amendment, 2026-10-05).
+- 11e9fb6: An element an optimistic guess mounts now lands together with its bindings (#3835). A first pass created by a guess's lane reads as the lane's, not just routes as it: a binding the lane mounts reads a write the action still holds as the screen (its committed value) and re-derives when the action lands. Before, a binding inside a memo the lane created was born held while the memo's element showed, so `<div>Hello</div>` appeared without its `style` until the action finished; directly under the lane pass the binding showed the held value early instead.
+- 11e9fb6: A `Loading` mounted by an optimistic write over a flight shows its fallback again (#3835's seat regressed it). Lane work with no committed value yet reads a pending flight the way a mainline mount's memo does: it enters and throws, so the boundary it mounts catches the pending (A29's boundary exemption), instead of being served the flight's committed value. A render effect is still a stale reader of a held flight (rule 3). Approach and tests from #3843 by @brenelz.
+- b0bad02: A lane's node inside a held frame stays the lane's: `holdFrame` no longer re-lists a verdict reader (or a derivation of a guess) created under a held pass on the frame's transaction, where the landing nulled its transaction with its lane value still on and the next read of it crashed (`laneRead` → `txOf(null)`, `REACTIVITY_HALTED`) — a `Loading` over `latest(x)`, or a memo of `isPending(() => x())`, unmounted and remounted while `x` is held (fuzzer F7a/F7b; A15 #3698: lane work never makes its node transaction work).
+- 0c550fd: A mainline mount whose child reads a lane derivation in flight shows the child as a stale reader beside its mount control, whether or not the lane is held (fuzzer F8)
+- 2317623: Fix a render effect a lane took over from a held transaction: it keeps running as the lane's work while it waits on the lane's flight, and drops the hold when it leaves the lane (#3766).
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
+- 2317623: Fix an optimistic store over a derived store hiding its update after an action's local write to the same row: the row a held write staged is no longer guessed over the container's slot (#3796).
+- d1309ad: Resolve a writable derived store's retained draft row to its store proxy when an optimistic store chained over it writes, so the optimistic write to that row shows while its action is pending (#3859).
+- 924d909: A store fold's presence notification (`in` subscribers) now diffs the old and new presence of each observed key before writing the node, as the value notification already does (#3743). `setSignal` joins a held node's transaction before its equality gate (A34 (1): a write to a held node is a proposal, the same value or another), so a `reconcile()` outside an action that had deleted an observed key — the incoming snapshot leaving it absent too — made the whole tick the action's: an unrelated `a.value` stayed stale until the action settled. A real presence change still notifies and still proposes on a held node.
+
+  The adoption's diff base now materializes a nested prototype-overlay draft (a wide owned record) before it is taken: through the overlay's prototype a key the draft had deleted still read as present, so the presence skip fired on a real deletion and a reconcile restoring the key never re-proposed on the held leaf (it committed the draft's `undefined` beside a backing that had the key).
+
+  Two optimistic-store fixes the diff uncovered: a container carrying an arrangement guess is now told of an arrangement change whether or not anything subscribes to the container (for a guessed container the write is the landing that judges the guess — before, only the unconditional presence write reached the lane, so a newer question's rows landing beneath an optimistic push published beside it when the reader subscribed to leaves only); and an older truth re-based under an arrangement guess no longer re-stages a slot whose row the committed backing already shows by key, nor an unchanged `length` (a spurious frame for leaf-only readers).
+
+- 6be6c51: Remove the empty carved module reexport that caused TS2306 during the Signals build.
+- 7acc039: A render effect created while an action holds a value it reads no longer runs its callback when a later pass re-stages it before the action lands (#3802). That run passed `undefined` as the value, because the effect had nothing committed yet, so compiled JSX bindings threw and halted reactivity. The effect now runs once, at the commit that lands the action, with the latest staged value.
+- bde4299: The seam (`settle`) no longer pays the effect-queue merge on a plain flush — nothing parked, no lane reveal, no landing: this flush's runs are the queue as they stand instead of a `concat` copy, a parked flush stashes its runs in place, and the per-flush list resets run only when a list is non-empty. About 100 ns less fixed cost per flush (−11% on a 20k-key store commit, −45% on a one-signal flush), with the effect order of every other seam unchanged.
+- 1b9ceb6: Size audit (measurement branch): `affects()` rebuilt on the L2 hold model as ruled (A24 (4), the #2893 audit) — a declared in-flight change that lights up `isPending` on the marked accessor and its derivations for the surrounding transaction's lifetime; never a hold, never an entanglement, never a suspension. A count on the node, listed with its scope; coverage pull-derived at probe time; verdict readers re-derived at registration and release. The store targets return with the stores. Also: `GlobalQueue`'s hook statics are `declare static` (type-only) — they emitted as `static X;` on every bundle.
+- 1b9ceb6: Attribution on the L2 hold model: the observe-tier engine is fed from the rebuilt lane and verdict layers again (hold census — blockers, optimistic/affects/isPending/latest acknowledgements; optimistic reverts labelled superseded vs reverted; loading-boundary fallback show/hide records; run posture). A lane derivation's first landing no longer trips the dev `SETTLE_WALK_UNINITIALIZED_SOURCE` tripwire.
+- 1b9ceb6: Size audit (measurement branch): the reactive engine rebuilt on the L2 hold model — transactions as the one hold relationship (membership, `blocked`, frame reads, born-held), with lanes (`createOptimistic`), verdicts (`isPending`/`latest`), boundaries (`createLoadingBoundary`/`createErrorBoundary`), `createRevealOrder` and `action` rebuilt on it as modules behind `GlobalQueue` hooks; stores, `affects()` and the attribution engine carved out pending their own steps. Every step is measured on the whole size suite and recorded in `documentation/plans/size-reduction-carve-step1.md` (§1–§28), with the maintainer's rulings that decided each behavior. Checkpoint before the §28 replay of the lane layer.
+- 1b9ceb6: Size audit (measurement branch): carve the lane layer — `createOptimistic`'s write, `isPending`, `latest` — ahead of its rebuild from the §28 principles (`documentation/plans/size-reduction-carve-step1.md`). The layer measured 1775 B br on `+ isPending/latest` and 1809 B br on the live page as built.
+- 1b9ceb6: Size audit (measurement branch): the lane layer rebuilt from the §28 principles (S0 skeleton). A node's value lives in one of three places — `_value` the committed truth, `_pendingValue` a transaction's staging, `_x._lane` the lane's value — and the lane transaction carries the shown/held state (`_shown`, `_held`); the seat of a pass is its node's; leaves read the screen; the body-end correction runs at the seam with one more pure round so its re-derivations are the parent's; a dissolving lane retires the void world's flights. Removes `CONFIG_LANE_HELD`, `CONFIG_HELD_TRUTH`, `REACTIVE_VERDICT_RERUN` and the seam-time value swap. Fixes #3409 (indicators of a body-end correction clear together) and the #3698 held-lane children case. Design and results in `documentation/plans/size-reduction-carve-step1.md` §28.
+- 1b9ceb6: Size audit (measurement branch): §28 S1 — holds and seams on the rebuilt lane layer. A render effect reading a lane flight that has never shown waits on it in its own frame and reads the landed answer at the landing (A15 LANE, #3334); a zombie's say is moot only for the transaction that disposes it (#3463); a lane-derived value committed at a dissolve publishes its inputs (#3648); a boundary re-armed through a display-ahead read swaps as the lane's from the head (#3540); any stale reader of a flight holds it, lane work included (V5/A17).
+- 1b9ceb6: Size audit (measurement branch): §28 S2 — verdicts and consolidation on the rebuilt lane layer. The verdict watchers merge into the lane layer's staged-readers list (one seam, one rule: a pass that read this flush's staging as the screen re-derives if the frame parks); one `staleReader` registration shared by frame reads, lane reads and verdict routes; `dissolveLane` restructured by outcome, every guess of a dissolving lane re-homed with its truth. No behavior change; 0 pins moved.
+- 1b9ceb6: Size audit (measurement branch): the spec pass. `SPEC-ASYNC-SEMANTICS.md` gains "The hold model — L2 (2026-10-04)" — the carve's rulings in the spec's voice, the 2026-10-03 re-pins, and a mechanism note (the per-rule "Mechanism (index, 2026-09-14/15)" paragraphs describe the pre-L2 implementation; the L2 module map is the cross-reference) — with dated amendments on A18, A19, A22, A29 and A34. `INTERNALS-ASYNC-STATE.md` gains "0. L2 — the hold model: what replaced §1–§4". `RULES-INDEX.md` regenerated; plan-section citations in `src/` comments are written `plan sec. N`. Comment-only in source.
+- 1b9ceb6: Size audit (measurement branch): §41.4 benchmark fixes. A plain pass already marked as having read this flush's staging reads an unheld container staging directly — the per-key "did this key change" question is asked once per pass, not once per key (a `mapArray` over 1k shifted rows asked it 1k times; store array ops `splice`/`shift`/`unshift`/`reverse`/`push` on 1k proxied rows now at parity with `next`). At the fold, a child whose parent was adopted whole no longer re-resolves its slot by an O(rows) `indexOf` that cannot hit (the slot already holds the child's new backing).
+- 1b9ceb6: Size audit (measurement branch): §41 benchmark fixes. A derived store's family settle walk runs only after a wake (`fam.woke`), not on every sync commit — a 1k-row derived store's no-op re-derive was walking every leaf (14× the fork). A value read under a staging asks only whether the key's value or presence changed (`readSource(target, key, shape)`); descriptor readers and hold decisions keep the full enumerability/accessor test, as does any container with accessors seen. Keyed reconcile of 1k rows read by `mapArray` in the staging flush: 2.5× faster.
+- 1b9ceb6: Size audit (measurement branch): §41.5 — the container node's escape hatch (Q-A). A store staging gets its container node only when something can read the frame through it: a structural subscriber, lane work, a creation-time pass, or a derive a transaction holds. Otherwise the backing swap and the fold queue are the whole staging — nothing is allocated, queued or swept per container — and when a flush parks, the seam materializes and holds the node for every node-less staging (`_storePark`), so a never-read key of a held container still reads committed until the landing (pinned). The fold queue itself no longer allocates per batch: a reusable list plus a weak map of pre-batch backings written in place (a dbmon tick's ~7000 containers cost ~540 KB of map table per tick before). dbmon-deep tick 1.17–1.19× → 1.08–1.13× by the harness's own method; node parity.
+- 1b9ceb6: Size audit (measurement branch): the fold queue records a pre-batch backing only for adoptions (whose backing swaps eagerly), in a weak map written in place batch after batch; a draft's pre-batch backing is its own committed backing, so nothing is recorded for it — 2000 fresh one-key stores per flush had cost 2000 weak-map insertions and ran at 2× `next` (CodSpeed's `fresh stores` bench). The two rare moves of a draft's backing mid-batch (a privatization, a draft over an adopted raw) are kept in small per-batch maps.
+- 1b9ceb6: Size audit (measurement branch): §40 S3c — projection verdict windows and family pending on L2; the promise-delivery readers by posture. A probe answered before the flush had a transaction re-runs at the seam even when a later read routed its pass into the verdict lane (`REACTIVE_PROBE_UNANSWERED`); a render effect already observing a derive's flight keeps pulling it on re-run (the frame's hold is not dropped with its flight still up); the post-pass family wake fires only for a flight this pass registered (#3181); a derive's rejection reaches its leaves' readers (`handleAsync` gains an `onError(error, pending)` seam; `errorFamily`). `wakeFamily` stamps leaves with the derive as a pending source and propagates through core's own `propagateStatus` (split out of `notifyStatus`): branch recovery stays pending through another path, pending render effects are held by the frame. A `refresh()` during a non-quiet flight does not launder the new question; a quiet flight's landing writes are quiet through their reveal on stores. `resolve`/`until`/`refresh`'s waiter deliver their own transaction's frame and, over a foreign hold, the committed view at its commit (#3482/#3490). The descriptor trap reads the backing the container's frame serves (#3706). Four pins re-ruled onto L2 / signal parity (plan §40.2): A22-3, #3662 step 1, #3585 never-resolving case, #3038 companion walk.
+- 1b9ceb6: One provenance test for a derivation's landing and a written landing alike (`stale`); signal/store twin pins for the overlapping-actions and kanban shapes.
+- 1b9ceb6: Optimistic stores: a landing is judged against the guess of the question it answers. Another action's landing beneath a guess is held beneath it (the truth for the commit), the guess keeps showing, and the guess's own landing judges it; an arrangement guess on a keyed list is re-based over the held truth by key (order from the guess, rows from the truth, new rows appended, rows the setter removed stay removed). Two overlapping list edits confirming out of order no longer snap back. A corrected lane that had shown keeps the runs it queued this round; a chained view's guess reverts against the inner store's live value.
+- 1b9ceb6: Stores on L2, S1: plain `createStore` returns (`snapshot`, `deep`, `storePath`, `isWrappable`, `markRaw`, `$TRACK`/`$TARGET`/`$PROXY`/`$RECORD`, `storeIsShallow`). A store is a tree of L2 nodes: one-literal slot nodes (`slotSignal`) for leaves, presence, deep witness and the container node — the `$TRACK` node given a value, whose staging is the pending backing, so the scheduler owns the backing's lifetime. Core: the slot-node sweep dispatch and the store commit hook; `_devWindows` becomes an observe-literal slot; `mapArray` reads `$TRACK` again. Derived stores, projections, reconcile and optimistic stores return on later steps.
+- 1b9ceb6: Stores on L2, S2: plain stores under holds. Every leaf read is core's `read()` (the hold rules — frame reads, joins, A28 — come from core, tracked or not); nodes are born from the two frames and held by the container's transaction only for keys the batch changed (#3706); structural reads take the container's frame; a setter's returned replacement is staged, not eager. Core: `read()`'s held arm now applies to untracked reads by a pass (a derivation of a held write is never published mainline — A29/A15).
+- 1b9ceb6: Stores on L2, S3a: `createProjection`, `createStore(fn, seed)` and `reconcile` return. The firewall is projection-only and lives in the store: every read through a projection pulls the derive first (core `read()` of it — untracked when settled, so nothing subscribes to the derive; tracked while a flight is up, so readers observe it as a memo's would); pending propagates to leaf readers by core's own dependent rule and settles at the landing; a derive's continuation writes join its hold; the creation run commits directly; adoption is eager with the container node keeping the committed frame. Core: the self-registered-flight probe in `recompute` is restored (projection-only, carved by mistake); an untracked verdict read of an uninitialized pending node links its reader as `read()` does. Derived-store manual writes follow A34 rule B (re-pinned).
+- 1b9ceb6: Stores on L2, S3b: holds on derived stores. A pass reading a key a held batch left unchanged reads committed and holds no one (#3706); a mainline setter above a held adoption publishes mainline for the keys the hold did not change (#3688); a user write to a key whose staging is a held derivation becomes the draft's prior state and the hold re-derives over it (A34 (3), #3612 — `CONFIG_MANUAL_WRITE` discriminates a user's proposal from the derive's derivation).
+- 1b9ceb6: Stores on L2, S4: optimistic stores on lanes. A user write to an optimistic store is a guess on the written key's node (presence and container arrangement guesses alongside), shown under the action's hold, confirmed or corrected by a landing beneath it, dissolved at settle — no store-side layer or backup snapshots. The committed backing is never touched by a guess. Reads compose per key through the nodes; a guess over an in-flight derive stands in for the flight (A17). Chained views (`createOptimisticStore(base)`) keep their links on the inner store's truth. A user's `reconcile` on an optimistic family writes the draft. The optimistic machinery is late-bound: a plain store does not carry the lane layer. Core: a slot node's flight is its family's derive (`_slotFlight`); an untracked read inside lane work derives from the lane; a pass that joined a hold before its first lane read is re-derived on the screen; linked lanes are judged by `blocked`; a supersession resolves the lane's merged parent.
+- 1b9ceb6: Store size pass after S4: the write override is a live binding (no accessor call on the `get` hot path); the optimistic draft and its set-aside staging live in the optimistic module; one predicate for the lane-view composition sites. Behavior unchanged.
+- 1b9ceb6: Stores on L2, S5: the store half of `affects()` — `affects(store)` marks the record's carrier and every live node under it, `affects(record, key)` the slot's leaf; coverage by raw identity (captured proxies, chained views, cross-family raws), nodes born in the window inherit the mark, untracked probes are witnessed. Ambient marks whose flush parks join its transaction; one over a node whose own flight is up (a declared reload) lives to the landing. `StoreNode` is exported again (the L2 target's shape).
+- 1b9ceb6: Stores on L2, S-U: `merge`/`omit` and the merge/omit view machinery (`utils.ts`) are back unchanged; the carve has no stubs left.
+- 1a3f87f: Store fold queue: the pre-batch committed backing is recorded beside the queued target and released with the drain. The weak map it replaces kept every container's last adopted-away backing alive until its next adoption — for a keyed reconcile, the previous tick's whole tree promoted out of the nursery every tick (the saturated listened-paths and reconcile-tree shapes ran 10–15% over `next` on that alone); for a store adopted once, the old tree for the store's lifetime. The per-batch side maps for mid-batch privatizations and drafts over adoptions fold into the same record.
+- 5622be8: `UNSTABLE_MEMO_OUTPUT` compares symbol-keyed properties too, so a memo returning a fresh symbol-keyed box each run (as `dynamic` does for an in-flight promise) is no longer reported as new-but-equivalent.
+- 11e9fb6: A mount made by a verdict reader stays mainline (#3851). Inside an action, `<Show when={latest(x) > 0}>` opens at once, but a `<Loading>` it mounts used to show `content 1` beside the committed `x = 0`: the content's first pass was staged in the verdict lane its creator was in, and in the action's own flush it read the staged `x` before the seam held it. A first pass now takes its creator's lane only for an optimistic lane (head and tail of its pass alike); a mount a verdict lane makes whose first pass reads a staging of a flush with a transaction is born held like one that read a held node (other new memos do not join the transaction by being created); and verdict-lane work that read the frame's stagings re-derives on the committed world when the frame stays parked. The boundary shows its fallback and `content 1` at the landing.
+- b07fed5: A memo pulled by an `isPending`/`latest` probe computes as its own pass, outside the probe's window: it no longer caches the committed input in place of a flushed write (fuzzer F10), or reads an uninitialized input as `undefined` instead of suspending (F11).
+- b0bad02: A verdict reader that reveals a flight nobody holds registers it with the frame (A15 first observer, #3458): `observeFlight` holds the flight's node in the frame's transaction, so the transaction waits for the landing instead of holding nothing, landing at its own seam and re-deriving the reader into the same observation every flush ("Potential Infinite Loop Detected") — an action whose body-end write re-asks an async memo as its verdict lane's work, revealed to a `latest()` reader the action adopted (fuzzer F12), or any memo re-asked unobserved and then revealed to a reader using `latest()`/`isPending()`.
+- b07fed5: An `isPending` reader of an async memo settles when the memo's flight lands equal to its committed value: the settle walk re-derives the verdict reader instead of leaving it `true` (fuzzer F9).
+- b0c8489: A re-run that commits `undefined` is no longer counted as waste. A projection that mutates its draft or reconciles a returned value, or a memo that does its work by writing a signal, has no output to compare, so its re-runs were reported as pure cost. `RerunEvent.changed` now reports `true` for these runs (as it already did for side-effect-only effects), so `WASTED_RECOMPUTE` no longer fires for them and `costs().wastedMs`, `expectNoWaste` and the performance tracks stop counting them as wasted.
+
 ## 2.0.0-rc.13
 
 ## 2.0.0-rc.12
diff --git a/packages/signals/package.json b/packages/signals/package.json
index 5bb91708d..37323ac02 100644
--- a/packages/signals/package.json
+++ b/packages/signals/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@solidjs/signals",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "description": "Solid's reactive primitives: signals, memos, effects, stores, and async-aware computations.",
   "author": "Ryan Carniato",
   "license": "MIT",
diff --git a/packages/solid/CHANGELOG.md b/packages/solid/CHANGELOG.md
index cc5112f5e..1529cfb3e 100644
--- a/packages/solid/CHANGELOG.md
+++ b/packages/solid/CHANGELOG.md
@@ -1,5 +1,107 @@
 # solid-js
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- 4b4c2cb: A server `<Loading>` whose creating pass is disposed (an `<Errored>` retry re-rendering its children) now stops retrying instead of looping until "did not converge". A boundary re-created under the same fragment id owns the fragment, so the abandoned instance never settles it with blank markup; with no successor, the abandoned instance releases its fragment so the response still ends.
+- 21ff8f8: Infer `createEffect` and `createRenderEffect` compute results as const so inline tuple results retain their element types without a type argument or `as const`.
+- 3c1d512: A fill that claims adopted markup reads the state the server rendered it from (frames-rulings 3.6 (iii), "the consumer parks" — S1's third commit ported onto `next` without its `claiming` hint).
+  - `materializeContainerTrace` parks a replayed backlog beyond the snapshot until hydration ends (`onHydrationEnd`; the next microtask when no hydration is in progress) and then applies it as one ordinary update. A container trace is materialized at a fill's arg-read; when that fill claims server markup — the document's pass, a frame's deferred claim under its hold, a claim at a fragment's reveal after hydration-done — the snapshot is what the markup was rendered from, the claim trusts the markup (a text hole is never rewritten during a claim), and a store already past the markup left the DOM diverged for good. Parked, the claim reads the snapshot and the backlog lands after it, so the DOM catches up outside hydration. The release order is the one 3.2 pins: the claim, the frame's hold release, done, then the backlog. A fresh mount pays one beat for not being told apart: its backlog lands a microtask after its snapshot, before any paint. A failure in the backlog applies in order, after the parked patches.
+  - The materializer creates its projection under a DETACHED root. Rooted under the reading owner — during hydration an id-carrying one — a trace revived at t=0 consumed one child id per trace while one revived by a late claim consumed none, and a keyed sibling after the frame hydrated under different keys in the two runs.
+
+- 9a213bb: Derived writes apply first, then derivations re-run. A manual write to a writable derived value (`createSignal(fn)`, `createStore(fn)`) lands at once; when one of its sources changes — in the same update or later, inside or outside an action, across async holds — the function re-runs and receives the write as `prev` (or as the draft for `createStore(fn)`), and decides what to keep. A write on its own never re-runs the function.
+
+  This reverses beta.11's same-tick precedence (#2692), where a write beat a source change in the same flush: a function that ignores `prev` now discards a write made in the same update as a source change, and a same-value write no longer holds against it. To keep a local value across source changes, carry it in the data as a flag the function honors. It also fixes #3733 (a write inside an action blocked later source changes for the whole hold, a regression since #2692) and supersedes the frame-scoped mask from #3740, whose changeset this replaces.
+
+- b0c6e6a: Add the missing diagnostic guide sections so every diagnostic code links to its repair guidance.
+- da84bd9: Fix hydration adoption throwing when a traced compute calls `Promise.withResolvers()` or `Promise.try()`. The trace run swaps the global `Promise` for a never-settling mock that lacked these two statics, so the call threw out of hydration instead of adopting the server value. The mock now provides both: `withResolvers` returns a never-settling mock with no-op `resolve`/`reject`, and `try` returns a never-settling mock without invoking its callback (matching how the mock's constructor ignores its executor).
+- 3c1d512: Frames A5′ — a deferred fragment's placeholder inside a server component's element is the frame's content by rendering, not by adoption (frames-rulings 3.3, ruled 2026-10-06).
+
+  **`solid-js`:** the document fragment ledger's `fragmentPolicy` lets a post-done swap proceed when the fragment is owned — its `pl-*` template is in the document and the integration's ownership predicate `_$HY.fa(placeholder)` says so — beside the existing claimant case; no hold, no replay for owned fragments. `_$HY.fr.claim` / `_$HY.fr.release` are removed from the published ledger (`_$HY.fr` is `{ pending, subscribe }`); `_$HY.fa(placeholder): boolean` is the new integration hook. `fragmentPending` now reads a revealed fragment from its swap record (`_$HY.v`) before its `_fr` stamp: the producer emits the swap script and then the `_fr` settle in the same batch, so a `_$HY.fr.pending()` read inside the reveal notification saw the revealing fragment as still pending — a page's last reveal never read as exhaustion and a waiter released on exhaustion waited forever.
+
+  **`@solidjs/web` (frames client):** installs `_$HY.fa` once (`pl.closest("[data-fid]")`, minus elements of a boundary disposed in place — C14); deletes `claimRegionFragments`, the per-adoption claim set, the cascade's claim half and the release loop (the dev-only rejection report over the region's `pl-*` templates stays, 0 prod bytes); `documentBoundary` pends on the intercept's one arrival answer (`awaitBoundary`) and `boundaryWaiters` is deleted (G9). A post-done swap into server-component markup no client has adopted yet now lands at once; the adoption that follows finds it in place and reads its declared records synchronously.
+
+- 3c1d512: A server `<Loading>` inside a server component that fails after the first flush renders the server's outcome into its fragment instead of a blank (C12 (c), frames-rulings 3.3): the nearest server `<Errored>`'s fallback for the error, at the `<Loading>`'s position (asked through the boundary error handler's new `outcome` mode; a `<Loading>` between passes the question up); with no server `<Errored>` the error escapes the component — the frame's own `:error` on the stream face (an unkeyed `error` chunk), a frame-addressed `{ type: "error", fid, error }` op on the document face's `sc:live` channel (only the owning adopted boundary applies it) — and the position keeps the boundary's own fallback. `_fr` still rejects and the keyed error chunk still rides (the diagnostics). Outside a server component nothing changes (the blank the client twin renders fresh over). `HydrationContext.registerFragment`'s resolver gains a third argument (`escaped?: { frame?: string }`) and the context an internal `frameId`.
+- 3c1d512: An adopted frame occurrence claims its server markup by re-entering hydration the way a streamed `<Loading>` resume does (frames-rulings 3.1 / 3.2, the savings plan's A2 — S-hold's window form).
+  - `solid-js`: `hydrateWindow(id, fn, scope?)` is factored out of a streamed boundary's resume and reached as `sharedConfig.hydrateWindow` (`@internal`): the keys under `id` gathered into the registry (the captured `scope` pair when another `hydrate()` root replaced the live one, #2917), hydrating on for the synchronous window, the current owner the claim owner (a render the window forces elsewhere is a client render, #3504), the owner the window's snapshot and live scope when none is open — so a write during a late claim is held and replays once the claim is over, and a late claim no longer re-marks the root's scope. `sharedConfig.claimRoots` (`@internal`) is typed: the claimant declares a range that may be detached around its window. `holdBoundary` stays the registration; the resume path is unchanged in behaviour.
+  - `@solidjs/web` (frames): `claimRender` is the window — one `createOwner({ id: prefix })` and the call — instead of a registry of its own gathered by walking the range, a hydrating flag flipped through `sharedConfig`'s setter (which reset hydration-done and re-ran its completion from outside the runtime), and a hand-over of keys from the root registry: `gatherClaims` and `hasPendingFragment` are deleted (the window gathers by the producer prefix and always engages). `adoptBoundary` captures the registry/gather pair it adopts under so a claim made long after — under the frame's hold, at a fragment's reveal — gathers against the root that holds the frame.
+  - `@solidjs/web`: `gatherHydratable`'s prefix-scoped gather selects its keys natively (`[_hk^="…"]`) instead of sweeping every `_hk` and filtering in JS — it now runs once per adopted occurrence, not only per late resume.
+
+- 9d89df7: Hydration-done counts the frames client's holds (frames-rulings 3.1, ruled): an adopted occurrence the frame has not claimed yet — waiting for its args record or a `{$ref}`'s data — registers as a pending boundary through the same registration a streamed `<Loading>` resume takes (`sharedConfig.holdBoundary`, internal), so `onHydrationEnd` and `isHydrationInProgress()` mean the same thing with or without server components (contract C3 a).
+- 7233451: frames: the container-trace materializer is the frames client's traces tier — `@solidjs/web/frames/trace`, loaded through the server-announced tier mechanism (`prepareTier("trace")`), so the store engine leaves every server-component page that never meets a trace (page base −6.6 KB brotli, page live −6.7 KB; frames eager −83 B). `solid-js/internal/container-trace` is a new `solid-js` entry carrying `materializeContainerTrace(marker, claiming?)` (the store engine reached through `@solidjs/signals`, the hydration dispatch `withStoreHydration` and the patch protocol read back from `solid-js`); the materializer leaves `solid-js`'s main and `solid-js/internal` entries. The eager frames client keeps the trigger: the loader entry, the held-set predicate (an adopt-time record whose args carry a `{ $tr }` marker while the tier is absent is held under frames-rulings 3.1 — its server interior on screen, hydration-done waits — and mounts with the record it was held on, a replacement applying as an args change), and the `claiming` hint (`FrameHostOptions.revive(value, claiming?)`), which keys the materializer's parked backlog on the claim again: a fresh mount reads the fold of its whole backlog at once.
+- 759a9b6: A server memo re-created at a still-pending slot now takes the slot's answer when the earlier flight settles it (#3815). A retry pass that re-creates a component while its async memo is in flight hands the new memo the slot's shared deferred, but only the earlier memo's promise settles it, so the new memo kept its `NotReadyError` on that already-resolved promise. A memo reading it then retried every microtask, so no timer fired again, the stream never ended and the process sat at 100% CPU. On rc.13 the trigger was a function hole that created a component returning a pending `lazy()` view. On `next` it is an `<Errored>` retry that re-creates a pending `<Loading>`, with a fresh promise per setup and a memo reading it. The joined memo now adopts the slot's value or error when the shared deferred settles, the same way a re-created async-iterable node already did.
+- e345dc7: A live source whose server value is still streaming when the root hydration pass ends now takes over when hydration ends, not when the root pass ends. A source with a `loadingValue` keeps taking over when the root pass ends: its markup is commit #0, which needs no claim against the streamed value. Before, a source created in the shell and read by a streamed `<Loading>` boundary connected before that boundary's fragment arrived, so the boundary could not claim its server-rendered DOM and rendered a second copy beside it.
+- 41fdf96: `reportRequestFailure(error, event)` (`@solidjs/web`, server) reports a failure that fails a request outside any render or server function the runtime reports, such as a middleware throw that a framework's request handler catches. The ambient server error hook hears it as `kind: "request"`, `handling: "failed"`, with the request event, once per error object, and its return is ignored. With no hook registered the failure goes to `console.error`, as a render that fails before its shell does. `ServerErrorSite.kind` (`solid-js`) gains `"request"`. On the client the function is a no-op.
+
+  A synchronous throw out of `renderToString`, or out of `renderToStream`'s first pass (and so `renderToFrameStream` and `serverComponentResponse`), is now reported to the server error hook as `kind: "render"`, `handling: "failed"` before it is rethrown, where it previously reached the caller without the hook hearing it. A request handler that catches it and calls `reportRequestFailure` adds nothing; the hook hears it once, as the render's.
+
+- 87a3862: Server `createMemo` over an async iterable now keeps by-slot flight memory like thenables do: a `<Loading>` retry that re-creates the node adopts the slot's settled first value (or joins its pending flight) instead of opening a fresh iterable every pass, so sources that hand back a new iterable per call (subscribers, `liveQuery()`) converge instead of reporting "did not converge".
+- 7addcc6: Fix two SSR failures when the shell suspends above an `<Errored>` (a lazy memo throwing `NotReadyError`, the router's flash-decode shape). A `<Loading>` below the boundary whose content settled before the shell's suspension did lost its content: the fallback shipped and nothing swapped it, because the fragment inlined into a shell that did not yet hold its placeholder. And a hole that reached a suspension through a returned accessor (`{props.children}` resolving to an `<Errored>` whose subtree is pending — a `lazy()` route with no `<Loading>` between, for one) re-read its expression on every retry, re-creating every component above the boundary — state and pending sources included, so a component owning its pending source never converged. The retry now resumes the accessor that suspended.
+- Updated dependencies [0c550fd]
+- Updated dependencies [ecb68a1]
+- Updated dependencies [b07fed5]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [fa371c3]
+- Updated dependencies [96c5e19]
+- Updated dependencies [9a213bb]
+- Updated dependencies [721eb06]
+- Updated dependencies [b07fed5]
+- Updated dependencies [bc51ada]
+- Updated dependencies [eaddda4]
+- Updated dependencies [d231b99]
+- Updated dependencies [3086f1b]
+- Updated dependencies [3c7631a]
+- Updated dependencies [09eadfe]
+- Updated dependencies [be82cf3]
+- Updated dependencies [fd9f381]
+- Updated dependencies [b07fed5]
+- Updated dependencies [fff1615]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b0bad02]
+- Updated dependencies [0c550fd]
+- Updated dependencies [2317623]
+- Updated dependencies [4f67697]
+- Updated dependencies [2317623]
+- Updated dependencies [d1309ad]
+- Updated dependencies [924d909]
+- Updated dependencies [6be6c51]
+- Updated dependencies [7acc039]
+- Updated dependencies [bde4299]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1a3f87f]
+- Updated dependencies [5622be8]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0bad02]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0c8489]
+  - @solidjs/signals@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/solid/package.json b/packages/solid/package.json
index ae10e76d4..33e03ee93 100644
--- a/packages/solid/package.json
+++ b/packages/solid/package.json
@@ -1,7 +1,7 @@
 {
   "name": "solid-js",
   "description": "Reactive JavaScript library for building user interfaces. Compiles JSX to real DOM with fine-grained signal-based updates — no virtual DOM.",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "homepage": "https://solidjs.com",
@@ -131,7 +131,7 @@
     "performance"
   ],
   "dependencies": {
-    "@solidjs/signals": "^2.0.0-rc.13",
+    "@solidjs/signals": "^2.0.0-rc.14",
     "csstype": "^3.1.0",
     "seroval": "~1.6.7",
     "seroval-plugins": "~1.6.7"
diff --git a/packages/test-integration/CHANGELOG.md b/packages/test-integration/CHANGELOG.md
index 37046cdd5..87107118c 100644
--- a/packages/test-integration/CHANGELOG.md
+++ b/packages/test-integration/CHANGELOG.md
@@ -1,5 +1,138 @@
 # test-integration
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [0c550fd]
+- Updated dependencies [59fb244]
+- Updated dependencies [ecb68a1]
+- Updated dependencies [d4b10b5]
+- Updated dependencies [b07fed5]
+- Updated dependencies [2eb6e00]
+- Updated dependencies [3c1f809]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [fa371c3]
+- Updated dependencies [96c5e19]
+- Updated dependencies [9a213bb]
+- Updated dependencies [721eb06]
+- Updated dependencies [721eb06]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [365f37d]
+- Updated dependencies [b07fed5]
+- Updated dependencies [bc51ada]
+- Updated dependencies [eaddda4]
+- Updated dependencies [da84bd9]
+- Updated dependencies [d231b99]
+- Updated dependencies [98b916d]
+- Updated dependencies [98d35b9]
+- Updated dependencies [3086f1b]
+- Updated dependencies [b57eb2e]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [9d89df7]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [3c1d512]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [203ab1a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [3c7631a]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [7233451]
+- Updated dependencies [09eadfe]
+- Updated dependencies [9e85a09]
+- Updated dependencies [a5d0e76]
+- Updated dependencies [6be8486]
+- Updated dependencies [e44b2e4]
+- Updated dependencies [01e80a6]
+- Updated dependencies [be82cf3]
+- Updated dependencies [759a9b6]
+- Updated dependencies [fd9f381]
+- Updated dependencies [b07fed5]
+- Updated dependencies [fff1615]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b0bad02]
+- Updated dependencies [0c550fd]
+- Updated dependencies [2317623]
+- Updated dependencies [e345dc7]
+- Updated dependencies [4f67697]
+- Updated dependencies [2317623]
+- Updated dependencies [d1309ad]
+- Updated dependencies [924d909]
+- Updated dependencies [6be6c51]
+- Updated dependencies [41fdf96]
+- Updated dependencies [7acc039]
+- Updated dependencies [87a3862]
+- Updated dependencies [bde4299]
+- Updated dependencies [53ef0e6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [1b9ceb6]
+- Updated dependencies [7513131]
+- Updated dependencies [2656284]
+- Updated dependencies [9338c00]
+- Updated dependencies [7addcc6]
+- Updated dependencies [6f77b1b]
+- Updated dependencies [537e945]
+- Updated dependencies [1a3f87f]
+- Updated dependencies [5622be8]
+- Updated dependencies [11e9fb6]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0bad02]
+- Updated dependencies [b07fed5]
+- Updated dependencies [b0c8489]
+- Updated dependencies [7233451]
+- Updated dependencies [8d66ae5]
+  - solid-js@2.0.0-rc.14
+  - @solidjs/signals@2.0.0-rc.14
+  - @solidjs/babel-plugin@2.0.0-rc.14
+  - @solidjs/web@2.0.0-rc.14
+  - @solidjs/h@2.0.0-rc.14
+  - @solidjs/html@2.0.0-rc.14
+  - @solidjs/universal@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/test-integration/package.json b/packages/test-integration/package.json
index 931f69464..afda1220f 100644
--- a/packages/test-integration/package.json
+++ b/packages/test-integration/package.json
@@ -21,5 +21,5 @@
     "gitly": "^2.2.1",
     "shelljs": "^0.8.5"
   },
-  "version": "2.0.0-rc.13"
+  "version": "2.0.0-rc.14"
 }
diff --git a/packages/universal/CHANGELOG.md b/packages/universal/CHANGELOG.md
index f7ba105bd..f1a73683d 100644
--- a/packages/universal/CHANGELOG.md
+++ b/packages/universal/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @solidjs/universal
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9a213bb]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [da84bd9]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [759a9b6]
+- Updated dependencies [e345dc7]
+- Updated dependencies [41fdf96]
+- Updated dependencies [87a3862]
+- Updated dependencies [7addcc6]
+  - solid-js@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/universal/package.json b/packages/universal/package.json
index ff49a89bd..e40649d3c 100644
--- a/packages/universal/package.json
+++ b/packages/universal/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/universal",
   "description": "Solid's universal runtime for creating custom renderers",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "homepage": "https://solidjs.com",
@@ -51,7 +51,7 @@
     "test": "vitest run"
   },
   "peerDependencies": {
-    "solid-js": "^2.0.0-rc.13"
+    "solid-js": "^2.0.0-rc.14"
   },
   "devDependencies": {
     "solid-js": "workspace:*"
diff --git a/packages/web/CHANGELOG.md b/packages/web/CHANGELOG.md
index 6f6e6e8cc..a901e3da1 100644
--- a/packages/web/CHANGELOG.md
+++ b/packages/web/CHANGELOG.md
@@ -1,5 +1,123 @@
 # @solidjs/web
 
+## 2.0.0-rc.14
+
+### Patch Changes
+
+- ecb68a1: Binding slots: the fill runs once per occurrence, untracked, under the occurrence's owner — as a component body and a template-slot fill do. State created in the fill lives as long as the occurrence; a top-level read is a one-time read (dev: `STRICT_READ_UNTRACKED`, naming the fill); getters are the reactive form. Handlers and refs are read once when an element binds and go through `assign`, so events delegate, tuples bind and interactions wrap as in client JSX. On the server an array at a handler position is a dev finding (reason `tuple`) instead of being flattened; only `ref` merges arrays. Template-slot fills are untracked on every render path and carry the same labelled warning.
+
+  Breaking: `AttributeSlot` is renamed `BindingSlot`, with no alias, and its return is constrained (`SlotOutput<J>` / `SlotError<M>`, both exported) so an array, DOM node, function, async value or `$`-prefixed key is a type error on both sides. The diagnostic code `ATTRIBUTE_SLOT_POSITION` is renamed `BINDING_SLOT_POSITION`. The fill-shape finding also names async values.
+
+- d4b10b5: Binding slots: a slot property placed as a child (`<strong>{list.remaining}</strong> items left`) is a text position. The server emits a comment pair around it, `<!--_s:t=<occurrence>:<key>-->…<!--/_s:t-->`, with the escaped t=0 value inside on the document face and nothing on the stream face; the client writes the text between the markers from the occurrence's render effect, and a refetch's morph keeps the client's text. Strings and numbers render; nullish and booleans render empty, as a client insert renders them. Any other value is a new client dev finding (`BINDING_SLOT_POSITION`, reason `text-shape`) and clears. The content of `<textarea>`, `<title>`, `<style>` and `<script>` is not a text position (a comment is literal text there); bind `value=` or a style property instead.
+
+  Breaking: a slot property as a child used to render nothing and raise the `text` finding; it now renders and binds, and the `text` reason is retired.
+
+- 2eb6e00: Cancelling a server function or frames stream partway through a chunk now ends it cleanly instead of failing as a malformed stream.
+  - Chunk headers must be exactly `;0x` plus 8 hex digits plus `;`, and payloads must be valid UTF-8.
+  - A stream that fails to decode is cancelled instead of being left unread.
+  - The reader frees the memory from a large chunk once it is read.
+
+- 721eb06: Performance tracks no longer run the attribution cost checks by default (#3739). `enablePerformanceTracks()` — which `@solidjs/vite-plugin` calls in every `vite dev` session — now takes a records-only engine hold, so the six cost checks (`hotRuns`, `hotTime`, `wideDeps`, `unstableMemos`, `fanOut`, `wastedRecompute`) are opt-in again. To turn them back on, pass `enablePerformanceTracks({ attribution: { checks: true } })` (or `performanceTracks: { attribution: { checks: true } }` in the vite plugin), or take your own `attribution.enable()` hold. In dev builds, the `insert` child-resolution effect (which must track each row's resolved child, e.g. every `<Show>` row of a `<For>`) is also exempt from `WIDE_SCOPE_DEPS`; `HUGE_FAN_IN` still covers it.
+- 365f37d: Fix a hydration key miss on a `dynamic()` / `<Dynamic>` element whose prop getter mints a hydration id (a conditional expression over a signal compiles to a condition memo) and whose children include an element (#3741). The client's runtime `spread` inserted `children` before running its attribute effect, while the server's `ssrElement` read attributes first, so the memo and the child element took each other's ids and the child was rebuilt instead of claimed. `spread` now applies attributes before inserting children — the order a compiled element already uses — and `ssrElement` reads a `children` prop after every attribute regardless of key order. Observable on the client: a `ref` on a `dynamic()` element now runs before its children are inserted, as it does on a compiled element.
+- 98d35b9: Fix computed keys in compiled SSR `style` objects (builds without `serverComponents`). A computed key's name got no `;`, so `style={{ color: "red", [k]: v }}` rendered `color:redtop:1px` and the browser dropped both declarations. Hydration keeps the server's inline style, so they stayed dropped. A nullish first value also no longer leaves a leading `;`. Both compilers now pass a multi-entry object to a new `ssrStyleProperties(name, value, …)` helper, which writes the separator only between the entries it writes; a single entry keeps `ssrStyleProperty`.
+- b57eb2e: Streamed fragments gated on their stylesheets now reveal under a nonce-based CSP, and no longer stay on the fallback when a sheet loads before its fragment's template is parsed (#3747). The gated links carry `data-dfc` instead of inline `onload`/`onerror` handlers, which a strict `script-src` blocks; a capture-phase listener installed by the stream's fragment helpers, from a script that carries the nonce, counts them down. The content template is now written ahead of its links: a cached sheet could fire `load` before the parser reached the template, and `$dfr` dropped the reveal.
+- 3c1d512: frames: A1b + A4 (S-ref) — a slot record's `{$ref}`s settle at the host's write, through the response's own data table (`FrameHostOptions.resolve(ref, frameId, version, current)`); an undelivered key is a pending read the response's `data` chunk settles and its `complete`/`error` rejects (L1 — a value that never comes is an error, not a silence); a fresh mount waits for the record to settle, a mounted occurrence's prop pends and holds its value. Codec data tables are per response (keyed by frame id and version). Deleted: `ServerComponentHandlerOptions.onStream`, `STAGED_DATA` and the staged tables, `FrameHost.resolve`, `FrameHostOptions.isContainer`/`FrameHost.isContainer`, `Frame.rebase`, the frame's record dedupe (`#refArgsUnchanged`, `#slotResolvedRefs`) — a re-sent record's equality is the fill's per-prop memo's — and the frame's error/root value latches (applied state keyed by record identity). `FrameHost.preview`/`Frame.preview` lose their `resolve` parameter and stay: the compute-half preview is what stages a refetch's args with the transaction that read it.
+- 3c1d512: frames: a reveal applies its range (frames-rulings 2.3, A3). A revealed segment's content is applied against the store as it is revealed — its fills mount and the segments whose placeholders it carries reveal inside it, in the same flush and before a reconstructed boundary commits the content — so the frame's flush no longer retries over its segments, and a segment nested in content a pending fill holds no longer waits for a chunk that never comes. The readiness/retry model's second ledger (`#revealed` / `#fallbackShown`) is gone: a reveal's applied state is the content record it applied, a fallback's the gate it materialized, by identity, in the one applied map; whether a segment is shown is the DOM's to say. `Frame.isRevealed(segment)` is removed.
+- 3c1d512: frames: A4 (S-record) — the document face declares a slot record at its marker: `_$HY.r["sc:slot:<fid>:<occurrence>"]` is a pending promise written with the occurrence's markup and settled with the args by the record's data script (the shape a fragment's `<key>_fr` takes), so the adopting client awaits a record that trails its range's reveal through the value's own `.then` instead of polling the registry (C2 (a2) flips). Output shape: ≈ +32–38 B per document slot record (the resolver helpers are shared with the page's fragment declarations); a sync render (`renderToString`) writes the settled value as before. Deleted: the #2968 `setTimeout` re-drain poll and `FrameOptions.recordsPending` / `FrameOptions.drainRecords`.
+- 3c1d512: Frames A5′ — a deferred fragment's placeholder inside a server component's element is the frame's content by rendering, not by adoption (frames-rulings 3.3, ruled 2026-10-06).
+
+  **`solid-js`:** the document fragment ledger's `fragmentPolicy` lets a post-done swap proceed when the fragment is owned — its `pl-*` template is in the document and the integration's ownership predicate `_$HY.fa(placeholder)` says so — beside the existing claimant case; no hold, no replay for owned fragments. `_$HY.fr.claim` / `_$HY.fr.release` are removed from the published ledger (`_$HY.fr` is `{ pending, subscribe }`); `_$HY.fa(placeholder): boolean` is the new integration hook. `fragmentPending` now reads a revealed fragment from its swap record (`_$HY.v`) before its `_fr` stamp: the producer emits the swap script and then the `_fr` settle in the same batch, so a `_$HY.fr.pending()` read inside the reveal notification saw the revealing fragment as still pending — a page's last reveal never read as exhaustion and a waiter released on exhaustion waited forever.
+
+  **`@solidjs/web` (frames client):** installs `_$HY.fa` once (`pl.closest("[data-fid]")`, minus elements of a boundary disposed in place — C14); deletes `claimRegionFragments`, the per-adoption claim set, the cascade's claim half and the release loop (the dev-only rejection report over the region's `pl-*` templates stays, 0 prod bytes); `documentBoundary` pends on the intercept's one arrival answer (`awaitBoundary`) and `boundaryWaiters` is deleted (G9). A post-done swap into server-component markup no client has adopted yet now lands at once; the adoption that follows finds it in place and reads its declared records synchronously.
+
+- 3c1d512: frames: a frame's error is an errored async value (frames-rulings 3.3, A7). `FrameHost.landing(address)` rejects with the error record at the response's `:error` write, so the mount's content node throws to the nearest client `<Errored>` — the covering `<Loading>` no longer releases over an empty `<solid-frame>`. An error after the landing (a later yield failing, a cut-off stream, a refetch's response erroring) errors the node the same way; with no client `<Errored>` the core halts, as for any uncaught async error. The `<Errored>`'s `reset` re-asks: an errored landing is not a landing for a fresh consumer, and the re-read opens a new flight for the same address — the handler records the call behind every address it handles or the document answered (`callFor`, `@internal`), and the client re-invokes it through the server-function registry's RPC seam, whose client half now carries `createServerReference(id)`. A response for an address whose mounts show an error writes through instead of being staged. `frame.error` still records the error.
+- 9d89df7: frames: the address is an async source (S-flush) — a mount's covering `<Loading>` pends on the bound address's first flush through `FrameHost.landing(address)` (content or error), per bound address, so a switch is a new question and the superseded address's late writes release nothing (contract C17 a, c); the store is one response's — a version bump or rebind replaces it wholesale, root included (C6 a1, b2; C7 c); a called occurrence (`prop#n`) found without its record waits for it instead of being evaluated argless (C18); the document face's reveal cascade syncs the adopting frame — a reveal is an apply (C2 b, C4 d).
+- 7233451: frames: the assets tier (frames savings pass C5) — the head mirror a segment's `assets` record drives (the stylesheet gate, module and typed preloads, inline styles) leaves the eager frames client for the lazy chunk `@solidjs/web/frames/assets`, loaded through the tier mechanism. A segment whose assets record carries stylesheets or inline styles is not ready while the tier is not resident: the server's fallback stays on screen and the reveal happens at max(tier load, stylesheet load) — no segment reveals unstyled. Once the tier is resident only stylesheets gate; inline styles, modules and preloads apply at the record's arrival, and a segment with none of these never waits on the tier. New export path `@solidjs/web/frames/assets` (`@experimental`); `InstallOptions.tiers` loaders resolve `TierModule` (a module with or without `install()`).
+- 7233451: frames: the binding-slot tier (`@solidjs/web/frames/bind`, `@experimental`) — the `_s:*` marker parsers, consumer discovery, the morph's owned-position arms, the per-frame consumer sets and the fill's binding leave the eager frames client as a lazy chunk; `assign` leaves with them. A marker met while the tier is absent holds the frame under frames-rulings 3.1 (hydration-done waits; the install's flush binds). The delegated-event replay window is closed by a bare ` _hk` the server stamps on each document-face element with an `_s:on:*` position (4 bytes each, nothing else stamped): the tier marks the element completed at the bind and drains the queue, so a click before or during the hold reaches the bound handler. Data occurrences now mount with the current record.
+- 3c1d512: A server `<Loading>` inside a server component that fails after the first flush renders the server's outcome into its fragment instead of a blank (C12 (c), frames-rulings 3.3): the nearest server `<Errored>`'s fallback for the error, at the `<Loading>`'s position (asked through the boundary error handler's new `outcome` mode; a `<Loading>` between passes the question up); with no server `<Errored>` the error escapes the component — the frame's own `:error` on the stream face (an unkeyed `error` chunk), a frame-addressed `{ type: "error", fid, error }` op on the document face's `sc:live` channel (only the owning adopted boundary applies it) — and the position keeps the boundary's own fallback. `_fr` still rejects and the keyed error chunk still rides (the diagnostics). Outside a server component nothing changes (the blank the client twin renders fresh over). `HydrationContext.registerFragment`'s resolver gains a third argument (`escaped?: { frame?: string }`) and the context an internal `frameId`.
+- 3c1d512: frames: one server sweep lands as one frame (C13). The sink collects the `hole` / `attr` re-emissions one sweep produces and emits them as one `{ type: "ops", ops: [...] }` chunk on the stream face (one wire line) and one `sc:live` op of the same shape on the document face; a sweep that changes one binding emits that member alone, as before. The client maps the unit to one record map and applies it as one write — one hole pass, one `frame:applied` (the hole pass now announces once per flush, not once per hole). The document op log flattens a unit into its members (last value per hole). Additive wire (`FrameChunk` gains the `ops` member; RFC addendum in `frame-streams-rfc.md`).
+- 3c1d512: An adopted frame occurrence claims its server markup by re-entering hydration the way a streamed `<Loading>` resume does (frames-rulings 3.1 / 3.2, the savings plan's A2 — S-hold's window form).
+  - `solid-js`: `hydrateWindow(id, fn, scope?)` is factored out of a streamed boundary's resume and reached as `sharedConfig.hydrateWindow` (`@internal`): the keys under `id` gathered into the registry (the captured `scope` pair when another `hydrate()` root replaced the live one, #2917), hydrating on for the synchronous window, the current owner the claim owner (a render the window forces elsewhere is a client render, #3504), the owner the window's snapshot and live scope when none is open — so a write during a late claim is held and replays once the claim is over, and a late claim no longer re-marks the root's scope. `sharedConfig.claimRoots` (`@internal`) is typed: the claimant declares a range that may be detached around its window. `holdBoundary` stays the registration; the resume path is unchanged in behaviour.
+  - `@solidjs/web` (frames): `claimRender` is the window — one `createOwner({ id: prefix })` and the call — instead of a registry of its own gathered by walking the range, a hydrating flag flipped through `sharedConfig`'s setter (which reset hydration-done and re-ran its completion from outside the runtime), and a hand-over of keys from the root registry: `gatherClaims` and `hasPendingFragment` are deleted (the window gathers by the producer prefix and always engages). `adoptBoundary` captures the registry/gather pair it adopts under so a claim made long after — under the frame's hold, at a fragment's reveal — gathers against the root that holds the frame.
+  - `@solidjs/web`: `gatherHydratable`'s prefix-scoped gather selects its keys natively (`[_hk^="…"]`) instead of sweeping every `_hk` and filtering in JS — it now runs once per adopted occurrence, not only per late resume.
+
+- 9d89df7: frames: a `data` chunk is under the store's version guard like every other chunk — a superseded response's late data lands nowhere, never in the table that is now the current response's (contract C5 a, b, e).
+- 7233451: frames: drop the three dead `#slotNodes` writes for data occurrences — the only reader (the zombie check) skips data occurrences, so the consumer-element arrays were built and never read
+- 9d89df7: frames (dev): a server `<Loading>` fragment inside an adopted server component that rejects on the server is reported — the client shows what the server rendered for that outcome and invents no error state of its own (contract C12 c, client half).
+- 9d89df7: Hydration-done counts the frames client's holds (frames-rulings 3.1, ruled): an adopted occurrence the frame has not claimed yet — waiting for its args record or a `{$ref}`'s data — registers as a pending boundary through the same registration a streamed `<Loading>` resume takes (`sharedConfig.holdBoundary`, internal), so `onHydrationEnd` and `isHydrationInProgress()` mean the same thing with or without server components (contract C3 a).
+- 7233451: frames: the live wire moves into a lazy tier (`@solidjs/web/frames/wire`, the sixth chunk). The connection a `live()` loop's response runs under — the open-frame count its end is judged by (a death with frames open vs a completion), the join of a second loop onto an address already live, the supersession cancel, `connection.ended` / `cancel` — the have-list ledger per mount with its encoder, and the resume shape (`Last-Event-ID` + `X-Frame-Have`) load with the chunk. The eager client keeps the arm that awaits the tier's residency before a live response's body is read, so a live connection without the chunk cannot happen; the chunk's import starts at the `live()` call, before its first fetch (preload-at-call, through the new optional `responseHandler.onLive()` hook the sf client fires), and a non-live call never loads it. One accepted degraded case: content applied before the chunk was resident kept no ledger, so that first connect sends no have-list (and no ordinal) and receives a full snapshot.
+
+  Public surface: `Frame.have?()` is removed from the `Frame` interface (the ledger is the tier's `haveOf(frame)`, `@internal`); `encodeHaveList` moves from `frame-transport` into the tier (`@internal`; `decodeHaveList` and the `FRAME_HAVE_*` constants stay); the `@solidjs/web/frames/wire` export path is added; `ServerFunctionsClientConfig.responseHandler` gains the optional `onLive()`; `ServerComponentHandler` gains `onLive()`.
+
+  Pins: `consistency/tier-wire-preload.spec` and `server-functions-live-loop.spec` — the latter drives `live()`'s reconnect loop from the consumer's side (first-connect failure, the fail-fast 4xx set and 408 / 425 / 429 / `Retry-After`, the cursor as `Last-Event-ID`, the `online` wake, `return()` and a caller's signal at every phase, `live(GET(fn))`, the handler's local answers), closing the loop's branch-coverage gap.
+
+  Size: frames eager −965 min / −305 br (10.89 KB); pages −349 / −335 br eager; the `wire.js` chunk 1,922 / 934 (lazy; the live page loads it at its first `live()` call). Caps ratcheted to measured + 10 B.
+
+- 3c1d512: frames: a plain (non-`live`) server component response ends at a streaming bound. A response whose content reads a standing source — a generator memo, a projection — used to stay open until the source settled, which for a source that never returns was never, with none of `live`'s reconnect semantics. The producer now ends it after `maxYields` emitting sweeps past the first flush (default 64) or `maxDurationMs` after the first flush (default 30 000 ms) — and when the request's `signal` aborts after the first flush — emitting `{ type: "complete", bound: "yields" | "time" }` before the body closes, and tears the render down quietly (sources returned, no abandonment finding). Both are new options on `FrameStreamOptions` (`renderServerComponent`, `renderToFrameStream`, `serverComponentResponse`); a `live` response is never bounded. The client stores `:bound` beside `:complete` and, in dev, warns once per cut-off naming `live()` as the declared way past the bound. `createFrameSink` gains an optional fourth `hooks` argument (`onYield`) and its `end(bound?)` takes the bound. Additive wire; RFC addendum in `frame-streams-rfc.md`.
+- 1b9ceb6: Frames client: an address switch re-arms the shell gate and rebinds the frame in the pass that sees the new address (the follow's compute), not in an effect's run. Under the hold model a switch delivered while the previous switch's gate still pends lands the binding in the frame that gate holds, and an effect's run is stashed with that frame — behind the very gate the rebind would release, so a second switch mid-flight never bound to the live call. The gate signal takes `ownedWrite` (the re-arm and a warm rebind's release are written from the pass). Both the call-driven mount and the document-adoption face.
+- 203ab1a: Server-component content for a call a boundary is showing now lands with the transition that read it, instead of morphing in when the response arrives. A refetch, or a single-flight region, is staged: the call resolves to a binding naming the staged version, and the mount commits it when that binding reaches it. The slot args go first, under the transition, so a fill deriving optimistic intent over a server arg never reads the old arg. The markup lands at the commit. Single-flight regions show when the integration's cache takes the mutation's slice, so any cache that subscribes to flight data drives it, not just Solid Router.
+
+  An address switch's new content lands at the same commit: the frame re-binds in the run of the effect that follows the address, while the switch gate re-arms in its pass and settles on the new address's first content through a frameless registration on the host — so a second switch mid-flight still binds to the live call, and the morph no longer lands beside siblings the transaction still holds.
+
+  Behaviour change: a response for a showing call that no reader mounts is never shown. Previously it morphed every mount of the address on arrival.
+
+- 7233451: frames: C4 — the regions tier. Nested server-content regions (`{$frame}` slot args resolved to `<solid-frame>` region elements with frames bound over them) leave the eager frames client for the lazy chunk `@solidjs/web/frames/regions` (a new `@experimental` export path), loaded through the tier mechanism: the server announces `regions` where it mints one; a record naming a region met before the tier is resident waits — a fresh mount in the held set (the frame's hold registered under frames-rulings 3.1 on the adopt path, the server interior on screen), a mounted occurrence's new record pending in the store until the install's flush. `InstallOptions.tiers` now types a tier's module as the new exported `TierModule` (its exports are the tier's appliers; `install()` stays optional). Frames eager −1,078 B minified / −237 B brotli; the page scenarios −1,083 B minified; the non-SC scenarios unchanged.
+- 7233451: Frames client, residue pass 1 — the D list (dead / incidental code off the eager client; frames residue pass §2 rows 2b, 2c, 2e, 2f, 2g). `documentAddress` is gone: an adopted mount's address comes with its binding (every serialized reference resolves to the call's binding), and a mount with none — the per-function placeholder rendered directly — binds the function id. `slotsFor` keeps one dispose map: a live range binding's `insert` lives under the fill's own owner where there is one, else under an owner registered the same way, so a re-call disposes whichever path the previous invocation took. The zombie heuristic and the `#slotNodes` map it read are gone — the morph relocates ranges among siblings and recreates nothing (DR-5), so "mounted" is the frame's set. `#revealSegment` has one path: a frame created without `FrameOptions.reveal` reveals through a default seam that inserts the content at once (no boundary) — the content is applied as it is revealed, as on the boundary path — and a placeholder missing its closing comment is not revealed (dev error; `#showFallback` already treated it so). `handler.showing` no longer brands the bare per-function component: the reference a reader holds at t=0 is the bootstrap's binding, branded there. The capture arm (`contentHTML` + the last-unmount capture) stays: `lifecycle-matrix/remount` pins it.
+- 7233451: `FRAME_HAVE_HEADER` and `FRAME_HAVE_BUDGET` leave the `@solidjs/web/frames` client entry's export list (frames residue pass §2 row 5a). They stay exported from `@solidjs/web/frames/server`, where the header is read; the client sends the have-list itself through the handler's `resume` and nothing consumed the names off the client entry. Removed public surface, `@experimental`.
+- 7233451: The lean re-ask (frames residue pass §3.3). The server-function client hands its response handler the call it dispatched as a thunk — `ctx.retry` on `responseHandler.handle`, `info.retry` on `responseHandler.intercept` — the same reference, arguments, declared shape and per-call options, so a `GET`-declared read stays a GET by construction. The frames client's re-ask for an errored boundary's `reset` (frames-rulings 3.3) is that thunk: `callFor(address).retry()`. Gone with it: the frames client's `reask` installer and its reads of the RPC slot and the metadata brand, and `createServerReference(id)` on the client half of the server-function RPC slot (`getServerFunctionRPC()`, `@internal`), which nothing reads any more. `callFor` (`@internal`) now returns the recorded call with its `retry`. The `responseHandler` type in `ServerFunctionsClientConfig` documents the existing `intercept` seam alongside `handle`, both carrying `retry`.
+- 7233451: Frames client: every slot fill is placed by `insert` — the fill's output has the core's lifecycle (created under the fill's owner, claimed in place under hydration through `insertExpression`'s claim pass, disposed with the owner) instead of a frame-side copy of it. The Solid binding's static path (`normalizeSlotContent`, `isReactiveContent`, the in-place `settle` test) and the frame runtime's own range writer (`#replaceRange`) are gone; a static fill is one `insert` of a non-function value (no effect created), a reactive one binds the range as before. `createFrame` / `createFrameElement`: the frame element IS the range — the never-used comment-marker range mode of the runtime is removed. **`Slot` (`FrameOptions.slots`, `@experimental`) changes shape:** a callback owns its range — it places or binds its output before `ctx.range.end` over `ctx.existing` — and its return value is no longer read (before: returned nodes were placed by the frame; `undefined` claimed). A slot range missing its end marker (`FRAME_MARKER_CORRUPTED`) is left as the server rendered it instead of being filled at the parent's end.
+- 7233451: frames: residue 4 — a pending `{$ref}` read is owned by the decode table. A slot record's `{$ref}` to a key its response has not delivered yet is answered by that response's `createJSONDataTable` with a promise the table owns (marked `s = 0`, carrying `c`, the callbacks run when it settles), settled by the key's `data` chunk through the table's own `apply` and rejected by `close(error)` when the response ends (L1 — a value that never comes is an error where it is read, not a silence); a version bump drops the superseded table and its reads. The frames host keeps only the `record.pending` count (a fresh mount waits for its record, the covering `<Loading>` pends on the landing alone) and one fan-out helper; `pendingRef` / `settleWait` / the per-store waits are gone. `FrameHostOptions.closeData(frameId, version, error?)` (new, `@experimental`) tells the integration a response ended; the shared host closes that response's table. The transport awaits `prepareData` before a `slot` chunk whose args carry a `{$ref}`, as it does before a `data` chunk, so `resolve` always has a table. Frames eager client −505 min / −174 br (34,272 / 11,367 → 33,767 / 11,193); the lazy decode chunk +420 / +161.
+- 3c7631a: ABANDONED_FLIGHTS no longer fires for a frames slot arg that every re-shipped record re-reads while it is still pending (#3852). Dev builds mark the per-key slot-arg memo with an internal option that the check skips; the memo's flights are still recorded and still counted in `feedback()`.
+- 7233451: Frames: the server-announced tier mechanism (frames savings pass §2, Phase B — the seam alone; no tier is cut yet, every capability stays eager).
+
+  The server learns at render time which frames-client capabilities a response or a document needs — it mints each feature — and announces their names so the client can start the tier's import in parallel with the content instead of at first use: on a frame stream, the `X-Frame-Tiers` response header (the tiers the sync render pass minted) and, for a tier first needed after the head left, an in-band `tiers` member on the next chunk out (`FrameChunk.tiers`, additive); on a document, the `_$HY.r["sc:tiers"]` hydration record (cumulative, re-written at each new mint) plus a `<link rel="modulepreload">` per tier whose chunk URL the integration gave (`frameTransformDirectResult(value, { id, args, tierUrls })` — the server does not know the client's chunks; absent, the record alone carries the name). The sink's `needs(tier)` runs at the mint sites: a binding-slot position read (`bind`), a nested server-content region (`regions`), an assets chunk (`assets`), a traced container in a slot arg (`trace`), a `live` response (`wire`). A sync `renderToString` document announces nothing (no shared render slot); the client detects.
+
+  The client (`@solidjs/web/frames`): `installServerComponents(host?, { tiers })` takes the tier → loader map (`() => import(...)`, the module exporting `install()`), reads the document's record and starts each named load; `applyFrameResponse` reads the header before the body and `chunk.tiers` at each chunk, and a `data` chunk awaits the tiers it names before it decodes (its node tree needs them). A fresh mount whose tier is not resident — a data occurrence's `bind`, a region-carrying record's `regions` — waits like a recordless called occurrence: on the adopt path that wait is one more reason in the frame's registered hold (frames-rulings 3.1 — the event-replay window stays open, hydration-done waits), on the stream path the record stays pending in the store; the readiness check itself starts the load when nothing announced it (detection is the fallback), and the install flushes every live frame so the held occurrence mounts with the record it was held on. A name with no loader is resident (eager), which is every name today.
+
+  Measured before written (edited dist copies, `scripts/size`): frames eager client +473 B min / +145 B br (≤ +150 budget; the plan's ≈ +100 estimate, ×2.5 pre-estimate ≈ +250); pages +478 min; every non-server-component scenario 0 B. Frames server dist +793 B min; `@solidjs/web`'s own server entry 0 B.
+
+- 7233451: frames: the trace tier's update-site wait. A MOUNTED occurrence's new slot record whose args carry a `{ $tr }` container-trace marker while the trace tier is absent (a live slot op minting the page's first trace after the shell, a refetch adding a projection arg) now stays pending in the store: the live binding keeps the args it shows, the tier load starts, and the install's flush applies the record as an args change with the marker materialized. Before, `#syncSlots` guarded only the fresh mount (`needsTrace`) and the regions tier at the update site (`needsRegions`), so such a record was pushed into the live binding raw — the marker read as the value. Mirrors the regions tier's update-site wait.
+- 7233451: frames: the container-trace materializer is the frames client's traces tier — `@solidjs/web/frames/trace`, loaded through the server-announced tier mechanism (`prepareTier("trace")`), so the store engine leaves every server-component page that never meets a trace (page base −6.6 KB brotli, page live −6.7 KB; frames eager −83 B). `solid-js/internal/container-trace` is a new `solid-js` entry carrying `materializeContainerTrace(marker, claiming?)` (the store engine reached through `@solidjs/signals`, the hydration dispatch `withStoreHydration` and the patch protocol read back from `solid-js`); the materializer leaves `solid-js`'s main and `solid-js/internal` entries. The eager frames client keeps the trigger: the loader entry, the held-set predicate (an adopt-time record whose args carry a `{ $tr }` marker while the tier is absent is held under frames-rulings 3.1 — its server interior on screen, hydration-done waits — and mounts with the record it was held on, a replacement applying as an args change), and the `claiming` hint (`FrameHostOptions.revive(value, claiming?)`), which keys the materializer's parked backlog on the claim again: a fresh mount reads the fold of its whole backlog at once.
+- e44b2e4: Hydration: a `<Loading>` around `lazy()` whose module is still loading when hydration starts no longer moves its server-rendered nodes once the module lands. The boundary claims those nodes on its late resume, but the enclosing insert had tracked its region as empty, so it re-inserted them, which moved connected nodes and blurred a focused input. While hydration is in progress, an insert whose region is untracked now leaves the incoming nodes in place when every one of them is already a child of its parent. Once hydration completes, inserts behave as before. Fixes #3749.
+- 01e80a6: The hydration bootstrap marks every promise the inline payload files under `_$HY.r` as handled when it lands, so a serialized async read that rejected under an `<Errored>` (which already rendered its fallback) no longer raises `unhandledrejection` in the browser. A consumer reading the record still receives the rejection.
+- be82cf3: Observe: one interaction frame per event, not per listener. `InteractionRef` takes an optional `event`; frames with the same `event` re-enter one interaction record, which stays joinable for the event's dispatch and is recorded at the next task. The web runtime keys its frames by the DOM event, and `@solidjs/web` exports `dispatchAsInteraction(e, fn)` so a listener outside the runtime (a router's `document` click handler) joins the frame of the same event — `fn()` in production builds. One anchor click is now one interaction record carrying both the `onClick` work and the navigation (#3754).
+- 4f67697: **Breaking:** only `on` followed by an uppercase letter (`onClick`, `onPointerDown`) is an event handler. Lowercase `on*` names (`onclick`, `onmouseover`) are plain attributes everywhere:
+  - Both compilers compile `onclick={expr}` like any other attribute (`setAttribute`, reactive when `expr` is dynamic) instead of binding a delegated or native event, and SSR renders it as an escaped attribute instead of dropping it. A leftover 1.x `on:click={fn}` is likewise a plain namespaced attribute (it previously compiled to `addEventListener(":click", fn)`).
+  - `@solidjs/web` `spread`/`assign` set lowercase `on*` keys as attributes, the server spread walk renders them, and `useHead` applies lowercase `on*` attributes (camelCase handler names stay skipped). `ssrAttribute` escapes a function value instead of interpolating its source raw.
+  - `@solidjs/html` and `@solidjs/h` elements wrap a function passed to a lowercase `on*` in a getter like any other attribute; only `onXxx` and `ref` are exempt.
+  - `@solidjs/html` components follow `@solidjs/h`'s rule: every zero-argument function prop, `onXxx` handlers and `ref` included, is a getter, so a component handler must declare its event argument (`onClick=${e => …}`).
+  - New dev-only check `LOWERCASE_EVENT_ATTRIBUTE` (added to the `DiagnosticCode` union): warns once per attribute name when a function is set on a lowercase `on*` (or `on:`) attribute, naming the camelCase handler to use.
+
+- 41fdf96: `reportRequestFailure(error, event)` (`@solidjs/web`, server) reports a failure that fails a request outside any render or server function the runtime reports, such as a middleware throw that a framework's request handler catches. The ambient server error hook hears it as `kind: "request"`, `handling: "failed"`, with the request event, once per error object, and its return is ignored. With no hook registered the failure goes to `console.error`, as a render that fails before its shell does. `ServerErrorSite.kind` (`solid-js`) gains `"request"`. On the client the function is a no-op.
+
+  A synchronous throw out of `renderToString`, or out of `renderToStream`'s first pass (and so `renderToFrameStream` and `serverComponentResponse`), is now reported to the server error hook as `kind: "render"`, `handling: "failed"` before it is rethrown, where it previously reached the caller without the hook hearing it. A request handler that catches it and calls `reportRequestFailure` adds nothing; the hook hears it once, as the render's.
+
+- 53ef0e6: Single-flight delivery now settles slice entries the server folded while still pending before handing the envelope to the flight-data consumers. A collector may fold values that are still in flight (the router's collector returns its preloads' `query` promises as they stand), and the codec streams those after the response head; since the body decode resolves on the first chunk, the mutation call resolved, and a router action settled (busy state cleared, `onSettled` ran) before the refreshed route data existed. `deliverFlightData`, shared by the plain client and the frames client, now waits for every pending entry (`allSettled`, so a failed read stays with the cache entry it seeds) before running consumers.
+- 2656284: `createSSRResponse` no longer hangs when a streamed render ends before its shell flushes (#3719). A render that fails pre-shell (`onError` hears `handling: "failed"`) or is aborted through its `signal` now resolves with a bodyless 500, or a redirect when a `Location` is already on the response stub, and the stub is committed. A render that succeeds with an empty document resolves with an empty 200. The promise still never rejects.
+- 9338c00: `createSSRResponse` over a stream result now tears the render down when nobody will read it (#3768). Cancelling the resolved body (the client went away, a HEAD request whose body the host cancels) disposes the render through `renderToStream`'s disconnect path, as cancelling its `readable` does: every async source still being pulled is returned, `onCleanup` runs, and nothing more is written. This emits `SSR_STREAM_ABANDONED` with `data.reason: "consumer"`. A pre-flush `Location` (a bodyless redirect) tears the render down the same way, as the JSDoc already said, but without the finding, because nobody left. Previously both only dropped writes, and the render ran on until its sources happened to end. The render's observe record settles as `"abandoned"` in both cases.
+- 7addcc6: Fix two SSR failures when the shell suspends above an `<Errored>` (a lazy memo throwing `NotReadyError`, the router's flash-decode shape). A `<Loading>` below the boundary whose content settled before the shell's suspension did lost its content: the fallback shipped and nothing swapped it, because the fragment inlined into a shell that did not yet hold its placeholder. And a hole that reached a suspension through a returned accessor (`{props.children}` resolving to an `<Errored>` whose subtree is pending — a `lazy()` route with no `<Loading>` between, for one) re-read its expression on every retry, re-creating every component above the boundary — state and pending sources included, so a component owning its pending source never converged. The retry now resumes the accessor that suspended.
+- 6f77b1b: Fix the end of a streamed render racing a suspended shell. A `<Loading>` fragment settling while the shell was still suspended (a lazy memo throwing `NotReadyError` above it) could empty the fragment registry before the shell's root holes re-pulled, and the render flushed its serializer then: everything the re-pull serialized was dropped from the hydration data, and the awaited form (`renderToStream(...).then`) completed with an empty document — or, with an `<Errored>` holding the suspended subtree, never completed. The end of the response now waits for pending root holes.
+- 537e945: SSR validates dynamic attribute and tag names: a spread key the HTML parser would not read back as one attribute name (whitespace, quotes, `<`, `>`, `/`, `=`, control characters, or empty) is dropped, as the client's `setAttribute` refuses it; other names are written as is (`&` is no longer escaped to `&amp;`, which the parser keeps literally in a name). A `<Dynamic>`/`ssrElement` tag that is not one element name throws, as the client's `createElement` does.
+- 7233451: Add `dynamicComponent`, the component-only sibling of `dynamic` (client and server entries). Same contract, semantics and hydration shape as `dynamic` — the two share one implementation — but its source type excludes tag names, and it never references the element runtime: `dynamic` must be able to render a tag, so one `dynamic` on a page retains `createElement`, `spread`, the prop-collection helpers and the SVG/MathML tables for everyone; `dynamicComponent` never does. It is the documented way to mount a server component (`dynamicComponent(() => getStory(id))`); a server-component page mounted through it sheds ≈ 2.2 KB brotli. `dynamic` is unchanged.
+- 8d66ae5: Server bundles that don't serialize no longer retain the serializer's plugin set. Five module-level statements that Rollup shakes but Rolldown (Vite) and esbuild keep are now side-effect free to every bundler: the frozen `DEFAULT_WEB_PLUGINS` array is `/* @__PURE__ */`-annotated, seroval `Feature` flags are read on use, the stub gap-fill header set is built on first use, the event-stream heartbeat's `new TextEncoder()` is annotated (and no longer built at import time by `dist/server.js`), and the flash-cookie matcher is a regex literal. A server bundle importing only `isServer` or `getRequestEvent` drops from ~11.7 KB to ~1.6 KB minified (seroval bundled; Rolldown), and `renderToString` bundles shed ~260–380 B. No behavior or API change.
+- Updated dependencies [4b4c2cb]
+- Updated dependencies [21ff8f8]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9a213bb]
+- Updated dependencies [b0c6e6a]
+- Updated dependencies [da84bd9]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [3c1d512]
+- Updated dependencies [9d89df7]
+- Updated dependencies [7233451]
+- Updated dependencies [759a9b6]
+- Updated dependencies [e345dc7]
+- Updated dependencies [41fdf96]
+- Updated dependencies [87a3862]
+- Updated dependencies [7addcc6]
+  - solid-js@2.0.0-rc.14
+
 ## 2.0.0-rc.13
 
 ### Patch Changes
diff --git a/packages/web/package.json b/packages/web/package.json
index 73df21c46..3c9c25496 100644
--- a/packages/web/package.json
+++ b/packages/web/package.json
@@ -1,7 +1,7 @@
 {
   "name": "@solidjs/web",
   "description": "Solid's web runtime: client rendering, hydration, SSR, and DOM-specific control flow (Portal, Dynamic).",
-  "version": "2.0.0-rc.13",
+  "version": "2.0.0-rc.14",
   "author": "Ryan Carniato",
   "license": "MIT",
   "homepage": "https://solidjs.com",
@@ -385,7 +385,7 @@
     "seroval-plugins": "~1.6.7"
   },
   "peerDependencies": {
-    "solid-js": "^2.0.0-rc.13"
+    "solid-js": "^2.0.0-rc.14"
   },
   "devDependencies": {
     "@codspeed/vitest-plugin": "^5.4.0",