fix: suppress plugin registration logs in CLI mode (#380)

[buzhihuowu2019]

Summary

Fixes #380

Problem

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

Solution

Detect CLI mode via OPENCLAW_CLI environment variable (set by OpenClaw when running CLI subcommands). In CLI mode, downgrade registration and lifecycle logs from info to debug level.

Changes

• Added isCliMode() helper that checks process.env.OPENCLAW_CLI === "1"
• Downgraded 5 registration/lifecycle log lines to debug in CLI mode:
  • smart extraction enabled
  • plugin registered (db, model, smartExtraction)
  • diagnostic build tag loaded
  • session-strategy: using none
  • session-memory: typed before_reset hook registered

Behavior

Context	Before	After
Gateway runtime	info (visible)	info (unchanged)
CLI commands	info (noisy ~11 lines)	debug (suppressed)

Testing

Tested with openclaw memory-pro stats — registration logs no longer appear in stderr. Gateway startup logs remain unchanged.

[buzhihuowu2019]

The cli-smoke failure in reflection-bypass-hook.test.mjs is a pre-existing flaky test (4 subtests expecting stdout output that is empty). This PR only changes log levels from info to debug and does not affect any stdout/stderr content paths tested there. The same test likely fails on the upstream master branch as well.

[AliceLJY]

Code LGTM — clean, minimal change, no side effects.

The 4 test failures in reflection-bypass-hook.test.mjs are pre-existing (fixed on master by 8bbca98 but not yet in your branch). Please rebase onto latest master to pick up the seed date fix, then tests should pass.

@rwmjhb ready for merge after rebase.

[buzhihuowu2019]

Rebased onto latest master (picked up the seed date fix from 8bbca98). Ready for merge.

[rwmjhb]

Nice improvement overall. One thing I noticed: CLI-mode log suppression still seems incomplete.

On the current PR head, OPENCLAW_CLI=1 correctly downgrades the main startup logs, but self-improvement and memory- reflection registration-summary logs still go through api.logger.info(...) on their enabled paths. That means users with those configs can still get stderr noise before command output.

If the intended scope of #380 is “suppress registration/lifecycle noise in CLI mode,” I think those remaining registration logs should be gated the same way as the other startup logs.