@lotics/cli 0.178.0 → 0.179.0

package/dist/src/cli.js

@@ -45711,7 +45711,7 @@ function resultSideEffects(result) {
 }
 
 // src/version.ts
-var VERSION = "0.178.0";
+var VERSION = "0.179.0";
 
 // src/timezone.ts
 function machineTimezone() {

package/docs/building_an_app.md

@@ -49,6 +49,14 @@ needs.
 look at fill rates — a field that is present and empty on 90% of rows will not support the screen
 you are about to design.
 
+**That includes imagery.** If the entity has a likeness — a product, a property, a vehicle, a
+person — its picture is the strongest identifier a register row can carry, and an empty image field
+is a data gap to fill before you design around it (see `lotics docs composition`, §Character comes
+from the DATA). Fill it the same way you fill any other field: put the file on the record. Where the
+images do not exist yet, generate them out of band and `lotics file upload` + `update_records` them
+on — and keep one style across the whole set, because a catalogue whose shots disagree about
+lighting and background reads worse than one with no pictures at all.
+
 ## 4 — Typed field access
 
 ```
@@ -132,7 +140,8 @@ empty path — green, and proving nothing about the branch you care about.
 Then prove it end to end without a screen:
 
 ```
-lotics app workflow run <alias> '<json>'    # exits non-zero on error, so it is assertable
+lotics run run_app_workflow '{"app_id":"app_…","alias":"…","inputs":{…}}'
+# exits non-zero on error, so it is assertable
 ```
 
 A workflow is also how an app **produces a document** — an invoice, a debit note, a shipping
@@ -246,7 +255,7 @@ Once scaffolded, everything below happens locally:
 edit src/workflows/<alias>.ts        # or a screen, or a query
 lotics app codegen                   # after any schema change
 npm run typecheck                    # honest, because codegen is current
-lotics app workflow run <alias> …    # prove the mutation path
+lotics run run_app_workflow '{"app_id":…,"alias":…}'   # prove the mutation path
 lotics app dev                       # prove the screen
 …
 lotics app workflow set <alias>      # push the body; the server verifies

package/package.json

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