diff --git a/session-logs/2026-05-31-session.md b/session-logs/2026-05-31-session.md
index e26183b..d0afbba 100644
--- a/session-logs/2026-05-31-session.md
+++ b/session-logs/2026-05-31-session.md
@@ -146,3 +146,53 @@ Routed the still-pending dashboard build/deploy to Mike (coord message to GURU-5
 - PR #29: `azcomputerguru/gururmm` — merge commit 5e391ca, main tip 529b0b2 (CI version-bump).
 - Root commits: b1a5bc9 -> 959b3a1 (onboarding-diag), 9d21c23 (submodule bump).
 - Coord todos: ab091bae (notes-clear, howard), 929ce451 (deploy, mike). Coord message: 9b247556 -> GURU-5070/claude-main.
+
+---
+
+## Update: 19:48 MST — Deployed PR #29 dashboard to production via RMM agent
+
+### User
+- **User:** Howard Enos (howard)
+- **Machine:** Howard-Home
+- **Role:** tech
+
+### Session Summary
+Deployed the merged PR #29 dashboard changes to production at rmm.azcomputerguru.com. Mike (GURU-5070) clarified two things over coord: (1) the deploy is not pinned to his machine — build-server.sh runs on the gururmm server (.30) itself; (2) build-server.sh builds only the Rust SERVER, while PR #29 is dashboard/frontend, which ships as static files under /var/www/gururmm/dashboard/. A server rebuild alone would not make the dashboard changes live, which is why it remained v0.2.32 after the 529b0b2 merge.
+
+Howard-Home has no SSH key for guru@172.16.3.30 (only the vaulted password; no sshpass/plink for non-interactive password auth), and the vault has no SSH key for .30 (the OpenClaw fleet key is for Tailscale 100.x hosts only). Per Mike's "get it from the vault, OR add one via RMM," took the RMM path: the GuruRMM local agent runs on .30 as root, so the deploy was dispatched through it directly — no SSH needed.
+
+Recon via the agent showed the server repo clone (/home/guru/gururmm) was already at merged main 529b0b2 (the push-to-main webhook had reset it), node v20.20.0 / npm 10.8.2 available, and /var/www root-writable. Deploy was therefore just build + publish: `sudo -u guru npm run build` then `rsync -av --delete dist/ /var/www/gururmm/dashboard/`. build-server.sh was deliberately skipped — PR #29 has no server changes, so rebuilding/restarting the prod server was unnecessary risk.
+
+### Key Decisions
+- Deployed via the on-box RMM agent rather than SSH: no key on Howard-Home, agent runs as root on .30, cleanest path and matches Mike's "via RMM" guidance.
+- Skipped build-server.sh: PR #29 is dashboard-only; the server binary was unchanged, so a prod server bounce had no benefit.
+- No git sync needed: agent recon confirmed the repo clone was already at 529b0b2 (webhook-managed via git reset --hard origin/main).
+- Confirmed external curl of rmm.azcomputerguru.com returns empty (Cloudflare non-browser block) — relied on agent-side on-disk verification (live index.html asset == freshly built asset) instead.
+
+### Problems Encountered
+- Initial coord message to Mike wrongly stated build-server.sh deploys the dashboard; Mike corrected it. Re-sent an accurate resolution message.
+- No SSH access from Howard-Home to .30; resolved by running the deploy through the RMM agent instead of SSH.
+
+### Configuration Changes
+- Production deploy on .30: rebuilt dashboard (dist/) and rsync --delete to /var/www/gururmm/dashboard/. Live bundle index-CUrUAhv_.js (was index-Di8C-nbq.js). No repo or server changes.
+
+### Credentials & Secrets
+- guru@172.16.3.30 SSH/sudo password: vault `infrastructure/gururmm-server.sops.yaml` field `credentials.password` (SSH and sudo are the same). No SSH key exists for .30 in the vault.
+- RMM API admin creds: vault `infrastructure/gururmm-server.sops.yaml` `credentials.gururmm-api.admin-email` / `admin-password`. API base http://172.16.3.30:3001, JWT 24h.
+
+### Infrastructure & Servers
+- GuruRMM local agent on .30: hostname `gururmm`, os linux, agent id `5e5a7ebc-95ea-40c8-b965-6ec15d63e157`, runs as root, client "AZ Computer Guru".
+- Dashboard served by nginx from /var/www/gururmm/dashboard/ on .30; deployed v0.2.34.
+
+### Commands & Outputs
+- Recon cmd 9bdc02b9 (exit 0): agent_user=root, can_sudo_guru=yes, node v20.20.0, npm 10.8.2, repo_HEAD=529b0b2, origin_main=529b0b2, live_asset=index-Di8C-nbq.js.
+- Deploy cmd c49adad8 (exit 0): BUILD_OK, built_asset=index-CUrUAhv_.js, rsync sent ~1.38 MB, live_asset=index-CUrUAhv_.js, DASHBOARD_DEPLOYED_OK.
+
+### Pending / Incomplete Tasks
+- Follow-up todo ab091bae (howard): allow clearing Site notes (server COALESCE blocks empty).
+- Unblocked next tier (todo 15a5440f): BUG-009/010 isError, BUG-011 remove `any`, BUG-008 metrics internal_err, BUG-015 agent in Programs & Features.
+
+### Reference Information
+- Coord: component gururmm/dashboard -> deployed v0.2.34; lock 7ec5ac68 released; todo 929ce451 (deploy) done; messages to GURU-5070/claude-main.
+- #dev-alerts: dispatch + completion alerts posted (cmd c49adad8).
+- Procedure ref: wiki/systems/gururmm-build.md:122-127 (server + dashboard deploy steps).