Add Memory Gateway agent plugin

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

@@ -0,0 +1,34 @@
+# Memory Gateway Agent Policy
+
+Use Memory Gateway as a shared memory adapter. It is not a transcript store.
+
+At conversation start:
+
+- Search memory when previous context may matter.
+- Use `memory_search` with the current `user_id`, `agent_id`, `workspace_id`, and `session_id`.
+- Inject only compact relevant memory summaries into the working context.
+
+During a task:
+
+- Write only candidate episode summaries with `memory_append_episode`.
+- Save stable preferences, long-term project facts, architecture decisions, durable constraints, reusable workflows, and completed task conclusions.
+- Do not save complete raw conversations, chain-of-thought, large logs, one-time values, or secrets.
+
+At task or session completion:
+
+- Use `memory_commit_session` to let Memory Gateway and EverMemOS 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.
+
+When the user says to forget or reject memory:
+
+- Use `memory_feedback` with `incorrect`, `outdated`, or `not_useful`.
+- Use delete-capable tools only when the runtime exposes them and access control allows it.
+
+Default automation:
+
+- Auto search may be enabled.
+- Auto append episode may be enabled for safe summaries.
+- Auto commit is disabled by default.
+- Auto direct long-term upsert is disabled by default.
+

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

@@ -0,0 +1,24 @@
+# Memory Gateway Safety Filter
+
+The plugin must reject memory writes that contain:
+
+- passwords
+- API keys
+- tokens
+- secrets
+- bearer tokens
+- cookies
+- session IDs
+- private keys
+- SSH keys
+- one-time passwords or verification codes
+- large raw logs
+- full chat transcripts
+- chain-of-thought or hidden reasoning
+- unconfirmed sensitive personal attributes
+- low-value temporary chatter
+
+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.
+