docs(deployment): correct the QA leader-resolution note after scadaproj#43

Claude-Session: https://claude.ai/code/session_01GT67AEHd2Acv1YPwGfXEoV
2026-11-09 14:48:49 -05:00
parent 414050935e
commit 90b691af84
1 changed files with 5 additions and 0 deletions
@@ -435,6 +435,11 @@ Three things worth carrying forward:
   false on the co-located VD03 box, where the workaround is to point every `BaseUrl` at `127.0.0.1`
   so resolution never matches and each chip falls back to the raw Akka address. On QA the leader
   chips resolve to real names (`node-a (vq03)`), so that workaround is **not** wanted here.
+   **Correction (2026-11-09, scadaproj#43):** before that fix the host match ran across the whole
+   application, so on QA a group that shares hosts with another (the ScadaBridge site group vs central)
+   could show the other group's leader (`central-a`). `LeaderResolver` now matches only within the
+   group's own members; an unmatched leader shows the raw Akka address. Two members of one group on the
+   same host still can't be told apart.

 ---