docs: runbook section 5 lists a bot's token ids as svc (sage)

Darkwing's probe-s7f: svc-$BIZ revokes one bot token (204, then 401); the owner gets 403. A plain GET /tokens shows only svc's own tokens, so rotation names GET /tokens?owner_id=<bot id> for an old id. Decision 68 records the resolution. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-08 17:16:51 -05:00
parent 28fbdec97d
commit 67d29f7da5
2 changed files with 13 additions and 1 deletions
@@ -1239,3 +1239,10 @@ which stay with him. Each item names who decided it and what happened.
      an estate rule. Jason is away 10-10, so the runbook's Vikunja
      sections run on 10-11 at the earliest, depending on T236. R20 is
      confirmed to Mos: Sage is the stack's PM and Darkwing its Lead.
+    - Resolved (Darkwing, `probe-s7f.mjs`, probes.md section R):
+      `svc-$BIZ` revokes its bot's token with `DELETE /tokens/{id}`
+      (204, then 401 on the next request). The bot's other tokens keep
+      working. The owner's revoke gets 403. The runbook's section 5 now
+      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).