sync: auto-sync from HOWARD-HOME at 2026-07-15 13:59:09

Author: Howard Enos
Machine: HOWARD-HOME
Timestamp: 2026-07-15 13:59:09

.claude/memory/MEMORY.md

@@ -231,3 +231,4 @@
 - [ask-forum — human-in-the-loop via #ct-forum](../skills/ask-forum/SKILL.md) — ask a teammate a question in the private ct-forum Discord forum, get their human answer back in-session; forum-only, any human can answer, run the --wait as a proper background task
 - [Claude Code Bun crash -> pin 2.1.110](reference_claude_code_bun_crash_pin.md) - v2.1.114+ segfaults on Win11 at new-session start; npm pin 2.1.110 + DISABLE_AUTOUPDATER=1; unpin on #55219 fix
 - [GuruRMM build-server SSH key](reference_gururmm_build_server_ssh.md) — guru@172.16.3.30 key is ~/.ssh/gururmm-physical (not id_*); password fallback vault infrastructure/gururmm-server
+- [LAB-SVR retired](feedback_labsvr_retired.md) — Len's Auto LAB-SVR replaced by LAB-SERVER; never chase LAB-SVR

.claude/memory/feedback_labsvr_retired.md

@@ -0,0 +1,16 @@
+---
+name: LAB-SVR is retired — replaced by LAB-SERVER
+description: Len's Auto machine LAB-SVR was decommissioned and replaced by LAB-SERVER; never chase LAB-SVR again
+type: feedback
+---
+
+Len's Auto Brokerage's **LAB-SVR was replaced by LAB-SERVER**. Do NOT investigate, probe,
+queue commands on, or report LAB-SVR as a stale/offline machine — it is retired.
+
+**Why:** Howard has corrected this repeatedly ("for the last time... STOP LOOKING FOR THAT
+MACHINE", 2026-07-15). LAB-SVR still appears in stale data (GuruRMM offline agent record,
+old MSP360 plan rows), which keeps baiting audits into flagging it.
+
+**How to apply:** In any backup/RMM/fleet audit, treat LAB-SVR rows as retired-machine
+residue. Check LAB-SERVER for Len's Auto server health instead. Cleanup of the stale
+LAB-SVR records (MSP360 plans/user side, RMM agent record) is the actual actionable item.