Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

nvironment: OpenClaw 2026.4.12 on Linux/WSL2.

I enabled memory-wiki in bridge mode with:

vaultMode: "bridge"
search.backend: "shared"
search.corpus: "all"
bridge.readMemoryArtifacts: true
bridge.indexDreamReports: true
bridge.indexDailyNotes: true
bridge.indexMemoryRoot: true
bridge.followMemoryEvents: true
The workspace already contains:

MEMORY.md
many memory/*.md files
memory/.dreams/events.jsonl
openclaw memory status --json shows that the active memory plugin is working normally (memory-core, backend qmd), but openclaw wiki status --json still reports:

"bridgePublicArtifactCount": 0
and openclaw wiki doctor warns that bridge mode is enabled but no public memory artifacts are being exported.

This looks like a false negative in the openclaw wiki CLI path rather than missing memory data.

Steps to reproduce

1、Use OpenClaw with memory-core active and memory.backend = "qmd".
2、Ensure the workspace contains:
MEMORY.md
memory/*.md
memory/.dreams/events.jsonl
3、Enable memory-wiki with bridge mode, for example:
vaultMode: "bridge"
search.backend: "shared"
search.corpus: "all"
bridge.readMemoryArtifacts: true
4、Restart the gateway so memory-wiki is loaded.
5、Run:
openclaw memory status --json
openclaw wiki status --json
openclaw wiki doctor

Expected behavior

openclaw wiki status --json should report a non-zero bridgePublicArtifactCount, since memory-core should be able to expose at least:

the memory root file (MEMORY.md)
markdown files under memory/
the memory event log
openclaw wiki doctor should not warn that no public memory artifacts are available.

Actual behavior

openclaw wiki status --json reports:

"bridgePublicArtifactCount": 0
and openclaw wiki doctor reports:

Bridge mode is enabled but the active memory plugin is not exporting any public memory artifacts yet.
Even though:

memory-core is loaded
memory-wiki is loaded
the workspace contains valid memory files
openclaw memory status --json shows the memory stack is healthy
Possible cause: the standalone openclaw wiki CLI path may not be loading plugin registrations for the active memory capability, so listActiveMemoryPublicArtifacts(...) sees an empty registration state.

OpenClaw version

2026.4.12

Operating system

ubuntu

Install method

npm

Model

openai chatgpt codex 5.4

Provider / routing chain

openclaw -> proxy -> openai chatgpt codex 5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response