smbls 3.14.841 → 3.14.842

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # smbls
 
+## 3.14.842
+
+### Patch Changes
+
+- Round 4 (Nika 2026-10-21, without the once-per-frame iOS flush):
+
+  - smbls/fetch: a stale pre-rendered page refreshes once it takes a recorded answer, whenever that happens (a replaced page whose only reads are getDB() calls in code).
+  - scratch/element: the sprite parse and the caret check use the target document's realm.
+  - element/smbls: a frame removed during a later chunk of the first render or the adoption stops the boot.
+  - polyglot/smbls: labels persist in the app's own window storage; a project loadTranslations is tracked.
+  - smbls: create() never writes into the caller's app definition (a second create() of the same definition took the first app's state); a node or key passed as the app is kept. Docs: first-render hooks run outside the document; "removed" is el.\_\_ref === null; wait with el.whenConnected.
+  - app-rules: the rules namespace is appRules, not R (census collision with minified R).
+  - frank: a globalScope.X named in a comment is no read; a block-scoped const/let is never the project's single-letter name; the watchdog runs its child without --cpu-prof unless FRANK_WATCHDOG_CPU_PROF=1 (the profiler hung pushes on macOS node 24).
+  - cli/runner: smbls start listens on 127.0.0.1 unless --lan / --host / SMBLS_HOST; a bundler flag with a value passes through; lock.json records the API base of its projectId and a lock from another base re-resolves by owner/key.
+  - channels: an API base in the environment (SYMBOLS_API_BASE_URL / SYMBOLS_API_URL) names the channel when it is a known channel's API.
+
 ## 3.14.841
 
 ### Patch Changes

package/README.md

@@ -121,9 +121,40 @@ When things happen:
   route behind an awaited guard renders later, as before: the shell goes in,
   then the page — built outside the document in the same chunks and inserted
   whole.
+- Every element of the first view — the root too — runs `onInit`, `onCreate`
+  and `onRender` while its node is outside the document, and stays outside
+  until the commit, some tasks later. Code that awaits something in a hook
+  and then tests `el.node.isConnected` finds `false` and must not read that
+  as "removed". A removed element has `el.node === null` and
+  `el.__ref === null`. For work that needs a connected node (`showModal()`,
+  measuring, focus), or a swap that must wait for the node to be in, use
+  `el.whenConnected(fn)`: it runs `fn(el)` now if the node is connected,
+  otherwise in the same task as the insertion that connects it, and never
+  for an element removed first.
+
+  ```js
+  onCreate: async (el) => {
+    const page = await el.scope.loader()
+    el.whenConnected(() => el.set(page)) // not: if (!el.node.isConnected) return
+  }
+  ```
+
+  `onMounted` runs after the first view is in (next frame).
 - `DOMContentLoaded` and `load` can fire before the app is in the document
   (the boot continues after the entry script's task). Code after `create()` in
   the entry script runs before the design system is prepared.
+- The document can go away while the boot waits for its next task: an iframe
+  app whose host removes the frame, a test whose window closes when it ends.
+  The boot checks its document after that wait, and again at every chunk of
+  the first render and of the adoption of a pre-rendered page (one check per
+  chunk, not per element). A frame that left its document, or a document
+  that lost its window, stops the boot: the chunks built so far are disposed,
+  nothing more is built or attached, and `create()`
+  resolves with the bare definition, nothing mounts, no root `onCreate` runs,
+  no `popstate` listener is added and no error is logged. A top-level
+  document always keeps its boot. Await `create()` before you tear the frame
+  down when the app must finish. (A `<style>` whose document has no sheet for
+  it drops its rules; it never throws.)
 - The app root's own `onCreate` … `onRenderRouter` run before the root is in
   the document — every other element's hooks always ran before their element
   was attached. The first page's hooks, `onRouteChanged`, the scroll and the
@@ -154,9 +185,12 @@ When things happen:
   `fetch.seed.maxAge`), it is adopted from the build's data as any page is,
   and when the hydration window closes (on a replaced page: when its first
   view has settled) the fetch plugin asks again, at idle, for exactly what
-  took a recorded answer and swaps in what changed;
-  `window.__BRENDER_HYDRATION__.refreshed` counts it. A page that is not
-  stale sends nothing extra. See `@symbo.ls/fetch`, "A pre-built page shows
+  took a recorded answer and swaps in what changed. A page whose first
+  recorded answer is taken later (a `getDB()` read in `onRender`) refreshes
+  after that take, once its view settled again.
+  `window.__BRENDER_HYDRATION__.refreshed` counts it; on a replaced page that
+  object is `{ replaced: true, refreshed }`. A page that is not stale sends
+  nothing extra. See `@symbo.ls/fetch`, "A pre-built page shows
   the data of its build".
 
 ## Plugins