feat: Add self-hosted MemOS server support

[ChaoXu1997]

Summary

This PR adds support for self-hosted MemOS servers to the cloud plugin, enabling users to deploy their own MemOS API while still using this plugin.

Changes

1. Self-hosted Mode Detection (lib/memos-cloud-api.js)

• Auto-detect self-hosted mode when baseUrl is localhost or private IP (192.168.x.x, 10.x.x.x)
• Use different API endpoints for self-hosted vs cloud:
  • Cloud: /search/memory, /add/message
  • Self-hosted: /product/search, /product/add
• Skip API key validation for self-hosted mode

2. Plugin Kind Change (index.js, openclaw.plugin.json)

• Changed kind from "lifecycle" to "memory"
• This allows OpenClaw to recognize the plugin as a memory slot plugin
• Enables automatic memory write functionality via Gateway hooks

3. API Key Skip Logic

• Self-hosted MemOS servers don't require API key authentication
• Added conditional check: if (!cfg.apiKey && cfg.serverMode !== "self-hosted")

Configuration Example

{
  "memos-cloud-openclaw-plugin": {
    "enabled": true,
    "config": {
      "baseUrl": "http://localhost:8000",
      "userId": "openclaw-user",
      "agentId": "moss-server",
      "multiAgentMode": true,
      "recallEnabled": true,
      "addEnabled": true,
      "timeoutMs": 30000
    }
  }
}

Testing

• ✅ Self-hosted mode detection works correctly
• ✅ Memory search returns results from local MemOS server
• ✅ Memory add successfully stores to local server
• ✅ Plugin recognized as memory slot by OpenClaw Gateway

Related

• MemOS self-hosted API: https://github.com/MemTensor/MemOS
• Addresses issue where cloud plugin couldn't connect to self-hosted MemOS servers