neutralize upstream service branding

skill/memory-gateway-agent/SKILL.md

@@ -23,7 +23,7 @@ Do not write a real `user_key` into source files, prompts, logs, or committed do
 
 ## Workflow
 
-1. Run `$CLI health` when connectivity or EverOS availability is uncertain.
+1. Run `$CLI health` when connectivity or upstream memory service availability is uncertain.
 2. Use an existing `user_id` and `user_key`. Run `create-user` only when the user explicitly needs a new Gateway identity.
 3. Choose the operation:
    - Upload durable user files with `upload-resource`.
@@ -58,7 +58,7 @@ Read [references/api.md](references/api.md) when choosing scopes, constructing m
 
 - Do not expose internal file paths. Return the Gateway's `resource://{user_id}/{resource_id}` URI to users.
 - Do not claim ingestion succeeded unless the upload status is `extracted` or flush reports success.
-- Treat `health.status = degraded` as Gateway available but EverOS unavailable.
-- Resource deletion is soft deletion in Gateway search scope and removes the Gateway upload copy; it does not delete EverOS internal indexes.
+- Treat `health.status = degraded` as Gateway available but upstream memory service unavailable.
+- Resource deletion is soft deletion in Gateway search scope and removes the Gateway upload copy; it does not delete upstream memory service internal indexes.
 - Memory override and deletion require an owned `resource:{user_id}:{resource_id}` or `memory_edit:{user_id}` session.
 - Ask for confirmation before destructive deletion unless the user's current request explicitly instructs deletion.

skill/memory-gateway-agent/references/api.md

@@ -46,7 +46,7 @@ CLI="python skill/memory-gateway-agent/scripts/memory_gateway.py"
 $CLI health
 ```
 
-No credentials required. HTTP 200 may contain `"status": "degraded"` when EverOS is unavailable.
+No credentials required. HTTP 200 may contain `"status": "degraded"` when upstream memory service is unavailable.
 
 ### Create User
 
@@ -77,7 +77,7 @@ Requires credentials. Supported resources depend on the server MIME allowlist. S
 }
 ```
 
-`failed` means the record exists but EverOS ingestion failed. Identical active content for the same user/app/project may return the existing resource.
+`failed` means the record exists but upstream memory service ingestion failed. Identical active content for the same user/app/project may return the existing resource.
 
 ### List, Get, and Delete Resources
 
@@ -108,7 +108,7 @@ $CLI search "query" --scope current_chat --scope resources \
 
 When no scope is provided, the CLI searches `resources` only unless a conversation ID is supplied; with a conversation ID it searches `current_chat` and `resources`. Explicit `current_chat` scope requires `--conversation-id`.
 
-Each result includes normalized `id`, `session_id`, `text`, `source_scope`, and optional resource metadata. The `raw` field preserves the EverOS response.
+Each result includes normalized `id`, `session_id`, `text`, `source_scope`, and optional resource metadata. The `raw` field preserves the upstream memory service response.
 
 ### Add and Flush Memory
 
@@ -150,7 +150,7 @@ $CLI delete-memory mem_abc \
   --reason "User requested deletion"
 ```
 
-These operations write Gateway overrides or tombstones. They do not modify EverOS files directly. The server rejects sessions not owned by the authenticated user.
+These operations write Gateway overrides or tombstones. They do not modify upstream memory service files directly. The server rejects sessions not owned by the authenticated user.
 
 ## Message Format
 
@@ -161,7 +161,7 @@ Each message requires:
 | `sender_id` | string | Usually the current user ID |
 | `role` | string | `user`, `assistant`, or `tool` |
 | `timestamp` | integer | Unix milliseconds, greater than zero |
-| `content` | string or array | Text or EverOS content items |
+| `content` | string or array | Text or upstream memory service content items |
 
 Common content items:
 
@@ -187,7 +187,7 @@ Common content items:
 }
 ```
 
-Prefer base64 for local binary files. A `file://` URI is only usable when EverOS can access the same filesystem path.
+Prefer base64 for local binary files. A `file://` URI is only usable when upstream memory service can access the same filesystem path.
 
 ## Search Scopes