@deepdockai/cli 1.0.9 → 1.0.11

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 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.
+
+## 1.0.10
+
+- `GET /v1/devices` and `GET /v1/incidents` page with a cursor: the answer is `{ items, nextCursor }`, with `limit` (1 to 500, default 100) and `cursor` query parameters. The agent skill's key and pairing reference says how to loop over the pages, and the pinned device API carries the new shape. The CLI lists devices through `/partner`, which is unchanged.
+- The pinned device API documents the per-key `429 rate_limited` (600 calls and 120 writes per minute per API key, `Retry-After`).
+
 ## 1.0.9
 
 - The CLI knows `device_learning_only` (exit code 2, refused): the PC runs the Deepdock client for learning only, which runs no actions, so action calls and the systems list on it are refused before anything is sent. It changes only when the Deepdock service is installed on that PC; retrying does not help. The skill's error reference lists 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.9";
+var VERSION = "1.0.11";
 
 // src/runtime.ts
 var DEFAULT_BASE_URL = "https://api.deepdock.ai";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@deepdockai/cli",
-  "version": "1.0.9",
+  "version": "1.0.11",
   "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

@@ -87,7 +87,7 @@ curl -X POST "$BASE/v1/devices" \
 (`id`, `label`, `hostname`, `os`, `clientVersion`, `status`, `lastSeenAt`, `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 and `GET /v1/devices/{deviceId}` reads one, in the same shape.
+`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.
 
 4. Release with `DELETE /v1/devices/{deviceId}`; the device then shows a new code.
 

package/skill/references/clients/deepdock.ts

@@ -79,6 +79,8 @@ export type Device = {
     version: string | null
     status: SystemStatus
     access: SystemAccess
+    /** Set when `access` is the last known value (the device could not read it): when it last did. */
+    accessLastCheckedAt: string | null
     reportedAt: string
     writes: SystemWrites
   }[]
@@ -96,6 +98,8 @@ export type DeviceSystem = {
   version?: string
   status: SystemStatus
   access: SystemAccess
+  /** Set when `access` is the last known value (the device could not read it): when it last did. */
+  accessLastCheckedAt: string | null
   actions: ActionState[]
 }
 

package/skill/references/concepts.md

@@ -53,6 +53,7 @@ has a display `label` (may be `null`), a `version` the device reported (may be a
 | 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 |
 | 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 |