@lotics/cli 0.307.0 → 0.308.0

package/docs/design.md

@@ -19,8 +19,11 @@ rows in time, a template's act — until the model states it or declines it.
    `name` and `description`. A job is a desk a person works every day from its own list; one app per job,
    each one working register over one entity — an app per table, or one app holding every table, is no job's
    screen. What was brought into that register's rows or done to them — the files imported, the runs of a
-   batch — is read beside it as a log of the same app (`logs`, at most three), never an app of its own; a
-   second list people work as a desk is another app.
+   batch — is read beside it as a log of the same app (`logs`, at most three), never an app of its own.
+   A job is the record it moves and the rhythm it moves at — the first list it opens on. What that record
+   owns (a vehicle's papers, its services, its fines) is sections, blocks and acts of it, never an app;
+   work over another record or at another rhythm (the week's dispatch runs, beside each vehicle's file) is
+   another app, even when one person works both.
    A list worked only in passing on the way through another job — the rates a quote is priced from, the
    transfers its receipts are matched to, the statement sent from its records — is a block, a section or an
    act of that job's app, never an app of its own. A small business usually lands at four to six.
@@ -278,6 +281,8 @@ captured — and files it as a new row of the record's `timeline` child (`into`)
 - A person shows a face, a thing its picture, a file its preview, a plan its days on a time axis, a
   quantity a meter (`records.limits`) or a chart, a register its `readings` under its title, and long text
   reads whole (a `text` block).
+- Every app states its tile's colour (`theme.color`), apart from the workspace's other apps where it can be,
+  so the launcher tells the desks apart before their names are read.
 - Every category the job reads is coloured: each select option's `color`, and a `mark` where a brand or a
   glyph names it — on every option of a select read down a column (how it was paid, the channel, the mode).
 - Someone is a face wherever they are read. A person is a member field and a party a row of an entity stating

package/docs/workflow_steps.md

@@ -47,7 +47,7 @@ above. A provider's refusal carries the provider's own words.
 ### bkav_cancel_invoices (workflow step)
 
 - Cancel issued invoices.
-- A cancelled invoice still reports to the tax authority; correcting one instead is a replacement or adjustment through bkav_submit_invoices. (workflow step)
+- A cancelled invoice still reports to the tax authority; correcting one instead is a replacement or adjustment through bkav_submit_invoices. (workflow step, chat)
 
 **Inputs**
 
@@ -1069,7 +1069,7 @@ above. A provider's refusal carries the provider's own words.
 ### facebook_list_comments (workflow step)
 
 - Read the most recent comments left on a Facebook Page's posts.
-- Reply with facebook_reply_to_comment, passing the comment_id. (workflow step)
+- Reply with facebook_reply_to_comment, passing the comment_id. (workflow step, chat)
 
 **Inputs**
 
@@ -1094,7 +1094,7 @@ above. A provider's refusal carries the provider's own words.
 ### facebook_list_conversations (workflow step)
 
 - Read a Facebook Page's Messenger conversations with their recent messages.
-- Answer someone with facebook_send_message, passing the person_id. (workflow step)
+- Answer someone with facebook_send_message, passing the person_id. (workflow step, chat)
 
 **Inputs**
 
@@ -1129,7 +1129,7 @@ above. A provider's refusal carries the provider's own words.
 | --- | --- | --- | --- |
 | `connected_account_id` | string | yes |  |
 | `page_id` | string | yes | The page that owns the post the comment is on. |
-| `comment_id` | string | yes | From facebook_list_comments. (workflow step) |
+| `comment_id` | string | yes | From facebook_list_comments. (workflow step, chat) |
 | `message` | string | yes |  |
 
 **Answer**
@@ -1149,7 +1149,7 @@ above. A provider's refusal carries the provider's own words.
 | --- | --- | --- | --- |
 | `connected_account_id` | string | yes |  |
 | `page_id` | string | yes | The page the person wrote to. |
-| `person_id` | string | yes | From facebook_list_conversations. Page-scoped to this page. (workflow step) |
+| `person_id` | string | yes | From facebook_list_conversations. Page-scoped to this page. (workflow step, chat) |
 | `message` | string | yes |  |
 
 **Answer**
@@ -1187,8 +1187,8 @@ above. A provider's refusal carries the provider's own words.
 | Name | Type | Required | What it is |
 | --- | --- | --- | --- |
 | `connected_account_id` | string | yes | FedEx connected account |
-| `reference` | string | yes | The draft's reference (Open Ship index) from fedex_create_draft_shipment (workflow step) |
-| `master_tracking_number` | string |  | The master_tracking_number returned by fedex_create_draft_shipment — required to finalize the label (workflow step) |
+| `reference` | string | yes | The draft's reference (Open Ship index) from fedex_create_draft_shipment (workflow step, chat) |
+| `master_tracking_number` | string |  | The master_tracking_number returned by fedex_create_draft_shipment — required to finalize the label (workflow step, chat) |
 
 **Answer**
 
@@ -1201,7 +1201,7 @@ above. A provider's refusal carries the provider's own words.
 ### fedex_create_draft_shipment (workflow step)
 
 - Create a FedEx draft (Open Ship) booking — no label yet.
-- Confirm later with fedex_confirm_shipment. reference is a unique key you choose (e.g. the shipment order number) used to confirm or cancel. (workflow step)
+- Confirm later with fedex_confirm_shipment. reference is a unique key you choose (e.g. the shipment order number) used to confirm or cancel. (workflow step, chat)
 - Supports multiple packages, special services, and (international) customs commodities.
 
 **Inputs**
@@ -1261,7 +1261,7 @@ above. A provider's refusal carries the provider's own words.
 | --- | --- | --- | --- |
 | `reference` | string | yes |  |
 | `status` | "draft" | yes |  |
-| `master_tracking_number` | string |  | Pass this to fedex_confirm_shipment to finalize the draft (workflow step) |
+| `master_tracking_number` | string |  | Pass this to fedex_confirm_shipment to finalize the draft (workflow step, chat) |
 
 ### fedex_create_shipment (workflow step)
 
@@ -2701,7 +2701,7 @@ above. A provider's refusal carries the provider's own words.
 
 ### misa_save_bank_voucher (workflow step)
 
-- Push a bank voucher (deposit / withdrawal / transfer) into MISA AMIS. voucher_type: 1 deposit (báo có), 3 withdrawal/debit-advice (báo nợ), 2 internal transfer. bank_account_id is the company-side bank account GUID — look it up with misa_get_dictionary (data_type 8). (workflow step)
+- Push a bank voucher (deposit / withdrawal / transfer) into MISA AMIS. voucher_type: 1 deposit (báo có), 3 withdrawal/debit-advice (báo nợ), 2 internal transfer. bank_account_id is the company-side bank account GUID — look it up with misa_get_dictionary (data_type 8). (workflow step, chat)
 
 **Inputs**
 
@@ -2722,7 +2722,7 @@ above. A provider's refusal carries the provider's own words.
 | `custom_field3` | string |  |  |
 | `custom_field4` | string |  |  |
 | `custom_field5` | string |  |  |
-| `bank_account_id` | string | yes | Bank account GUID in MISA — look up via misa_get_dictionary (workflow step) |
+| `bank_account_id` | string | yes | Bank account GUID in MISA — look up via misa_get_dictionary (workflow step, chat) |
 | `account_object_code` | string |  |  |
 | `account_object_name` | string |  |  |
 | `total_amount_oc` | number | yes |  |
@@ -2885,7 +2885,7 @@ above. A provider's refusal carries the provider's own words.
 
 ### misa_save_sales_voucher (workflow step)
 
-- Push a sales voucher (invoice / sales return / discount-credit-note / sales order) into MISA AMIS. voucher_type: 11 invoice, 13 sales voucher, 12 return, 10 discount/credit note, 20 sales order. reftype refines the sub-type (e.g. 3530 unpaid sale, 3560 sales invoice, 3571 service cash). account_object_code identifies the customer in MISA — must already exist (use misa_save_dictionary first if not). (workflow step)
+- Push a sales voucher (invoice / sales return / discount-credit-note / sales order) into MISA AMIS. voucher_type: 11 invoice, 13 sales voucher, 12 return, 10 discount/credit note, 20 sales order. reftype refines the sub-type (e.g. 3530 unpaid sale, 3560 sales invoice, 3571 service cash). account_object_code identifies the customer in MISA — must already exist (use misa_save_dictionary first if not). (workflow step, chat)
 - MISA sync ack only confirms queueing; final accept/reject arrives async on the registered callback URL.
 
 **Inputs**

package/docs/workflows.md

@@ -62,8 +62,8 @@ await send_email({
 | validate | `validate({ checks: [{ fail_when: <expr>, field_key: "...", message: <expr> }, ...] });` |
 
 Every step's inputs, the values each takes and its answer: `lotics tools <name>` prints them; the steps only a body
-runs — a connection's, a mail's — are all in `workflow_steps`. `query_integration_tools` lists the workspace's
-connections and the steps each opens.
+runs — a connection's, a mail's — are all in `workflow_steps`. A person connects a service in Lotics under
+Settings → Connections; a step names that connection by its `connected_account_id`.
 
 `return` is a call, not a JavaScript `return` statement. `validate` ends the workflow with an error
 when a check's `fail_when` is truthy; the check's `field_key` names the control its message lands on —

package/package.json

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