@deepdockai/cli 1.0.27 → 1.0.29

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 1.0.29
+
+- A paused action's `reason` can also read `credentials_rejected` (the program no longer accepts the stored sign-in) or `certificate_changed` (the program's server certificate changed). Both are fixed by the customer choosing "Anmeldung erneuern" in the Deepdock client, and the action resumes by itself. Calls answer `action_paused` meanwhile, as for any pause. The bundled device types and the skill's concepts list include them.
+
+## 1.0.28
+
+- The device API's `Error.code` list no longer names `organization_required`, `forbidden`, `conflict` and `already_member`: only the dashboard tree (`/partner`) answers them, never `/v1`. The CLI still meets them on its own `/partner` calls and keeps their exit codes (`organization_required` 1, the other three 2), now from a list of its own. Nothing changes for a script that reads `--json` or the exit code.
+
 ## 1.0.27
 
 - An update is called with `PATCH` again; a read and a create stay `POST`. All three take a flat JSON body and nothing in the URL. The method must be the action's own: any other answers `405 invalid_request` with `Allow` naming the one method (`POST` or `PATCH`), so a `POST` to an update is refused and does nothing. A query string on an action path is still `400 invalid_request`. A write still needs an `Idempotency-Key`; a read ignores it.

package/dist/deepdock.js

@@ -11440,7 +11440,7 @@ import { spawn } from "node:child_process";
 import { homedir, hostname } from "node:os";
 
 // src/version.ts
-var VERSION = "1.0.27";
+var VERSION = "1.0.29";
 
 // src/runtime.ts
 var DEFAULT_BASE_URL = "https://api.deepdock.ai";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.27",
+  "version": "1.0.29",
   "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/clients/deepdock.ts

@@ -106,7 +106,12 @@ export type PairBody = { code: string; label?: string }
 
 export type ActionState =
   | { action: string; state: 'active' }
-  | { action: string; state: 'paused'; reason: 'structure_changed' | 'readback_failed'; pausedAt: string }
+  | {
+      action: string
+      state: 'paused'
+      reason: 'structure_changed' | 'readback_failed' | 'credentials_rejected' | 'certificate_changed'
+      pausedAt: string
+    }
 
 export type DeviceSystem = {
   system: string

package/skill/references/concepts.md

@@ -60,6 +60,8 @@ has a display `label` (may be `null`), a `version` the device reported (may be a
 | action state | `paused` | the action is paused with a `reason` and `pausedAt` | calls answer `action_paused`; show the feature as paused, poll `GET .../systems` at a low rate |
 | pause `reason` | `structure_changed` | the system changed in a way the action depends on (for example a vendor update); Deepdock reviews and resumes | wait; nothing to do on your side |
 | pause `reason` | `readback_failed` | a write's result did not match, so nothing was saved | wait; tell the user the change was not saved |
+| pause `reason` | `credentials_rejected` | the program no longer accepts the sign-in the device stored for it (for example a changed password) | tell the user to choose "Anmeldung erneuern" in the Deepdock client; the action resumes by itself once the new sign-in works, nothing to resume |
+| pause `reason` | `certificate_changed` | the program's server certificate is not the one the device accepted at sign-in | tell the user to choose "Anmeldung erneuern" in the Deepdock client, compare the fingerprint it shows and sign in again; the action resumes by itself, nothing to resume |
 | pause `reason` | `system_stopped`, `system_missing` | as the system statuses above; these need no resume and clear when the system is back | as above |
 
 Switch on these values; any value you do not know is shown as it is.

package/skill/references/errors.md

@@ -24,9 +24,9 @@ with the **same** `Idempotency-Key`); **Show** says what the end user should see
 | `not_found` | 404 | no such route; an update whose id matches no record; a write naming a record that does not exist or belongs to another one | no | "record not found" when it is a record; otherwise a bug |
 | `rate_limited` | 429 | more than 600 calls, or more than 120 writes (counted in both), with this key in a minute; or more than 5 failed pairing claims in 60 s | yes, after `Retry-After: 60` (`retryAfterSeconds: 60` in the body); a write keeps its key. The pairing claim answer has neither: wait up to a minute | "try again in a minute" |
 
-Codes your `/v1` code never receives, listed so the enum is complete: `organization_required`
-(403), `forbidden` (403), `conflict` (409), `already_member` (409) and `client_outdated` (400) are
-dashboard-only.
+`client_outdated` (400) is in the enum but answered only to the Deepdock CLI (by its
+`X-Deepdock-Cli` version), so your own `/v1` code never receives it. The dashboard tree's own codes
+(`organization_required`, `forbidden`, `conflict`, `already_member`) are not in the `/v1` enum.
 
 ## Device, system and action resolution