@uniweb/core 0.26.1 → 0.26.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/core",
-  "version": "0.26.1",
+  "version": "0.26.2",
   "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
   "type": "module",
   "exports": {

package/src/page.js

@@ -600,11 +600,23 @@ export default class Page {
    * is "give me the page to render *here*," not "give me the next URL
    * with content."
    *
-   * Used by SSR paths (Cloudflare Worker isolate today; framework SSG
-   * pre-handles this differently via expandDynamicPages) to avoid
-   * rendering nothing when an author requests `/docs` and the page is
-   * a folder whose actual landing content lives in `/docs/intro` flagged
-   * as `isIndex: true`.
+   * The case it exists for: an author requests `/docs`, the page is a folder
+   * with no content of its own, and its actual landing content lives in
+   * `/docs/intro` flagged `isIndex: true`.
+   *
+   * ⭐ **ONE CALLER, AND IT IS THE RULE FOR BOTH OF THE RENDERER'S TARGET FORMS:**
+   * `createPageRenderer().render()` (`@uniweb/runtime`) applies this after
+   * resolving, so a route and an already-resolved Page promote identically.
+   * Ruled 2026-09-12 [Diego], closing an asymmetry in which the same page rendered
+   * differently depending on which form the caller held — silently, with no error
+   * on either path.
+   *
+   * ⚠️ **It briefly had NO caller** (2026-09-12), after an SSR consumer replaced its
+   * hand-composed sequence with `render()`. An earlier version of this paragraph
+   * named that consumer and claimed the static build "pre-handles this differently
+   * via expandDynamicPages"; **both halves were wrong** — the static build never
+   * called this at all: it emits a redirect to the first descendant with content
+   * (`getNavigableRoute`) rather than promoting anything.
    *
    * @returns {Page} The page to render — `this` or its index child.
    */