@lotics/cli 0.321.65 → 0.321.67

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.
@@ -3827,10 +3827,9 @@ above. A provider's refusal carries the provider's own words.
3827
3827
 
3828
3828
  ### request_locked_record_change (workflow step)
3829
3829
 
3830
- - Submit one change request to change locked field values on a record.
3831
- - Include every blocked field in the same call — the approver accepts or rejects the change set as a whole.
3832
- - Values are NOT changed immediately; an approver must accept the request first.
3833
- - Returns `{ request_id, status }`.
3830
+ - Submit one change to locked field values on a record, with its reason.
3831
+ - Include every blocked field in the same call — the change set is accepted or rejected as a whole.
3832
+ - The people who manage the table decide it before any value changes (`status: "pending"`, with `request_id`); a table whose `locked_change` is `tell` writes it at once and tells them (`status: "applied"`).
3834
3833
 
3835
3834
  **Inputs**
3836
3835
 
@@ -3845,8 +3844,8 @@ above. A provider's refusal carries the provider's own words.
3845
3844
 
3846
3845
  | Name | Type | Required | What it is |
3847
3846
  | --- | --- | --- | --- |
3848
- | `request_id` | string | yes | |
3849
- | `status` | "pending" | yes | |
3847
+ | `request_id` | string | | |
3848
+ | `status` | "pending" \\| "applied" | yes | |
3850
3849
 
3851
3850
  ## save
3852
3851
 
@@ -37,7 +37,7 @@ A keyed entry is removed by `null`: a field, check, view, option, instruction, q
37
37
 
38
38
  ## Locking and changing a locked record
39
39
 
40
- `update_records` with `locked: true` locks the targets (write access) and `locked: false` unlocks them (the table's manager). Beside field edits, a record that is locked before and after the call is refused into `blocked`; an unlock lands before the edit and a lock after it. `request_change: { reason }` files one change request per blocked record instead, carrying the values the call resolves, and lists them in `requested` as `{ record_id, request_id }`; the unlocked targets of the same call are written, and the call and its requests are one transaction, so a request that cannot be filed leaves them unwritten too.
40
+ `update_records` with `locked: true` locks the targets (write access) and `locked: false` unlocks them (the table's manager). Beside field edits, a record that is locked before and after the call is refused into `blocked`; an unlock lands before the edit and a lock after it. `request_change: { reason }` files one change request per blocked record instead, carrying the values the call resolves, and lists them in `requested` as `{ record_id, request_id }`; the unlocked targets of the same call are written, and the call and its requests are one transaction, so a request that cannot be filed leaves them unwritten too. A table whose `locked_change` is `tell` writes the locked record at once instead, tells the people who manage it, and lists the record in `applied`.
41
41
 
42
42
  ## Undoing a write
43
43
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@lotics/cli",
3
- "version": "0.321.65",
3
+ "version": "0.321.67",
4
4
  "description": "Lotics SDK and CLI for AI agents",
5
5
  "type": "module",
6
6
  "bin": {