docs(index): Auth 0.2.1 adopted by all four apps; FallbackServers live-gated on HG + ScadaBridge rig

ldap_setup.md

@@ -242,9 +242,13 @@ Three gaps to settle before this is a design rather than a sketch:
 
 **Found and fixed 2026-08-12.** All four Auth packages are **published to the Gitea feed at
 `0.2.1`** and restore-verified from a scratch consumer (the assembly restored *from the
-feed* carries the fix; `0.2.0` does not). **The four apps still pin `0.1.5`, so nothing is
-fixed for them until each bumps** — a pin bump is the remaining step, and until it happens
-every app still fails a domain-root search with `ServiceAccountBindFailed`.
+feed* carries the fix; `0.2.0` does not). **ADOPTED by all four apps 2026-08-13** —
+OtOpcUa `master @ 08e33fc7`, ScadaBridge `main @ d28824d9`, MxAccessGateway
+`main @ 1cb14d2`, HistorianGateway `e42ff31` (on its `dashboard-ui-sweep-theme-0.4.1`
+branch) — each built + tested green; commits are local, not yet pushed. `FallbackServers`
+failover was live-gated the same day against the local redundant GLAuth pair
+([`infra/glauth-redundant/`](infra/glauth-redundant/)): HistorianGateway dashboard login
+drill PASS (sticky failover both directions).
 
 Authenticating with `SearchBase = DC=nam,DC=zimmer,DC=com` fails on **both DCs** with
 `ServiceAccountBindFailed` in ~546 ms. It is not connectivity, not the service account,