@deepdockai/cli 1.0.27 → 1.0.28

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 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.28";
 
 // 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.28",
   "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

@@ -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