docs: runbook token listing reads the items envelope (sage)

Darkwing's correction, checked against the 2.7.0 OpenAPI: GET /tokens returns PaginatedAPIToken, with items possibly null. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-08 17:17:18 -05:00
parent 67d29f7da5
commit 7780ef1e54
2 changed files with 6 additions and 1 deletions
@@ -1246,3 +1246,8 @@ which stay with him. Each item names who decided it and what happened.
      names `GET /tokens?owner_id=<bot id>` as svc for finding an old
      id. The async update lag has an upper bound of 5 s under load,
      inside S3's 60 s overlap window (section U).
+    - Correction (Darkwing, same day): `GET /tokens` answers with the
+      paginated `{items, ...}` envelope (`PaginatedAPIToken` in the
+      2.7.0 OpenAPI), not a bare array. The probe's `items ?? body`
+      read hid it. The runbook's listing line now reads `.items[]?`,
+      which also covers a null `items`.