sync: auto-sync from GURU-5070 at 2026-06-11 11:10:31

Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-11 11:10:31

.claude/memory/MEMORY.md

@@ -129,3 +129,4 @@
 - [Check for client-slug fragmentation](feedback_client_slug_fragmentation.md) — Before concluding a client has no records, grep broadly (company/owner/initials/hostname/"Last, First") across clients/, wiki/, session-logs/, vault — one client gets split across slug variants (Wolkin was 4: wolkin/wolkin-law/rswolkin/robert-wolkin). Consolidate to one canonical slug; action prior logs' Pending items.
 - [RMM user_session = false SMB failures](feedback_rmm_user_session_smb_false_negative.md) — GuruRMM net use/net view/Add-Printer to a remote \HOST fail with error 67 / RPC 1702 (even with valid creds) because user_session is a WTS-impersonated non-interactive token that can't do authenticated SMB. The share/printer may work fine interactively. Treat RMM SMB results as "can't tell"; verify via ScreenConnect.
 - [Broken [[backlinks]] = write-me-later markers](feedback_broken_backlinks_are_writeme_markers.md) — A [[name]] with no matching file is an intentional "worth writing" marker, not breakage. Flesh the missing memory out from session history/logs and index it; never strip the link to silence the warning. memory-dream reports these as INFO candidates, not errors.
+- [gururmm session-logs are in a submodule](gururmm-session-logs-submodule-save.md) — save via the new box (.30); GURU-5070 cant push to gururmm Gitea

.claude/memory/gururmm-session-logs-submodule-save.md

@@ -0,0 +1,27 @@
+---
+name: gururmm-session-logs-submodule-save
+description: Saving gururmm session-logs/docs requires committing inside the guru-rmm git submodule and pushing from the new box (.30) — sync.sh doesn't commit submodule contents and GURU-5070 can't push to gururmm Gitea
+metadata:
+  type: reference
+---
+
+`projects/msp-tools/guru-rmm` is a **git submodule** (gururmm repo,
+`git@172.16.3.20:azcomputerguru/gururmm.git`, branch main). So gururmm session logs
+(`projects/msp-tools/guru-rmm/session-logs/...`) and docs (`docs/HOST_MIGRATION_RUNBOOK.md`,
+etc.) are tracked in the **submodule**, not the parent ClaudeTools repo.
+
+`/save` -> `sync.sh` commits/pushes the **parent** ClaudeTools repo only; it leaves submodule
+**gitlinks unstaged** (unless `--with-submodules`) and NEVER commits submodule *contents*. So a
+session log written under the submodule is left **uncommitted/untracked** by a normal `/save`.
+
+**GURU-5070 cannot push to gururmm Gitea** (`ssh -p 2222 git@172.16.3.20` -> Permission denied;
+its key isn't authorized there). The **new box (.30 / .47)** CAN push (its `~/.ssh/id_ed25519` is
+authorized as `gururmm-build-server`).
+
+**To persist gururmm session logs/docs from GURU-5070:** scp the file(s) to the new box's
+checkout `/home/guru/gururmm/...` (it's on main with push access), `git add` them explicitly
+(avoid the build-artifact changelog cruft), commit + `git push origin main` from the new box.
+Then on GURU-5070 advance the submodule (`git -C <sub> fetch origin && stash -u && reset --hard
+origin/main && stash drop`), `git add` the gitlink in the parent, commit, and `sync.sh`. The
+GURU-5070 submodule checkout tends to sit **detached at a stale commit** (it lags the build
+host's auto-bump commits) — fetch first. See [[gururmm-physical-server-storage]].