diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 0b442863a..64d39c21c 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "a0ca54699722ba47e285e4be58a49e2ec0410503",
-  "syncedAt": "2026-04-26T02:34:19.349Z"
+  "sha": "f0fa35082b7b269ce2bc14cac3c962e5b43f48b0",
+  "syncedAt": "2026-04-26T02:40:20.433Z"
 }
diff --git a/docs/tools/acp-agents.md b/docs/tools/acp-agents.md
index 6d990f09f..868e4c994 100644
--- a/docs/tools/acp-agents.md
+++ b/docs/tools/acp-agents.md
@@ -372,7 +372,7 @@ One-shot ACP sessions spawned by another agent run are background children, simi
 - The parent asks for work with `sessions_spawn({ runtime: "acp", mode: "run" })`.
 - The child runs in its own ACP harness session.
 - Child turns run on the same background lane used by native sub-agent spawns, so a slow ACP harness does not block unrelated main-session work.
-- Completion reports back through the internal task-completion announce path.
+- Completion reports back through the task-completion announce path. OpenClaw converts internal completion metadata into a plain ACP prompt before sending it to an external harness, so harnesses do not see OpenClaw-only runtime context markers.
 - The parent rewrites the child result in normal assistant voice when a user-facing reply is useful.
 
 Do not treat this path as a peer-to-peer chat between parent and child. The child already has a completion channel back to the parent.