@lotics/cli 0.55.0 → 0.57.0

package/dist/starter_template.js

@@ -379,10 +379,10 @@ mount(
             path: "src/App.tsx",
             // Default scaffold = a minimal in-app router example (a list screen and a
             // detail screen), so a new app starts with the recommended routing shape:
-            //   - The app uses react-router via `AppRouter` (from @lotics/app-sdk/router),
-            //     which makes screens real addressable URLs — embedded, they live in the
-            //     host address bar (?_loc=…) and the browser Back/Forward walk screens;
-            //     standalone, real path URLs.
+            //   - The app uses react-router via `AppRouter` (from @lotics/app-sdk/router).
+            //     The app owns its own url — embedded, that's the iframe's own url (the
+            //     host never sees it, so navigation never reloads the app); standalone,
+            //     real path URLs. Browser Back/Forward walk app screens in both.
             //   - The full-container layout pattern is preserved in `Screen`: an outer
             //     <View flex:1> claims the iframe height (index.html sets
             //     html/body/#root to 100% + #root is a flex column). Keep that chain
@@ -397,11 +397,13 @@ import { Card } from "@lotics/ui/card";
 import { Text } from "@lotics/ui/text";
 import { Button } from "@lotics/ui/button";
 
-// AppRouter makes the app's screens real, addressable URLs — write plain
-// react-router (useNavigate / useParams / <Link>) and it handles both modes:
-//   - Embedded in the Lotics host: the current screen lives in the host address
-//     bar (?_loc=…) — shareable + refresh-survivable — and the browser Back /
-//     Forward buttons walk app screens (then leave the app).
+// AppRouter makes the app's screens real URLs — write plain react-router
+// (useNavigate / useParams / <Link>) and it handles both modes. The app owns its
+// own url, so navigation never reloads the app:
+//   - Embedded in the Lotics host: the app drives the iframe's OWN url (invisible
+//     to the user, never seen by the host). Browser Back / Forward walk app
+//     screens; the screen is also mirrored to the host url, so it's shareable and
+//     survives a full refresh (handled by AppRouter — no extra code).
 //   - Standalone at <slug>.lotics.app: a normal browser router with real path URLs.
 
 const ITEMS = [
@@ -648,10 +650,11 @@ the full export list at https://www.npmjs.com/package/@lotics/ui.
 ## Routing
 
 \`src/App.tsx\` ships a minimal in-app router. Write plain react-router and wrap
-your routes in \`AppRouter\` from \`@lotics/app-sdk/router\` — it makes screens real,
-addressable URLs in both modes: embedded in the Lotics host the current screen
-lives in the host address bar (\`?_loc=…\`, shareable + refresh-survivable) and the
-browser Back/Forward walk app screens; standalone (\`<slug>.lotics.app\`) it's a
+your routes in \`AppRouter\` from \`@lotics/app-sdk/router\` — the app owns its own
+url, so navigation never reloads the app. Embedded in the Lotics host it drives
+the iframe's own url (invisible to the user, never seen by the host); browser
+Back/Forward walk app screens, and the screen is mirrored to the host url so it's
+shareable and survives a full refresh. Standalone (\`<slug>.lotics.app\`) it's a
 normal browser router with real path URLs. A single-screen app can drop the
 router and render one screen directly.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lotics/cli",
-  "version": "0.55.0",
+  "version": "0.57.0",
   "description": "Lotics SDK and CLI for AI agents",
   "type": "module",
   "bin": {