diff --git a/REQUIREMENTS.md b/REQUIREMENTS.md
index e8663fb..6d88d83 100644
--- a/REQUIREMENTS.md
+++ b/REQUIREMENTS.md
@@ -296,6 +296,16 @@ the daily unlock is needed on this path are both answered: it is, and this is th
 > the `+` pod, which reportedly never needed the blessing, or re-linking the `−` pod inside
 > its ~50 s window.
 
+> **The command channel works; a keep-alive on it does not help — 2026-08-27.** Writing
+> `00 08 00` gets a `0x3c` reply carrying device metadata: name `Zwift Click`, `0B-34C45903A18E`,
+> version `B.0`, type byte `0x0B`, address. Sent every 10 s across a full run, the pod
+> answered every one — **including after the cliff**, while refusing to report a single
+> button. Last button frame 51.62 s, `flag=1 timer=900` at 51.75 s, nothing after.
+>
+> That is the sharpest framing of the fault so far: the link is healthy, the device is
+> responsive, and it is withholding *one capability* on a timer. A periodic message is not
+> what re-arms it.
+
 > **Do not send `play-rideon` casually.** It reliably blanks the pod's output stream and
 > costs a recovery wait. It is kept in the probe because reproducing a finding matters, not
 > because it is safe to leave running.