Bug: memory-tencentdb plugin config keys (recall/extraction/embedding) rejected by gateway schema validation

Description

When configuring the memory-tencentdb plugin under plugins.entries, the gateway rejects recall, extraction, and embedding config keys as "Unrecognized keys", even though these are officially documented in the plugin's openclaw.plugin.json configSchema.

Steps to Reproduce

1. In openclaw.json, configure memory-tencentdb with documented config keys:

{
  "plugins": {
    "entries": {
      "memory-tencentdb": {
        "enabled": true,
        "hooks": {
          "allowConversationAccess": true
        },
        "recall": {
          "enabled": true,
          "maxResults": 3,
          "scoreThreshold": 0.5,
          "strategy": "hybrid"
        },
        "extraction": {
          "enabled": true,
          "maxMemoriesPerSession": 8,
          "enableDedup": true
        },
        "embedding": {
          "enabled": true,
          "provider": "dashscope",
          "baseUrl": "https://dashscope.aliyuncs.com/compatible-mode/v1",
          "apiKey": "...",
          "model": "text-embedding-v3",
          "dimensions": 1024
        }
      }
    }
  }
}

1. Run openclaw gateway restart

2. Gateway fails with:

Config invalid
File: ~/.openclaw/openclaw.json
Problem:
  - plugins.entries.memory-tencentdb: Unrecognized keys: "recall", "extraction", "embedding"

Running openclaw doctor --fix strips these keys from the config.

Expected Behavior

Gateway should accept all keys defined in the plugin's openclaw.plugin.json configSchema.properties:

• capture
• extraction
• persona
• pipeline
• recall
• embedding
• tcvdb
• bm25
• report
• storeBackend

Since configSchema.additionalProperties is also set to true, any documented key should pass validation.

Workaround Found

Wrapping the plugin-specific config in a config sub-object works:

{
  "memory-tencentdb": {
    "enabled": true,
    "hooks": {
      "allowConversationAccess": true
    },
    "config": {
      "recall": { ... },
      "extraction": { ... },
      "embedding": { ... }
    }
  }
}

The plugin's parseConfig function at runtime reads from the raw entry level (not from config), so the config wrapper means the settings are silently ignored by the plugin unless the gateway merges config into the entry before passing it through.

Environment

• OpenClaw version: 2026.5.7 (eeef486)
• Installed via: pnpm global
• OS: Linux (Ubuntu 22.04)
• Plugin: @tencentdb-agent-memory/memory-tencentdb (latest)

Impact

Without fix, users cannot:

1. Configure recall parameters (maxResults, scoreThreshold, strategy, timeout)
2. Enable external embedding providers for semantic search
3. Tune extraction dedup or session limits

All these features require using the config wrapper workaround, which may or may not actually pass config to the plugin depending on gateway behavior.