smbls 3.14.850 → 3.14.852

package/CHANGELOG.md

@@ -1,5 +1,23 @@
 # smbls
 
+## 3.14.852
+
+### Patch Changes
+
+- An app that declares `content: {}` keeps its built page on screen through the takeover. The router's first `set()` used to replace the adopted content element, take the built node out of the DOM and build a fresh one (an adoption miss; the page was off screen for a frame, 40–100 ms at 6x CPU). While a hydration window is open, `set()` now hands the old content's node back to the window and the new content adopts it in place.
+
+## 3.14.851
+
+### Patch Changes
+
+- 2e9abb3: The three brender registry writers moved out of the `@symbo.ls/utils` index into a new server entry, `@symbo.ls/utils/server`: `brenderRegistryBlock`, `encodeBrenderRegistry`, `brenderRegistryTreeBlock`.
+
+  - Why: every `@symbo.ls/utils` index export is spread into `context.utils`, so the writers rode in every browser bundle (about 1.2 KB raw, 330 B Brotli) and no browser code calls them.
+  - `el.call('brenderRegistryBlock' | 'encodeBrenderRegistry' | 'brenderRegistryTreeBlock', …)` no longer reaches them, and `smbls` (which re-exports the utils index) no longer exports them.
+  - Server or build code that writes a registry: `import { brenderRegistryBlock, encodeBrenderRegistry, brenderRegistryTreeBlock } from '@symbo.ls/utils/server'` (ESM and CJS).
+  - The client half stays in the index: `BRENDER_REGISTRY_BLOCK`, `BRENDER_REGISTRY_TREE_BLOCK`, `decodeBrenderRegistry`, `readJsonDataBlock`, `jsonForScript`.
+  - `@symbo.ls/brender` imports the writers from the new entry, so it needs the `@symbo.ls/utils` release that ships `@symbo.ls/utils/server`. The pages it writes are byte-identical.
+
 ## 3.14.850
 
 ### Patch Changes