Add memory-dream skill + additive cross-machine memory sync

memory-dream: read-only memory lint/consolidation analyzer (index, backlinks,
stale refs, dup clusters, profile drift); additive-only --apply-safe, all
merges/deletes are proposals. sync-memory.sh: additive repo<->harness-profile
union (no delete/overwrite, conflicts surfaced), wired to a SessionStart hook.
Migrates the useful profile-only memories into the synced repo store.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

.claude/memory/feedback_no_toml_config_endpoints.md

@@ -0,0 +1,16 @@
+---
+name: No TOML/config file approach for endpoints
+description: User explicitly prohibits TOML or config-file-based endpoint configuration — this will never be approved
+type: feedback
+originSessionId: 50d853e9-1d2f-4094-9b7b-f509fb95891f
+---
+Never propose storing endpoint URLs, server addresses, API targets, or connection parameters in TOML files, config files, INI files, or any file-based config approach when it comes to deployed agents or endpoints.
+
+**Why:** User stated directly: "I cannot stand the toml/config file approach to anything when it comes to endpoints" and "that approach will never be approved by me/the user."
+
+**How to apply:** When designing agent deployment, enrollment, or configuration:
+- Embed endpoint/server data directly in the binary (compile-time constants, build flags, or baked into the installer)
+- Use registry keys (Windows) for anything that must be configurable post-install
+- Use MSI properties for install-time configuration
+- Never write agent.toml, config.toml, settings.ini, or equivalent files containing server URLs or connection endpoints
+- This applies to GuruRMM agent and any future agent/endpoint projects