--- name: backup-memory-topology description: "How the RobCo backup discovers memory, the multi-store topology, and the Roaming-junction gotcha" metadata: node_type: memory type: project originSessionId: 8665b012-05e2-4f82-8a4f-d996c5f6026d modified: 2026-07-20T18:12:07.010Z --- The `_robco-local-backup` repo's `sync.ps1` backs up EVERY memory store on this machine, in two ecosystems, each into its own `memory/<label>/` subfolder — never guessing which is canonical. **Two ecosystems:** - CLI project memory: `~\.claude\projects\<slug>\memory` → `memory/project-<slug>/`. A prior `sync.ps1` MISSED this entire ecosystem — the "reports success while protecting nothing" failure that is the reason discovery is enumerated rather than assumed. - Desktop local-agent-mode: `<base>\<guidA>\<guidB>\agent\memory` → `memory/localmode-<guid>/`. *Correction 2026-07-20: per-store file counts were removed from this file. They were wrong, and they are computed every run into `memory/_CAPTURE_MANIFEST.txt` — read that.* **Gotcha (why discovery is not a single path):** `~\AppData\Roaming\Claude\...` is a per-app virtualized junction that some shells resolve and pwsh does NOT (`Test-Path` returns False). The REAL physical base is `~\AppData\Local\Packages\Claude*\LocalCache\Roaming\Claude\local-agent-mode-sessions` — discovered via a `Claude*` glob so no packaged-app hash is hardcoded. **Self-check:** each run prints, and writes `memory/_CAPTURE_MANIFEST.txt` with, which stores were found and how many files each yielded, so a future wrong or empty capture is visible instead of hidden. Empty stores are skipped-and-reported; zero usable stores = loud non-zero failure, nothing pushed. Repo `zerckzzyHD/robco-uos-local-archive` is confirmed PRIVATE. A credential scan was run on 2026-07-18 covering API keys, tokens, private keys, `.env` files and service-account JSON, and found none at that time; the app is bring-your-own Gemini key. **Treat that as a dated scan result, not a standing guarantee** — a later audit did find a debug token in a memory store, so re-scan before treating any part of this archive as safe to publish.