docs: update portal for WRNexusJS 0.2.31

public/llms.txt

@@ -1,4 +1,4 @@
-# WRNexusJS documentation 0.2.30
+# WRNexusJS documentation 0.2.31
 
 Status: Private Developer Preview. This site documents 26 release-aligned packages.
 
@@ -281,7 +281,7 @@ wrnexus eject <component>     # copy a Wire UI component's .wrn into app/compone
 
 # Installed package documentation
 
-The following README files and declarations come from the installed private 0.2.30 release.
+The following README files and declarations come from the installed private 0.2.31 release.
 
 ## @wrnexus/ai
 
@@ -1271,6 +1271,15 @@ interface ModeFunctionsBlock {
     mode: DataMode;
     body: string;
 }
+interface LifecycleBlock {
+    mount?: string;
+    update?: string;
+    unmount?: string;
+}
+interface WatchBlock {
+    state: string;
+    body: string;
+}
 interface RealtimeHandler {
     event: string;
     args: string[];
@@ -1304,6 +1313,8 @@ interface PageAst {
     functions: string[];
     dataApis: DataApiBlock[];
     modeFunctions: ModeFunctionsBlock[];
+    lifecycle: LifecycleBlock;
+    watches: WatchBlock[];
     apis: ApiBlock[];
     realtimes: RealtimeBlock[];
 }
@@ -2738,14 +2749,15 @@ declare const REACTIVE_RUNTIME: string;
  * Progressive enhancement over normal links: intercepts same-origin `<a>`
  * clicks, fetches the target page's HTML, swaps the `#app` container in place,
  * updates history/title/scroll, ensures any framework runtimes the new page
- * needs are present, and re-hydrates. Anything unexpected (cross-origin,
- * modified click, non-HTML response, missing `#app`) falls back to a full
- * browser navigation, so behaviour degrades safely.
+ * needs are present, and re-hydrates.
  *
- * Data "loaders": pages load their data on the server (SSR `api` bindings), so
- * the fetched HTML already contains fresh data — no separate client loader is
- * needed. Client-side (`csr`) bindings and reactive scopes re-hydrate after the
- * swap. Programmatic navigation is exposed as `window.__wrnexusNavigate(url)`.
+ * Before replacing the current page, component lifecycle behaviors are
+ * explicitly disposed. This ensures `unmount` hooks and watcher cleanups run
+ * before the old DOM is removed.
+ *
+ * Programmatic navigation is exposed as:
+ *
+ *   window.__wrnexusNavigate(url)
  */
 declare const NAV_RUNTIME: string;