From 6800c5ab84f473ca834573340a883ffc5ca62c92 Mon Sep 17 00:00:00 2001
From: "openclaw-docs-sync[bot]"
 <openclaw-docs-sync[bot]@users.noreply.github.com>
Date: Tue, 28 Apr 2026 10:24:41 +0000
Subject: [PATCH] chore(sync): mirror docs from
 openclaw/openclaw@e2f3044b8fb7d667edff52df8e1c7cac22cd2d08

---
 .openclaw-sync/source.json  |  4 ++--
 docs/cli/wiki.md            | 13 +++++++++++++
 docs/plugins/memory-wiki.md |  6 ++++++
 3 files changed, 21 insertions(+), 2 deletions(-)

diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index a216040a5..e630191c0 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "1b13f53047ee78f2318e60b7f02b214934661cae",
-  "syncedAt": "2026-04-28T10:21:27.170Z"
+  "sha": "e2f3044b8fb7d667edff52df8e1c7cac22cd2d08",
+  "syncedAt": "2026-04-28T10:23:15.277Z"
 }
diff --git a/docs/cli/wiki.md b/docs/cli/wiki.md
index 5a25e8d3d..477bf2b64 100644
--- a/docs/cli/wiki.md
+++ b/docs/cli/wiki.md
@@ -68,10 +68,18 @@ Inspect current vault mode, health, and Obsidian CLI availability.
 Use this first when you are unsure whether the vault is initialized, bridge mode
 is healthy, or Obsidian integration is available.
 
+When bridge mode is active and configured to read memory artifacts, this command
+queries the running Gateway so it sees the same active memory plugin context as
+agent/runtime memory.
+
 ### `wiki doctor`
 
 Run wiki health checks and surface configuration or vault problems.
 
+When bridge mode is active and configured to read memory artifacts, this command
+queries the running Gateway before building the report. Disabled bridge imports
+and bridge configs that do not read memory artifacts remain local/offline.
+
 Typical issues include:
 
 - bridge mode enabled without public memory artifacts
@@ -168,6 +176,11 @@ source pages.
 Use this in `bridge` mode when you want the latest exported memory artifacts
 pulled into the wiki vault.
 
+For active bridge artifact reads, the CLI routes the import through Gateway RPC
+so the import uses the runtime memory plugin context. If bridge imports are
+disabled or artifact reads are turned off, the command keeps the local/offline
+zero-import behavior.
+
 ### `wiki unsafe-local import`
 
 Import from explicitly configured local paths in `unsafe-local` mode.
diff --git a/docs/plugins/memory-wiki.md b/docs/plugins/memory-wiki.md
index e9bae2519..abe381439 100644
--- a/docs/plugins/memory-wiki.md
+++ b/docs/plugins/memory-wiki.md
@@ -65,6 +65,12 @@ If bridge mode reports zero exported artifacts, the active memory plugin is not
 currently exposing public bridge inputs yet. Run `openclaw wiki doctor` first,
 then confirm the active memory plugin supports public artifacts.
 
+When bridge mode is active and `bridge.readMemoryArtifacts` is enabled,
+`openclaw wiki status`, `openclaw wiki doctor`, and `openclaw wiki bridge
+import` read through the running Gateway. That keeps CLI bridge checks aligned
+with the runtime memory plugin context. If bridge is disabled or artifact reads
+are turned off, those commands keep their local/offline behavior.
+
 ## Vault modes
 
 `memory-wiki` supports three vault modes: