@lotics/cli 0.321.4 → 0.321.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/docs/design.md CHANGED
@@ -428,8 +428,9 @@ an app (`app_architecture`).
428
428
  A record is a head, its parts and at most one Side. From three parts it shows one part at a time; fewer stack. A part is one area of the record's data a person comes to for its own job, like the tabs of a settings page; its related lists and field groups sit inside it under their headings. A status's stages are not areas: their acts stand at the foot of the rows they move. State each
429
429
  part whole for the work there: a field may stand in any number of parts, and a field an Act requires draws beside it
430
430
  unstated. A step may hold nothing but its name. What a person needs in view at every part (who it is for, how to reach
431
- them) goes in a Side: it leaves the head and stays on the rows. The status stands in the head or the Side, never a
432
- Section. `row` changes how the app's rows read, never a page nor what the app writes. A List, Reading, Statement or Act stated alike in several
431
+ them) goes in a Side: it leaves the head and stays on the rows; what only a stage's Act writes (an invoice's number,
432
+ a delivery's signature) stands empty before it, so it goes in that stage's Section (`at`), never the Side. The status
433
+ stands in the head or the Side, never a Section. `row` changes how the app's rows read, never a page nor what the app writes. A List, Reading, Statement or Act stated alike in several
433
434
  Sections draws once, in the first; a Check stated in a Section guards the whole record.
434
435
 
435
436
  The Record's Sections, in the order the work reaches them: the fields people write, a Field per paper the record
@@ -125,7 +125,7 @@ The `html` and `email` types print a raw value through a helper in the template'
125
125
 
126
126
  A field can also print as a **QR code** or a **Code 128 barcode** (a picture a phone's camera or a scanner reads back): `{{qr link}}` or `{{code128 position 6}}` in html (never email: mail clients do not show the picture, and a save refuses it), `{{position | qr}}` or `{{position | code128:6}}` as a whole Excel cell (its row grows to the picture), `{{IMAGE qr(position)}}` or `{{IMAGE code128(position, 6)}}` in Word. The optional number is the picture's width in centimetres. Without it the width follows the value's length — each module prints 0.5 mm in a QR code and 0.33 mm in a barcode, so a longer value prints wider; a width that would shrink a module below what a scanner reads (0.3 mm, 0.19 mm) is refused, naming the least width that scans. An empty field draws nothing.
127
127
 
128
- A record's **photos** (a files field, an act's paper hands each as a file cell `{id, name, mime, url}`) print too, and only for a file whoever makes the paper may read — the same rule the file proxy applies; any other file is never drawn. html: `{{#each photos}}<img src="{{url}}">{{/each}}` (only the data's file cells are inlined; a url typed into a text field stays a link). Word: `{{IMAGE picture(cover, 8)}}`, and `{{FOR p IN photos}}{{IMAGE picture($p, 8)}}{{END-FOR p}}` for several. Excel: `{{cover | picture:6}}` as the whole cell, or `{{this | picture}}` inside `{{#each photos}}` (each row grows to its picture). The number is the width in centimetres (8, or 6 in Excel, by default). `picture` takes one image file: a list (loop over it), a file that is no image or one that cannot be read is refused by name. Photos are embedded at most 1600 pixels across, about 200 dpi at 20 cm.
128
+ A record's **photos** (a files field, or a lookup of one through its links, an act's paper hands each as a file cell `{id, name, mime, url}`) print too, and only for a file whoever makes the paper may read — the same rule the file proxy applies; any other file is never drawn. html: `{{#each photos}}<img src="{{url}}">{{/each}}` (only the data's file cells are inlined; a url typed into a text field stays a link). Word: `{{IMAGE picture(cover, 8)}}`, and `{{FOR p IN photos}}{{IMAGE picture($p, 8)}}{{END-FOR p}}` for several. Excel: `{{cover | picture:6}}` as the whole cell, or `{{this | picture}}` inside `{{#each photos}}` (each row grows to its picture). The number is the width in centimetres (8, or 6 in Excel, by default). `picture` takes one image file: a list (loop over it), a file that is no image or one that cannot be read is refused by name. Photos are embedded at most 1600 pixels across, about 200 dpi at 20 cm.
129
129
 
130
130
  A Word command (`{{ … }}`) reads the data and calls, by name, a Word helper (`picture`, `qr`, `code128`) or one of these text
131
131
  and number functions: `trim`, `trimStart`, `trimEnd`, `lower`, `upper`, `capitalize`, `replace`, `replaceAll`, `removeChars`, `removeSpaces`,
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.4",
3
+ "version": "0.321.6",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {