@lotics/cli 0.266.0 → 0.267.0

package/docs/building_an_app.md

@@ -145,9 +145,22 @@ template you registered once (`lotics docs document_templates`).
 
 ## 7 — Look at it, then name it
 
-Open the app and look at it at a desktop width and at a phone's — every check above reads the
-definition, none of them the pixels. A version that looks wrong is one `lotics run rollback_app`
-away from the one before.
+Look at every app you apply, at a desktop width and at a phone's — every check above reads the
+definition, none of them the pixels:
+
+```
+lotics run screenshot_app '{"app_id":"app_…"}'
+# one PNG per width, saved as a workspace file; "path":"/rec_…" opens a screen inside the app
+lotics download <file_id>
+```
+
+Each shot is one screen, as a member sees it; `"full_page":true` grows it to the list scrolling
+inside the app. Beside each image comes its `snapshot`, the screen's accessibility tree as text —
+read it to check labels and values without opening the picture.
+
+The app is drawn live, as you, read-only: a screen that writes when it opens shows that write
+refused, and `errors` lists what failed on the page. A version that looks wrong is one
+`lotics run rollback_app` away from the one before.
 
 Then set the icon, the colour and the app's own `description` through `lotics run update_app`. The
 `description` heads the capability listing the member's chat agent reads on **every** turn, so a

package/package.json

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