diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 25f0e0083..2b197a2c4 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "e53c45ba94620341e40dffa340b4ac4af8de5906",
-  "syncedAt": "2026-04-29T03:25:22.517Z"
+  "sha": "e27fe55aa8e345806e252c2e1d12f9a442b894d4",
+  "syncedAt": "2026-04-29T03:34:28.855Z"
 }
diff --git a/docs/plugins/architecture-internals.md b/docs/plugins/architecture-internals.md
index fe1530151..eafbcab53 100644
--- a/docs/plugins/architecture-internals.md
+++ b/docs/plugins/architecture-internals.md
@@ -92,6 +92,10 @@ backends registered by setup-api without blocking legacy plugins.
 OpenClaw does not cache plugin discovery results or direct manifest registry
 data behind wall-clock windows. Installs, manifest edits, and load-path changes
 must become visible on the next explicit metadata read or snapshot rebuild.
+The manifest file parser may keep a bounded file-signature cache keyed by the
+opened manifest path, inode, size, and timestamps; that cache only avoids
+re-parsing unchanged bytes and must not cache discovery, registry, owner, or
+policy answers.
 
 The safe metadata fast path is explicit object ownership, not a hidden cache.
 Gateway startup hot paths should pass the current `PluginMetadataSnapshot`, the