Validate Memrok through clean user-like install paths

[MichaelSchmidle]

Ripe follow-up from the current v0.6.0 → v1.0 gap analysis.

Goal

Validate Memrok through clean user-like OpenClaw install and distribution paths, not only the dev-mounted plugin path.

Why

Current coverage is better than before:

• packaged-plugin smoke exists
• plugin-path runtime event coverage exists

But we still do not have one cleanly tracked work item for the broader real-user install/distribution matrix.

Include

• clean OpenClaw home/state setup
• ordinary plugin install path closer to user consumption
• validation that Memrok loads, initializes, and performs basic context-engine behavior
• enough coverage to catch packaging/install/distribution drift that the dev-mounted path hides

Non-goal

• do not build a huge environment matrix at once
• start with the smallest credible user-like install path