@deepdockai/cli 1.0.18 → 1.0.19

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 1.0.19
+
+- 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.
+
 ## 1.0.18
 
 - 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.

package/dist/deepdock.js

@@ -10861,6 +10861,7 @@ var EXIT_CODES = {
   pairing_code_invalid: 2,
   other_partner_build: 2,
   device_learning_only: 2,
+  device_answer_unreadable: 2,
   device_connected_twice: 2,
   rate_limited: 2,
   target_rejected: 2,
@@ -11431,7 +11432,7 @@ import { spawn } from "node:child_process";
 import { homedir, hostname } from "node:os";
 
 // src/version.ts
-var VERSION = "1.0.18";
+var VERSION = "1.0.19";
 
 // src/runtime.ts
 var DEFAULT_BASE_URL = "https://api.deepdock.ai";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.18",
+  "version": "1.0.19",
   "description": "Deepdock partner CLI: pair devices, see systems and actions, create the API key your code runs them with.",
   "type": "module",
   "license": "MIT",

package/skill/references/errors.md

@@ -38,6 +38,7 @@ dashboard-only.
 | `other_partner_build` | 409 | pairing: the device runs another partner's client build | no | "this device is set up for another provider" |
 | `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" |
 | `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" |
+| `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" |
 
 ## Input
 
@@ -93,6 +94,7 @@ const REACTION: Record<string, Reaction> = {
   other_partner_build: 'stop',
   device_learning_only: 'stop',
   device_connected_twice: 'stop',
+  device_answer_unreadable: 'stop',
   invalid_input: 'fix-input',
   target_rejected: 'fix-input',
   unknown_author: 'fix-input',