Replace EverMemOS with EverOS backend

plugins/memory-gateway-agent/README.md

@@ -117,7 +117,7 @@ Verified boundaries:
 
 The plugin rejects memory writes containing passwords, API keys, bearer tokens, cookies, private keys, SSH keys, one-time verification codes, large logs, full raw transcripts, and chain-of-thought.
 
-The plugin writes summarized candidate episodes. It does not store full raw conversations. Long-term memory should normally be produced by `memory_commit_session`, allowing Memory Gateway and EverMemOS to deduplicate, detect conflicts, and route review drafts.
+The plugin writes summarized candidate episodes. It does not store full raw conversations. Long-term memory should normally be produced by `memory_commit_session`, allowing Memory Gateway and EverOS to deduplicate, detect conflicts, and route review drafts.
 
 Direct long-term `memory_upsert` is high risk and is not called automatically. If a user asks to forget or delete a memory, the agent should call `memory_feedback` or a delete-capable tool instead of silently keeping the memory.
 

plugins/memory-gateway-agent/hermes.plugin.yaml

@@ -25,7 +25,7 @@ tools:
   memory_append_episode:
     description: Append a safe summarized candidate episode.
   memory_commit_session:
-    description: Ask Gateway/EverMemOS to consolidate session episodes.
+    description: Ask Gateway/EverOS to consolidate session episodes.
   memory_upsert:
     description: Upsert a stable memory through Gateway.
   memory_feedback:

plugins/memory-gateway-agent/openclaw.plugin.yaml

@@ -22,5 +22,5 @@ hooks:
 safety:
   stores_full_raw_conversation: false
   rejects_secrets: true
-  long_term_commit_via_evermemos: true
+  long_term_commit_via_everos: true
 

plugins/memory-gateway-agent/policies/memory_policy.md

@@ -16,7 +16,7 @@ During a task:
 
 At task or session completion:
 
-- Use `memory_commit_session` to let Memory Gateway and EverMemOS decide what can be promoted.
+- Use `memory_commit_session` to let Memory Gateway and EverOS decide what can be promoted.
 - Do not promote all episodes directly to long-term memory.
 - Conflicting or high-value memories should enter review rather than overwrite existing memory.
 

plugins/memory-gateway-agent/policies/safety_filter.md

@@ -20,5 +20,5 @@ The plugin must reject memory writes that contain:
 
 The plugin stores summaries rather than raw messages. If a message is useful but contains sensitive detail, redact the sensitive detail before writing. If redaction would remove the meaning, reject the write.
 
-Long-term memory should normally be created by session commit and EverMemOS consolidation, not by direct upsert.
+Long-term memory should normally be created by session commit and EverOS consolidation, not by direct upsert.
 

plugins/memory-gateway-agent/schemas.py

@@ -42,7 +42,7 @@ MEMORY_APPEND_EPISODE = {
 
 MEMORY_COMMIT_SESSION = {
     "name": "memory_commit_session",
-    "description": "Commit a session through Memory Gateway and EverMemOS. Promotes only what consolidation accepts.",
+    "description": "Commit a session through Memory Gateway and EverOS. Promotes only what consolidation accepts.",
     "parameters": {
         "type": "object",
         "properties": {