@lotics/cli 0.321.119 → 0.321.121

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/build.md CHANGED
@@ -145,6 +145,6 @@ screenshot_app {"app_id": "app_…", "as_member": "<member id>", "pages": [{}, {
145
145
 
146
146
  ## 7. Hand over
147
147
 
148
- Name the workspace and its organization after the business with `set_workspace` (`name`, `organization_name`, and `organization_language`: the language its papers, invitations and members default to, `vi` until set), and leave standing instructions there (`instructions`, one entry per rule): who the business is, its people's words, what any agent here must keep to. As an admin, invite the people named with `set_members` (`members` keyed by email, role `member` or `admin`), else say whom to invite.
148
+ Name the workspace and its organization after the business with `set_workspace` (`name`, `organization_name`, and `organization_language`: the language its papers, invitations and members default to, `vi` until set), and leave standing instructions there (`instructions`, one entry per rule, keyed by the job it serves): who the business is, its people's words, and what the rows cannot tell an agent (the day its records begin). As an admin, invite the people named with `set_members` (`members` keyed by email, role `member` or `admin`), else say whom to invite.
149
149
 
150
150
  Before you report, answer each question of `design/the-rubric` with a call, and put right or name each gap. Then show the owner what you built, job by job, each paper and what makes it, with the choices you made for them to change.
package/docs/workflows.md CHANGED
@@ -941,8 +941,7 @@ One open order per reference, a row never counting against itself:
941
941
  A table workflow is what follows every committed write of a table's rows, whoever makes it: the grid, an import, an agent or
942
942
  any app. An effect that must hold for all of them belongs to the table. A button on one screen is that app's act, a value fixed
943
943
  when a row is made is `default_from`, and a rule that refuses a write is a check; a table workflow runs after the write has
944
- committed and cannot refuse it. An agent's write waits for the runs it set off, while they run and at most 10 seconds, and
945
- its answer names each that failed or had not ended.
944
+ committed and cannot refuse it.
946
945
 
947
946
  `set_workflow` writes it: the `source` opens with `on({ type, table, ... })` and carries the steps, and `enabled: false`
948
947
  keeps the workflow without running it (absent, it runs). `get_table` lists a table's workflows to whoever manages the
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.119",
3
+ "version": "0.321.121",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {