docs: correct stale LDAP-role, host-probe, resilience-table, Bad-value claims; fix tasks.json (#624)

Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
2026-10-08 08:16:43 -04:00
parent f383996127
commit 2befe9f9ba
13 changed files with 42 additions and 28 deletions
@@ -428,7 +428,7 @@ which is archreview 05/STAB-18.

 - **Connection loss stales, keeping the value.** On the `Connected → Reconnecting` edge
  `MqttConnection.ConnectionLost` fires, and both ingest paths mark every **already-observed**
-  reference `BadNoCommunication` with its **last value retained** and publish the change. A
+  reference `BadNoCommunication` with its **last value retained** (server-side; a client reads the Bad status with a null value) and publish the change. A
  never-observed reference (still `BadWaitingForInitialData`) and an already-Bad one are left alone.
  The event does **not** fire for a failed *initial* connect or during dispose — neither is an outage.
 - **Every (re)subscribe pushes the cached snapshots.** `SubscribeAsync` republishes each observed