diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json
index 1ffd9fe7a..42cd29fca 100644
--- a/.openclaw-sync/source.json
+++ b/.openclaw-sync/source.json
@@ -1,5 +1,5 @@
 {
   "repository": "openclaw/openclaw",
-  "sha": "925d11d89054c5dd1ba31de5537d2ee3cb5cdd3b",
-  "syncedAt": "2026-04-24T06:43:03.131Z"
+  "sha": "bcdacfa1b3df000ce04e3ce26bbe3051e56da3e8",
+  "syncedAt": "2026-04-24T07:25:52.072Z"
 }
diff --git a/docs/.generated/plugin-sdk-api-baseline.sha256 b/docs/.generated/plugin-sdk-api-baseline.sha256
index e476d320f..ed46e2067 100644
--- a/docs/.generated/plugin-sdk-api-baseline.sha256
+++ b/docs/.generated/plugin-sdk-api-baseline.sha256
@@ -1,2 +1,2 @@
-ad7ec565b1702a76a87b1a08904445c9838e10d4d41fb1c58909af886b702d80  plugin-sdk-api-baseline.json
-907a07c206dd52ebd910793fab7bca8640c37cf82ff7e7cca88ab1b12b4fbdfe  plugin-sdk-api-baseline.jsonl
+c0f788d1895ced2ffdad9f82e6afc592171e6651c61c0fc5083f0040437cda6d  plugin-sdk-api-baseline.json
+70e320157331080b98f9c2acae58e89ad1dc70b48adad265225a7eb76b6ac29f  plugin-sdk-api-baseline.jsonl
diff --git a/docs/automation/hooks.md b/docs/automation/hooks.md
index f59ef9afb..eefec6b7a 100644
--- a/docs/automation/hooks.md
+++ b/docs/automation/hooks.md
@@ -106,7 +106,7 @@ const handler = async (event) => {
 export default handler;
 ```
 
-Each event includes: `type`, `action`, `sessionKey`, `timestamp`, `messages` (push to send to user), and `context` (event-specific data).
+Each event includes: `type`, `action`, `sessionKey`, `timestamp`, `messages` (push to send to user), and `context` (event-specific data). Agent and tool plugin hook contexts can also include `trace`, a read-only W3C-compatible diagnostic trace context that plugins may pass into structured logs for OTEL correlation.
 
 ### Event context highlights
 
diff --git a/docs/plugins/codex-harness.md b/docs/plugins/codex-harness.md
index f376540f4..e520b3f8e 100644
--- a/docs/plugins/codex-harness.md
+++ b/docs/plugins/codex-harness.md
@@ -536,6 +536,10 @@ Until then, OpenClaw's `before_compaction`, `after_compaction`, `llm_input`, and
 `llm_output` events are adapter-level observations, not byte-for-byte captures
 of Codex's internal request or compaction payloads.
 
+Codex native `hook/started` and `hook/completed` app-server notifications are
+projected as `codex_app_server.hook` agent events for trajectory and debugging.
+They do not invoke OpenClaw plugin hooks.
+
 ## Tools, media, and compaction
 
 The Codex harness changes the low-level embedded agent executor only.