Environment

• OpenClaw 2026.4.21 (f788c88)
• macOS Tahoe 26.4.1 arm64
• memory-core, active-memory, and memory-wiki all loaded

Config

• memory-wiki: bridge mode, bridge.enabled=true, readMemoryArtifacts=true, indexDailyNotes=true, indexMemoryRoot=true
• memory-core: dreaming.enabled=true (cron 0 3 * * *)
• active-memory: enabled=true, queryMode=recent
• 5 agents configured in agents.list with explicit workspace paths

Problem

openclaw wiki bridge import --json consistently returns:

{
  "artifactCount": 0,
  "workspaces": 0
}

All three plugins show as loaded in openclaw plugins list. The main workspace has MEMORY.md and 29 daily note files in memory/. Dreaming has been enabled and triggered manually — dreaming promotion complete (workspaces=5, candidates=0, applied=0, failed=0) appears in the gateway log, confirming the dreaming runtime sees all 5 workspaces correctly.

However, listActiveMemoryPublicArtifacts returns [], causing bridge import to find 0 artifacts and 0 workspaces.

Diagnosis

PR #69219 (shipped in 4.20) fixed a bug where restoreMemoryPluginState was omitting the capability field, effectively wiping publicArtifacts after non-activating plugin loads. This fix appears to not fully resolve the issue — possibly a code path that still triggers the wipe after the fix.

Evidence:

• collectWorkspaceArtifacts should find MEMORY.md and memory/*.md files in all 5 workspaces
• resolveMemoryDreamingWorkspaces returns 5 workspaces during dreaming runtime (confirmed by log)
• But bridge import sees 0 workspaces, suggesting the capability is empty/wiped when bridge import runs

Expected

openclaw wiki bridge import should return artifacts for MEMORY.md and daily notes across all configured agent workspaces.

Steps to Reproduce

1. Enable memory-wiki in bridge mode with all bridge index flags true
2. Enable memory-core dreaming
3. Have MEMORY.md and memory/*.md files in workspace
4. Run openclaw wiki bridge import --json
5. Observe artifactCount=0, workspaces=0