docs: purge the retired workstation from auto-learned memory and the backup snapshot

Finishes the purge. These two surfaces were left out of the earlier commit
because the memory store is auto-generated, but both are read back into every
future session, so the name was still reaching the agent.

58 sites across 16 files: hostname, both LAN addresses, the SSID. Special-cased
the compound names a blind token swap breaks ('dank@the workstation/dankclaw',
'on the workstation/Dankclaw/Dankserver') and reworded the four that came out
ungrammatical. Facts kept: the hardware inventory of the box, the noctalia
architecture history, and today's own purge lessons all survive intact — only
the identifiers are gone.

Non-memory: the tracked .pre-pull-backup snapshot of a managed skill, whose
live counterpart was already clean.
This commit is contained in:
Frank committed 2026-09-28 16:57:00 -07:00
1 parent 689228e60d
commit 12c5e885f1
43 files changed
+799 -154

No files matched your search

@@ -1,4 +1,4 @@
thread_id: 01a059ae-72f3-76d4-8e09-735f8f2e0a5d
updated_at: 1788216058
Configured passwordless SSH among dankclaw/dankware, FrankBook-Pro, dankserver, and Hermes containers; installed and verified Podman stack on FrankBook-Pro macOS host.
Configured passwordless SSH among dankclaw, the workstation, FrankBook-Pro, dankserver, and Hermes containers; installed and verified Podman stack on FrankBook-Pro macOS host.
@@ -1,4 +1,4 @@
thread_id: 01a063a7-4c37-7765-8f58-21f7c860aed7
updated_at: 1788403307
serverAppConfigs service-status investigation from Dankware: repo manages services on Dankserver (192.168.0.235) and Dankclaw (192.168.0.143) via mostly rootless Podman Quadlet user units; both hosts are reachable by passwordless SSH. Hermes WebUI troubleshooting on Dankclaw found hermes/hermes-webui/hermes-dashboard active, but signal-cli-daemon inactive/disabled, which is likely why Hermes/WebUI cannot reach Signal transport.
serverAppConfigs service-status investigation from the workstation: repo manages services on Dankserver (192.168.0.235) and Dankclaw (192.168.0.143) via mostly rootless Podman Quadlet user units; both hosts are reachable by passwordless SSH. Hermes WebUI troubleshooting on Dankclaw found hermes/hermes-webui/hermes-dashboard active, but signal-cli-daemon inactive/disabled, which is likely why Hermes/WebUI cannot reach Signal transport.