@lotics/cli 0.316.21 → 0.316.23

package/docs/data_model.md

@@ -163,6 +163,8 @@ A table is named by its alias wherever a call names one (`table_id`, a link's `t
 - A link names its table by id, or by the `ref` of another table of the same call, and states its `multi`. A two-way link
   states `pair` on one table, as `true` or as a free alias, and the platform makes the partner on the other table with the
   inverse cardinality; a many-to-many link states both sides, since the inverse of many is not decided.
+  A link to its own table pairs with itself when `pair` is `true`, and with a second field of that table when `pair` names it
+  (a parent and its children).
   A link already holding rows is paired the same way, with its partner stated beside it in the call: the partner is filled from
   the links the rows hold and no cell of the link is rewritten. `pair: null` lets a pair go, both fields staying one-way links
   with their values; a field that holds one row, the partner or the link itself, refuses a pair two rows would crowd, naming the rows.

package/docs/design.md

@@ -111,7 +111,7 @@ second, and a free stretch adds a row there. `loads` reads what a lane carries a
 
 #### Gantt
 
-`layout: {"gantt": {"start": …}}` (and `end`, else the table's first `due`): one bar a row over
+`layout: {"gantt": {"start": …}}` (and `end`, else the table's first `due`; a `due` is a deadline, never an appointment date): one bar a row over
 its run of days — a shipment, a hire, a task of a project — read against today. `milestones` marks
 dates on the bar, `planned` the plan under it, `progress` how far it is done, `after` the rows it waits on;
 the List's `group` is its lanes. Worked: `examples/gantt`.

package/docs/first_build.md

@@ -177,4 +177,4 @@ run_app_workflow {"app_id": "app_…", "alias": "act_start_baking", "inputs": {"
 screenshot_app {"app_id": "app_…"}
 ```
 
-Fix a failure in the table or app that causes it. Leave standing instructions with `set_workspace` (`instructions`, one entry per rule): who the business is, the words its people use, what any agent working here must keep to. As an admin, invite the people the brief names with `set_members` (`members` keyed by email, role `member` or `admin`); where the tool is missing, say whom to invite. Then show the owner what you built, job by job, each paper they sent and what makes it, with the choices you made for them to change.
+Fix a failure in the table or app that causes it. Leave standing instructions with `set_workspace` (`instructions`, one entry per rule): who the business is, the words its people use, what any agent working here must keep to. As an admin, invite the people the brief names with `set_members` (`members` keyed by email, role `member` or `admin`), else say whom to invite. Then show the owner what you built, job by job, each paper and what makes it, empty fields they named, how mail is sent (a Gmail or Outlook step, or by hand), with the choices you made for them to change.

package/package.json

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