diff --git a/projects/msp-tools/guru-rmm b/projects/msp-tools/guru-rmm
index 1ed5596..7ab38ca 160000
--- a/projects/msp-tools/guru-rmm
+++ b/projects/msp-tools/guru-rmm
@@ -1 +1 @@
-Subproject commit 1ed55964db77d3964b330370b4e68de6fce2c3d6
+Subproject commit 7ab38ca1f2a362bcc96d72b4af7d3f379cf3939e
diff --git a/session-logs/2026-05-24-wiki-layer.md b/session-logs/2026-05-24-wiki-layer.md
index 4fc7fc4..7cb22a9 100644
--- a/session-logs/2026-05-24-wiki-layer.md
+++ b/session-logs/2026-05-24-wiki-layer.md
@@ -111,3 +111,78 @@ None created or discovered this session.
 - Karpathy post: https://x.com/karpathy/status/2039805659525644595 (2026-04-02)
 - Cascades wiki article: `wiki/clients/cascades-tucson.md` (last_compiled: 2026-05-24)
 - GuruRMM wiki article: `wiki/projects/gururmm.md` (last_compiled: 2026-05-24)
+
+---
+
+## Update: ~23:45 PT — Wiki completion, verification pass, corrections
+
+### Session Summary
+
+Session resumed after context window reset. The 4 system wiki articles (gururmm-build, jupiter, pluto, uranus) had already been written to disk in the previous context portion. This continuation updated `wiki/index.md` to reflect all 4 as seeded and removed them from the compilation queue, then committed and pushed. `wiki/overview.md` was compiled directly from all 6 seeded articles plus CLAUDE.md — covering team, all clients, internal projects, full infrastructure table, tooling stack, key URLs, and cross-cutting open action items. Committed and pushed. The overview went last in the seed queue as designed, reading from other wiki articles rather than raw logs.
+
+A full verification pass was run against each seeded article with Mike confirming accuracy or providing corrections one by one. Cascades of Tucson required one correction: the Syncro blank-contact rule is global (not Cascades-specific), so the article wording and the associated memory file were updated accordingly. A coord message was sent to Howard (ACG-TECH03L/claude-main) asking him to review the Cascades article from his onsite perspective.
+
+GuruRMM required significant corrections. The BB-SERVER and RECEPTIONIST-PC laggard note was stale — both were already on 0.6.38. The enrolled client/site list in the wiki had only 4 entries; the live API returned 55 agents across 12 clients. The full list was pulled via authenticated API call and written into the article. Mike confirmed all 12 clients as legitimate, noting some are Residential vs Corporate but all should be treated as active. The Saturn agent concern was resolved — that agent no longer appears in the API. The actual laggards are 15 offline machines on older versions that will self-update on reconnect. All 4 system articles were verified accurate with no changes required.
+
+### Key Decisions
+
+- **Verify from live API before documenting fleet state** — the cached laggard note was wrong within the same day. Fleet data now pulled from `GET /api/agents` at verification time rather than trusted from session-log memory.
+- **Syncro contact rule is global** — Mike confirmed on 2026-05-24 that "do not set contact unless requested" applies to all customers. Updated memory file and Cascades wiki article to reflect this; the global rule was already in `feedback_syncro_blank_contact.md`, so `feedback_syncro_cascades_contact.md` was narrowed to the Meredith Kuhn incident detail only.
+- **Residential vs Corporate client distinction noted but not blocking** — Mike confirmed all 12 enrolled clients are legitimate; Residential/Corporate distinction captured in the client type column of the GuruRMM article for future reference.
+- **Saturn agent resolved** — no "Saturn" labeled agent appears in the current API response. Concern removed from wiki and no cleanup action needed.
+
+### Problems Encountered
+
+- **Coord message parse failure (3 attempts)** — `curl` with inline JSON containing an em dash in the subject field caused "error parsing body". Resolved by writing the JSON payload to `/tmp/coord_msg.json` and using `-d @/tmp/coord_msg.json`. Root cause: shell encoding of the em dash character in the single-quoted string.
+- **Agent version field mismatch** — initial API query used `version` field; actual field is `agent_version`. All versions showed as `?`. Fixed on second query after inspecting raw agent object structure.
+- **Push rejected (fetch first)** — a sync from another machine had pushed between commits. Resolved with `git pull --rebase && git push`.
+
+### Configuration Changes
+
+**Modified:**
+- `wiki/index.md` — Systems table updated (4 articles now seeded); overview row marked compiled; gururmm-build/jupiter/pluto/uranus and overview removed from compilation queue
+- `wiki/clients/cascades-tucson.md` — Syncro contact rule wording updated to reflect global scope
+- `wiki/projects/gururmm.md` — Fleet state corrected; enrolled client/site list expanded from 4 to 12 clients; Saturn agent concern removed; actual laggards documented
+- `wiki/overview.md` — Fleet count and client table updated to match corrected GuruRMM data
+- `.claude/memory/feedback_syncro_cascades_contact.md` — Narrowed to Meredith Kuhn incident detail; global rule pointer added
+- `.claude/memory/MEMORY.md` — Index entry for cascades contact file updated to match
+
+**Created:**
+- `wiki/systems/gururmm-build.md` — committed this session (written in previous context)
+- `wiki/systems/jupiter.md` — committed this session
+- `wiki/systems/pluto.md` — committed this session
+- `wiki/systems/uranus.md` — committed this session
+- `wiki/overview.md` — compiled and committed this session
+
+### Credentials & Secrets
+
+- GuruRMM API admin credentials accessed from vault (`infrastructure/gururmm-server.sops.yaml`) for live API verification. No new credentials created.
+
+### Infrastructure & Servers
+
+**Live GuruRMM fleet (verified 2026-05-24 ~23:30 PT):**
+- 55 agents total, 37 online, 40/55 on v0.6.38
+- 12 enrolled clients (see GuruRMM wiki article for full table)
+- Laggards: 15 offline agents on v0.6.1 through v0.6.29 — all will self-update on reconnect
+
+**Coord message sent:**
+- ID: `33d1576d-02d2-4940-8e97-7d8c5140e8c0`
+- To: `ACG-TECH03L/claude-main` (Howard)
+- Subject: Review Cascades wiki article — needs your onsite context
+
+### Pending / Incomplete Tasks
+
+- **Howard review of cascades-tucson.md** — coord message sent; awaiting his corrections
+- **NPM stale proxy** — `rmm-api.azcomputerguru.com → 172.16.3.20:3001` should be `.30:3001`. Fix in NPM admin at http://172.16.3.20:7818. Still unresolved.
+- **wiki/commands/wiki-compile.md** — skill not yet implemented (Phase 2)
+- **wiki/commands/wiki-lint.md** — skill not yet implemented (Phase 4)
+- **Dataforth UDM resubnet** — TODO; eliminates Neptune routing workaround via D2TESTNAS
+- **Wiki seed — neptune, birthbiologic, key-paul** — still in queue, lower priority
+- **Mikes-MacBook-Air.local** — GuruRMM agent on v0.6.1 (macOS), significantly behind fleet. Needs manual update or investigation.
+
+### Reference Information
+
+- Commits this session: `7daca57` (4 system articles), `cbbea8b` (overview), `3a188dc`→`e4d3c1f` (contact rule corrections, rebased), `2f99a01` (GuruRMM corrections)
+- Wiki root: `wiki/`
+- GuruRMM API agents endpoint: `GET http://172.16.3.30:3001/api/agents` (JWT required)
+- Coord message to Howard: ID `33d1576d-02d2-4940-8e97-7d8c5140e8c0`