azcomputerguru/claudetools
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

sync: auto-sync from GURU-5070 at 2026-06-11 08:00:04

Browse Source 
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-11 08:00:04
This commit is contained in:
Mike Swanson
2026-06-11 08:00:19 -07:00
parent 23299a661e
commit cfc065b097
14 changed files with 186 additions and 483 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.claude/memory/MEMORY.md
View File

@@ -123,3 +123,4 @@
- [Syncro preview mandatory](feedback_syncro_preview_mandatory.md) — preview+confirm every Syncro write, including internal notes
- [Refresh session history first](feedback_refresh_session_history_first.md) — read prior incident logs before acting; do not re-remediate already-handled accounts
- [Autonomy scope](feedback_autonomy_scope.md) — confirm only for client-affecting actions; internal docs/wiki/ClaudeTools = act autonomously
- [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.

33
.claude/memory/feedback_client_slug_fragmentation.md Normal file
View File

@@ -0,0 +1,33 @@
---
name: Check for client-slug fragmentation before concluding "no records exist"
description: A single client can be recorded under several slug variants (e.g. wolkin / wolkin-law / rswolkin / robert-wolkin). Search broadly across variants before saying nothing is documented, and consolidate to one canonical slug when you find the spread.
type: feedback
---
When a client/machine is named and you can't find its records (vault, wiki, session logs), do
NOT conclude "nothing was captured" from a single-slug search. The same client is often
fragmented across multiple slugs and the RMM/Syncro display name (Last, First) form.
**Why:** Mike, 2026-06-11. On the Wolkin printer issue I searched `wolkin` in the vault, found
nothing, and asked Mike for a password we already had — because the two-day build was split
across FOUR slugs: `clients/wolkin/`, `clients/rswolkin/`, `clients/wolkin-law/`, and wiki
`wolkin.md` / `wolkin-law.md` / `robert-wolkin.md` (RMM client `Wolkin, Robert`, tenant
`rswolkin.com`). The credential and the *exact same* error-67 diagnosis were sitting in a
session log under a different slug. Mike: "an absolute failure of the session logs and wiki
system." It wasn't lost — it was unfindable because of slug drift, and pending items from the
prior log ("migrate creds to vault", "consolidate the slugs") were never actioned.
**How to apply:**
- Before concluding a client has no records, grep broadly: the company name, the owner's name,
initials, the hostname, and `Last, First` — across `clients/`, `wiki/`, `session-logs/`, and
the vault. e.g. `grep -ril "wolkin|rsw|robert" clients/ wiki/ session-logs/`.
- If you find the same client under >1 slug, **consolidate**: pick one canonical slug, move the
scattered logs/baselines into `clients/<canonical>/`, merge the wiki articles into one and
leave pointer stubs at the others, and add `aliases:` to the canonical article's frontmatter
so future recall finds it.
- Onboard each client under ONE slug from the start. The GuruRMM client name, the Syncro
customer, the vault dir, the wiki slug, and the `clients/<slug>/` dir should all match.
- Always action a prior log's "Pending" items (vault these creds, consolidate these slugs) —
unactioned pending items become the next session's wall.
- Wolkin canonical = slug `wolkin`; see [[wolkin]] wiki for the error-67 ZeroTier/SMB printer
wall (needs interactive fix, not scripted) and the `Get-NetAdapterBinding` bracket-wildcard tip.