openclaw - 💡(How to fix) Fix [Bug]: @openclaw/[email protected] npm bundle missing publicArtifacts registration from #85060

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

After upgrading to 2026.5.22, memory-wiki bridge mode reports 0 exported artifacts on top of memory-lancedb; the installed @openclaw/[email protected] dist/ contains zero references to the publicArtifacts.listArtifacts registration added by #85060.

Steps to reproduce

1. Install OpenClaw 2026.5.22 with bundled @openclaw/[email protected] from npm (via openclaw plugins install @openclaw/memory-lancedb).
2. Set plugins.slots.memory = "memory-lancedb" and enable memory-wiki with:
   • config.vaultMode = "bridge"
   • config.bridge.enabled = true
   • config.bridge.readMemoryArtifacts = true
3. Ensure the workspace contains real public artifacts on disk (here: ~/.openclaw/workspace/MEMORY.md, ~/.openclaw/workspace/memory/daily/*.md with 300+ files, ~/.openclaw/workspace/memory/dreaming/{deep,light,rem}/).
4. Restart the gateway: openclaw gateway restart.
5. Run openclaw wiki doctor and openclaw wiki bridge import.

Expected behavior

Per the 2026.5.22 changelog entry for #85060 ("Memory/LanceDB: expose public memory artifacts through the active memory provider bridge so memory-wiki imports durable memory files, daily notes, dream reports, and event logs without depending on memory-core internals. Fixes #83604."), memory-lancedb should register publicArtifacts.listArtifacts, and wiki bridge import should surface the on-disk MEMORY.md and daily notes (PR proof shows importedCount: 3 against three artifacts).

Actual behavior

wiki doctor reports Bridge: enabled (0 exported artifacts) and wiki bridge import returns Bridge import synced 0 artifacts across 0 workspaces. A grep on the installed @openclaw/[email protected] dist/ shows zero matches for publicArtifacts, listArtifacts, or registerMemoryCapability, while the same grep on @openclaw/memory-core dist/ does match. Rolling back memory-wiki to vaultMode: "isolated" restores wiki doctor: healthy.

OpenClaw version

2026.5.22 (a374c3a)

Operating system

macOS 15.5 (Darwin 25.5.0, arm64)

Install method

Homebrew openclaw CLI 2026.5.22; @openclaw/[email protected] installed via openclaw plugins install @openclaw/memory-lancedb (resolves under ~/.openclaw/npm/node_modules/@openclaw/memory-lancedb).

Model

NOT_ENOUGH_INFO (reproduction does not involve a model; the issue is in plugin package contents and reproduces with the gateway alone).

Provider / routing chain

NOT_ENOUGH_INFO (no provider routing involved; the failure is observed in openclaw wiki doctor / openclaw wiki bridge import against a local LanceDB-backed memory slot).

Additional provider/model setup details

NOT_ENOUGH_INFO

Logs, screenshots, and evidence

$ openclaw --version
OpenClaw 2026.5.22 (a374c3a)

$ openclaw config get plugins.slots.memory
memory-lancedb

$ openclaw config get plugins.entries.memory-wiki.config.vaultMode
bridge

$ openclaw config get plugins.entries.memory-wiki.config.bridge.enabled
true

$ openclaw config get plugins.entries.memory-wiki.config.bridge.readMemoryArtifacts
true

$ cat ~/.openclaw/npm/node_modules/@openclaw/memory-lancedb/package.json | grep '"version"'
  "version": "2026.5.22",

$ grep -rE "publicArtifacts|listArtifacts|registerMemoryCapability" \
    ~/.openclaw/npm/node_modules/@openclaw/memory-lancedb/dist/
# (no output — zero matches across:
#   dist/index.js, dist/lancedb-runtime.js, dist/cli-metadata.js,
#   dist/config.js, dist/test-helpers.js, dist/api.js)

$ openclaw wiki doctor
Wiki doctor: 1 issue(s) found

Wiki vault mode: bridge
Vault: ready (/Users/<user>/.openclaw/wiki/main)
Render mode: native
Obsidian CLI: missing
Bridge: enabled (0 exported artifacts)
Unsafe local: disabled
Pages: 6 sources, 6 entities, 3 concepts, 19 syntheses, 10 reports
Source provenance: 0 native, 0 bridge, 0 bridge-events, 0 unsafe-local, 6 other

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

Suggested fixes:
- Use a memory plugin that exports public artifacts, create/import memory artifacts first, or switch the wiki back to isolated mode.

$ openclaw wiki bridge import
Bridge import synced 0 artifacts across 0 workspaces (0 new, 0 updated, 0 unchanged, 0 removed). Indexes not refreshed (no-import-changes).

# After rollback to vaultMode=isolated:
$ openclaw wiki doctor
Wiki doctor: healthy
Wiki vault mode: isolated
...

For comparison, the on-disk workspace does have artifacts that the PR proof claims should be surfaced:

$ ls ~/.openclaw/workspace/MEMORY.md
/Users/<user>/.openclaw/workspace/MEMORY.md

$ ls ~/.openclaw/workspace/memory/daily/ | wc -l
     364

$ ls ~/.openclaw/workspace/memory/dreaming/
deep    light   rem

Impact and severity

Affected: any operator on 2026.5.22 who selects memory-lancedb as the memory slot and wants to use memory-wiki in vaultMode: bridge. Severity: blocks the documented bridge workflow for the lancedb slot; users must remain on isolated, losing the durable-memory import path that #85060 advertised. Frequency: 100% reproducible on the installed package (verified by direct file-content grep, not just behavior). Consequence: wiki bridge import is a no-op against an otherwise populated workspace; the user-visible "expose public memory artifacts" capability from the 2026.5.22 release notes is not functional via npm.

Additional information

@openclaw/[email protected] was published to npm at 2026-05-24T02:58:07Z (after PR #85060 merged at 2026-05-23T09:33:27Z). @openclaw/[email protected] is not yet published (npm view returns 404), and the 2026.5.24 section of CHANGELOG.md on main does not mention a memory-lancedb rebuild or any reference to #85060 / publicArtifacts.

Workaround: revert memory-wiki to vaultMode: "isolated", bridge.enabled: false, bridge.readMemoryArtifacts: false.