From 94a19d79707dab5b67a6c494dd9be47740f4b36d Mon Sep 17 00:00:00 2001 From: "openclaw-docs-sync[bot]" Date: Sat, 2 May 2026 18:45:47 +0000 Subject: [PATCH] chore(sync): mirror docs from openclaw/openclaw@76c327c0964a0bfcec73e72931fff00613addc34 --- .openclaw-sync/source.json | 4 ++-- docs/plugins/manifest.md | 3 +++ 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/.openclaw-sync/source.json b/.openclaw-sync/source.json index 7ab8c9361..d52d4a075 100644 --- a/.openclaw-sync/source.json +++ b/.openclaw-sync/source.json @@ -1,5 +1,5 @@ { "repository": "openclaw/openclaw", - "sha": "38990c0e0979d475d48f52dda6ddd6376d97a705", - "syncedAt": "2026-05-02T18:30:30.961Z" + "sha": "76c327c0964a0bfcec73e72931fff00613addc34", + "syncedAt": "2026-05-02T18:43:43.925Z" } diff --git a/docs/plugins/manifest.md b/docs/plugins/manifest.md index 273b6c8b1..bdb88364a 100644 --- a/docs/plugins/manifest.md +++ b/docs/plugins/manifest.md @@ -1149,6 +1149,9 @@ If you are unsure where a piece of metadata belongs, use this rule: Some pre-runtime plugin metadata intentionally lives in `package.json` under the `openclaw` block instead of `openclaw.plugin.json`. +`openclaw.bundle` and `openclaw.bundle.json` are not OpenClaw plugin contracts; +native plugins must use `openclaw.plugin.json` plus the supported +`package.json#openclaw` fields below. Important examples: