diff --git a/session-logs/2026-05-24-GURU-KALI-session.md b/session-logs/2026-05-24-GURU-KALI-session.md
index 72ae24b..db37dab 100644
--- a/session-logs/2026-05-24-GURU-KALI-session.md
+++ b/session-logs/2026-05-24-GURU-KALI-session.md
@@ -119,3 +119,19 @@ sed -i '228d;451d;534d' session-logs/2026-05-24-session.md   # removed <<<<<<< =
 - Agent ids: GURU-KALI `a73ba38e-cd02-4331-b8bf-474cd899ec22`, Saturn `8cd0440f-a65c-4ed2-9fa8-9c6de83492a4`, RECEPTIONIST-PC `9c91d324-1073-449c-8cc0-45c5bccfc218`. Deleted SL-SERVER `2585f6d5-3887-412e-a586-1dec030f0a40`.
 - ClaudeTools commits: a3c7064 (garbled cleanup + sync.sh guard), 6d065cf (backslash hook + CLAUDE.md note).
 - Issues/PRs: https://git.azcomputerguru.com/azcomputerguru/gururmm/issues/{15..19}, /pulls/{13,14,21}.
+
+---
+
+## Update: 12:33 MST — fleet converged 0.6.38; laggards noted in coord
+
+The re-triggered build published 0.6.38 and the fleet converged to 37/39 online on
+0.6.38 within ~10 min (1 -> 32 -> 36 -> 37). Two laggards remain one version back on
+0.6.37 (flaky WebSockets that miss the auto-update dispatch window; mechanism works,
+force-update lands when WS is up):
+- BB-SERVER (BirthBiologic) id 6c02baa7-0f1c-4990-b466-c9ab9eaefd3b
+- RECEPTIONIST-PC (Cascades of Tucson) id 9c91d324-1073-449c-8cc0-45c5bccfc218
+
+Noted for future rechecks in the coord messenger (to=mike, project=gururmm, msg id
+a254202a-aa33-4736-ba9c-cd5678dbef58): recheck their versions; if still behind latest,
+force-update via POST /api/agents/{id}/update; durable fix = investigate the client-site
+firewall/NAT resetting the long-lived WebSocket. All watchers finished; none running.