CLI commands (`memory-pro`) output noisy plugin registration logs to stderr

[buzhihuowu2019]

Every openclaw memory-pro CLI command (stats, list, search, etc.) outputs ~11 lines of repeated plugin registration logs to stderr before the actual command output:

[plugins] memory-lancedb-pro: smart extraction enabled (LLM model: GLM-4.7, noise bank: ON)
[plugins] memory-lancedb-pro@1.1.0-beta.9: plugin registered (db: ~/.openclaw/memory/lancedb-pro, model: embedding-3, smartExtraction: ON)
[plugins] memory-lancedb-pro: diagnostic build tag loaded (memory-lancedb-pro-diag-20260308-0058)
[plugins] session-strategy: using none (plugin memory-reflection hooks disabled)
... (repeated ~11 times for a single command)

This makes CLI output very hard to read. This is a CLI usability issue distinct from the gateway runtime registration loop (#351).

Expected behavior:

Plugin registration logs should:

1. Only appear once (not repeated per CLI invocation)
2. Go to the gateway log file, not stderr when running CLI commands
3. Or be suppressed entirely in CLI mode with a --quiet flag

Steps to reproduce:

1. Install memory-lancedb-pro@1.1.0-beta.9 via npm
2. Enable smartExtraction in config (GLM-4.7 LLM, embedding-3)
3. Run any CLI command, e.g.: openclaw memory-pro stats
4. Observe ~11 lines of plugin registration logs printed to stderr before the actual stats output

Environment:

• Plugin: memory-lancedb-pro@1.1.0-beta.9 (installed via npm)
• OpenClaw: 2026.3.24
• Platform: macOS ARM64
• Config: smartExtraction enabled, GLM-4.7 LLM, embedding-3 via Zhipu API
• Embedding Provider: Other (Zhipu API)

[AliceLJY]

Thanks for reporting this, @buzhihuowu2019. You're right that plugin registration logs flooding stderr on every CLI command is a usability problem. The CLI path should either suppress these logs or route them to the log file instead of stderr. A --quiet flag would also be a good addition. This is a reasonable fix if you'd like to submit a PR — the key change would be detecting CLI mode in the registration path and adjusting log output accordingly.