Summary

memory-wiki bridge import can return zero artifacts on cached plugin-load paths even when memory-core is loaded and the workspace contains valid memory artifacts.

Reproduction

1. Configure memory-wiki in bridge mode.
2. Ensure memory-core is the selected memory slot and the workspace contains exportable artifacts like MEMORY.md and memory/*.md.
3. Run openclaw wiki bridge import on a cached CLI/plugin-load path.

Expected

Bridge import should see the same exported artifacts as a fresh memory-core registration.

Actual

openclaw wiki bridge import reports 0 artifacts/workspaces on the cached path.

Root Cause

In dist/loader-*.js, cached plugin restore brings back memory runtime/prompt/flush state, but does not restore the registered memory capability. publicArtifacts lives on that capability, so listActiveMemoryPublicArtifacts() becomes empty after cache restore.

Cold registration exposes artifacts correctly; cached restore does not.

Proposed Fix

Persist and restore the full memory capability in the plugin registry cache, alongside:

• memory runtime
• memory prompt builder
• memory prompt supplements
• memory flush plan resolver
• memory corpus supplements

Why It Matters

This breaks the flagship qmd + memory-wiki bridge setup in a non-obvious way and makes bridge mode look unsupported when the actual problem is cache-state loss.