@deepdockai/cli 1.0.17 → 1.0.19

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/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.0.19
4
+
5
+ - A device answer Deepdock cannot read answers `502 device_answer_unreadable` instead of `500 internal_error`, on action calls and the systems list; the body carries `requestId` for support. Retrying does not help until the Deepdock client on that PC is updated; after a write, read the record back before writing again, since the device may have applied it. The skill's error reference lists it, and the CLI exits with 2 for it.
6
+
7
+ ## 1.0.18
8
+
9
+ - A read or write on a record the customer's system restricts (for example a locked chart) answers `422 record_restricted`: a read returns no data instead of an empty answer, and a write writes nothing. The skill's error reference lists it, and the CLI exits with 2 for it.
10
+
3
11
  ## 1.0.17
4
12
 
5
13
  - A device whose identity is held by two PCs (a copied PC or VM snapshot) answers every call with `409 device_connected_twice`; nothing runs and the `Idempotency-Key` is free. The skill's error reference lists it, and the CLI exits with 2 for it.
package/dist/deepdock.js CHANGED
@@ -10861,6 +10861,7 @@ var EXIT_CODES = {
10861
10861
  pairing_code_invalid: 2,
10862
10862
  other_partner_build: 2,
10863
10863
  device_learning_only: 2,
10864
+ device_answer_unreadable: 2,
10864
10865
  device_connected_twice: 2,
10865
10866
  rate_limited: 2,
10866
10867
  target_rejected: 2,
@@ -10873,6 +10874,7 @@ var EXIT_CODES = {
10873
10874
  unknown_provider: 2,
10874
10875
  record_locked: 2,
10875
10876
  record_not_editable: 2,
10877
+ record_restricted: 2,
10876
10878
  payload_too_large: 2,
10877
10879
  device_offline: 3,
10878
10880
  device_syncing: 3,
@@ -11430,7 +11432,7 @@ import { spawn } from "node:child_process";
11430
11432
  import { homedir, hostname } from "node:os";
11431
11433
 
11432
11434
  // src/version.ts
11433
- var VERSION = "1.0.17";
11435
+ var VERSION = "1.0.19";
11434
11436
 
11435
11437
  // src/runtime.ts
11436
11438
  var DEFAULT_BASE_URL = "https://api.deepdock.ai";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@deepdockai/cli",
3
- "version": "1.0.17",
3
+ "version": "1.0.19",
4
4
  "description": "Deepdock partner CLI: pair devices, see systems and actions, create the API key your code runs them with.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -38,6 +38,7 @@ dashboard-only.
38
38
  | `other_partner_build` | 409 | pairing: the device runs another partner's client build | no | "this device is set up for another provider" |
39
39
  | `device_learning_only` | 409 | the PC runs the Deepdock client for learning only, which runs no actions; nothing was sent to it. Reads, writes and the systems list on it all answer this | no; it changes only when the Deepdock service is installed on that PC | "this PC needs the Deepdock service to run actions" |
40
40
  | `device_connected_twice` | 409 | two PCs are connected with this device's identity (a copied PC or VM snapshot); nothing ran, so the `Idempotency-Key` is free | no; a person shuts the copy down, and calls work again about five minutes after only one PC is connected | "two PCs use this device; shut the copy down" |
41
+ | `device_answer_unreadable` | 502 | the device sent an answer Deepdock cannot read (for example from a client build with a fault); on a write the device may have applied it. The body carries `requestId` for support | no, and not with the same `Idempotency-Key` either; it changes only when the Deepdock client on that PC is updated. After a write, read the record back before writing again | "the connected PC sent an answer that could not be read; contact Deepdock with the request id" |
41
42
 
42
43
  ## Input
43
44
 
@@ -50,6 +51,7 @@ dashboard-only.
50
51
  | `no_open_case` | 422 | the customer has no open case and the action never opens one. Nothing was written | no; open a case in the system, or name one with `caseId` | "open a case first" |
51
52
  | `record_locked` | 422 | the customer's system locks the record the write would change (for example one already billed on a case). Nothing was written | no | "this record is locked in the customer's system" |
52
53
  | `record_not_editable` | 422 | the record is not locked but is stored in a form this action cannot edit (for example a note it cannot add to without rewriting it). Nothing was written | no | "this record cannot be edited through Deepdock" |
54
+ | `record_restricted` | 422 | the customer's system restricts access to the record (for example a locked chart): a read returned no data, so an empty answer would be wrong, and a write wrote nothing | no; the practice lifts the restriction in its system | "access to this record is restricted in the customer's system" |
53
55
  | Other action-specific refusals | 422 | the action's OpenAPI description names each such code and when it fires. Nothing was written | no; fix the reference or input | the missing precondition in the user's words |
54
56
 
55
57
  ## Device and system availability
@@ -92,6 +94,7 @@ const REACTION: Record<string, Reaction> = {
92
94
  other_partner_build: 'stop',
93
95
  device_learning_only: 'stop',
94
96
  device_connected_twice: 'stop',
97
+ device_answer_unreadable: 'stop',
95
98
  invalid_input: 'fix-input',
96
99
  target_rejected: 'fix-input',
97
100
  unknown_author: 'fix-input',
@@ -99,6 +102,7 @@ const REACTION: Record<string, Reaction> = {
99
102
  unknown_provider: 'fix-input',
100
103
  record_locked: 'stop',
101
104
  record_not_editable: 'stop',
105
+ record_restricted: 'stop',
102
106
  payload_too_large: 'fix-code',
103
107
  access_outdated: 'wait-setup',
104
108
  access_missing: 'wait-setup',