@deepdockai/cli 1.0.11 → 1.0.13

package/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 1.0.13
+
+- A device carries `lastKnownAt`: the time of its last report while it is not connected, `null` while it is connected. Every system of a device carries `lockedActions`: the actions the device reports locked because its database account lacks a right they need, under the spec set it runs now, or `null` when there is no verdict or the verdict is for an older spec set. Both are in the device list and, for `lockedActions`, in `GET /v1/devices/{deviceId}/systems`. The agent skill's TypeScript client types them, and its concepts reference explains them.
+
+## 1.0.12
+
+- The agent skill describes `rate_limited` for action calls: 600 calls and 120 writes per minute per API key, answered with `Retry-After: 60` and `retryAfterSeconds: 60`. It named only the pairing limit before.
+
 ## 1.0.11
 
 - Every system of a device carries `accessLastCheckedAt`, in the device list and in `GET /v1/devices/{deviceId}/systems`. It is set when `access` is the last known value because the device could not read it (its database stopped or unreachable), and then says when the device last read it. It is `null` whenever the latest report read the access. The agent skill's TypeScript client types it, and its concepts reference explains it.

package/dist/deepdock.js

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.11",
+  "version": "1.0.13",
   "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/auth-and-keys.md

@@ -84,7 +84,7 @@ curl -X POST "$BASE/v1/devices" \
 ```
 
 `label` is optional, 1 to 100 characters. The device must be online. Answer: `201` with the device
-(`id`, `label`, `hostname`, `os`, `clientVersion`, `status`, `lastSeenAt`, `claimedAt`, `outdated`, `systems`,
+(`id`, `label`, `hostname`, `os`, `clientVersion`, `status`, `lastSeenAt`, `lastKnownAt`, `claimedAt`, `outdated`, `systems`,
 and `updateAvailable` when it runs an older build); `hostname`, `os` and `clientVersion` are `null`
 until the device has reported them. Keep `id`: it is the `deviceId` of every later call.
 `GET /v1/devices` lists your devices a page at a time (`{ items, nextCursor }`; pass `nextCursor` back as `cursor` until it is `null`, `limit` 1 to 500, default 100), and `GET /v1/devices/{deviceId}` reads one; each device has the same shape. `GET /v1/incidents` pages the same way.

package/skill/references/calling-actions.md

@@ -98,9 +98,12 @@ Never invent an id, copy one from another device, or hard-code one from a test r
 
 ## Rate limits
 
-The only documented limit is on pairing: 5 failed claim attempts per key per rolling 60 seconds
-(`429 rate_limited`). Handle `429` generically anyway (honour `Retry-After` when present, back off,
-do not loop), since limits can be added additively.
+Each API key has its own budget on every `/v1` call: 600 calls per minute, and 120 writes per
+minute. A write (an action run that needs an `Idempotency-Key`) counts against both. Over a budget
+the call answers `429 rate_limited` with `Retry-After: 60` and `retryAfterSeconds: 60` in the error
+body. Honour it, back off and do not loop; a retried write keeps its `Idempotency-Key`. The numbers
+can change, so treat them as approximate. Pairing has a tighter limit of its own: 5 failed claim
+attempts per key per rolling 60 seconds, whose `429` carries neither the header nor the field.
 
 ## Response headers worth reading
 

package/skill/references/clients/deepdock.ts

@@ -70,6 +70,8 @@ export type Device = {
   clientVersion: string | null
   status: 'connected' | 'offline' | 'inactive'
   lastSeenAt: string | null
+  /** While the device is not connected: when it last reported. `null` while connected. */
+  lastKnownAt: string | null
   claimedAt: string | null
   /** True when an action assigned to you needs a newer client: that action answers device_outdated. */
   outdated: boolean
@@ -81,6 +83,7 @@ export type Device = {
     access: SystemAccess
     /** Set when `access` is the last known value (the device could not read it): when it last did. */
     accessLastCheckedAt: string | null
+    lockedActions: string[] | null
     reportedAt: string
     writes: SystemWrites
   }[]
@@ -100,6 +103,8 @@ export type DeviceSystem = {
   access: SystemAccess
   /** Set when `access` is the last known value (the device could not read it): when it last did. */
   accessLastCheckedAt: string | null
+  /** Actions the device reports locked because its database account lacks a right they need; `null` when there is no verdict for the spec set it runs now. */
+  lockedActions: string[] | null
   actions: ActionState[]
 }
 

package/skill/references/concepts.md

@@ -24,7 +24,7 @@ Details: [auth-and-keys.md](auth-and-keys.md).
 The Deepdock client installed on the customer's Windows PC next to their system. It connects
 outwards to Deepdock; nothing in the customer's network is opened to the internet. A device is
 identified by a UUID (`id`), carries a `label`, `hostname`, `os`, `clientVersion`, `status`
-(`connected`, `offline` or `inactive`), `lastSeenAt`, `claimedAt` (may be `null`), `outdated` (an
+(`connected`, `offline` or `inactive`), `lastSeenAt`, `lastKnownAt`, `claimedAt` (may be `null`), `outdated` (an
 assigned action needs a newer client: it answers `device_outdated`) and the `systems` it reported (each with a `writes` state; reads always work). `verified`: writes run. `unknown`: no version was reported, and writes go through. `partial`: some writes run and some are refused. `unverified`: a write answers `system_version_unverified`; with `reason: unverified_version` it works once Deepdock has verified that version, with `reason: unparseable` retrying does not help and you contact Deepdock.
 
 - **Pair**: claim a device for your organisation with the 6-character code it shows while unpaired.
@@ -48,12 +48,14 @@ has a display `label` (may be `null`), a `version` the device reported (may be a
 | device `status` | `connected` | the device is online and can run actions | normal |
 | device `status` | `offline` | the device is not connected right now (PC off, no network) | calls answer `device_offline`; retry later, show "offline" |
 | device `status` | `inactive` | not connected for 7 days; still paired | as offline; check with the site whether the PC still exists |
+| device `lastKnownAt` | ISO time or `null` | the time of the device's last report while it is not connected. `null` while it is connected | show the last known state with this time; it may be out of date |
 | system `status` | `running` | the customer's program is running on the device | normal |
 | system `status` | `stopped` | the program is installed but not running | calls answer `system_unavailable`; the site starts the program |
 | system `status` | `missing` | the program was not found where the device expects it | calls answer `system_unavailable`; contact the site and Deepdock |
 | system `status` | `unknown` | the device could not tell whether the program runs (its probe failed or is unavailable on that PC) | do not read it as stopped; the device decides when a call arrives |
 | system `access` | `ok`, `outdated`, `missing`, `not_set_up`, or `null` | the database access the device last reported (`null`: none known yet) | `outdated` refuses the actions that need the missing right with `access_outdated`, `missing` refuses every action with `access_missing`; the customer repeats "Erneut einrichten" in the Deepdock client, the incident closes by itself once `access` is `ok`, nothing to resume |
 | system `accessLastCheckedAt` | ISO time or `null` | set when `access` is the last known value because the device could not read it (its database stopped or unreachable): when it last read it. `null` when the latest report read it | show the access as last known, with this time; nothing to do until the device reads it again |
+| system `lockedActions` | list of action names or `null` | the actions the device reports locked because its database account lacks a right they need, under the spec set it runs now. `null`: no verdict yet, or the verdict is for an older spec set | do not offer a locked action as available; it answers `access_outdated` until the customer repeats "Erneut einrichten" |
 | action state | `active` | the action can be called | normal |
 | 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 |

package/skill/references/errors.md

@@ -17,7 +17,7 @@ with the **same** `Idempotency-Key`); **Show** says what the end user should see
 | `payload_too_large` | 413 | the request body is over 1 MiB | no; send less | nothing; a developer bug, or shorten the text |
 | `unauthenticated` | 401 | the key is missing, malformed, for the other environment, unknown, revoked or expired | no | "Deepdock API key refused; check it in the dashboard" to an operator |
 | `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 | too many failed pairing attempts with this key (5 per 60 s) | yes, after up to a minute (`Retry-After` when present) | "try again in a minute" |
+| `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