fix(memos-local-openclaw-plugin): integrate stfix(memos-local): report memory status correctly and avoid CLI-spawned viewersatus runtime and gate viewer self-start

[LEVO-Hephaestus]

Summary

This PR fixes two integration issues in the MemOS local OpenClaw plugin:

1. Register an OpenClaw memory runtime adapter so host status probes can read plugin health correctly
2. Gate viewer service registration and self-start logic to real gateway processes only

Problem

The plugin could still read and write memory correctly, but openclaw status reported memory as unavailable.

At the same time, CLI processes such as openclaw status could accidentally trigger the plugin's viewer self-start fallback, which caused extra viewer instances to be spawned and fallback ports to be consumed.

Changes

• add registerMemoryRuntime(...) so OpenClaw can query memory status through the standard runtime interface
• expose plugin-backed memory status details such as files, chunks, sources, and vector readiness
• restrict viewer service registration to actual gateway processes
• prevent non-gateway CLI runs from triggering viewer self-start
• keep the fix limited to plugin code only

Result

After this change:

• openclaw status reports normal memory status instead of unavailable
• memory status can show values such as files, chunks, sources sessions, and vector ready
• CLI commands no longer spawn extra viewer instances
• the memory viewer lifecycle stays bound to the gateway process as expected

Notes

This PR does not include any local machine config workarounds or user-specific environment changes.
It only addresses the plugin-side integration and lifecycle issues.

Validation

Validated locally by confirming that:

• memory read/write was still working before and after the fix
• openclaw status no longer reported unavailable
• status output showed plugin-backed memory health information
• non-gateway CLI commands no longer created additional viewer listeners