LLM/moltbot
1
0
Fork 0
mirror of https://github.com/moltbot/moltbot.git synced 2026-04-24 07:01:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

refactor: remove generated plugin sdk facades

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-05 09:06:11 +01:00
parent fd968bfb2d
commit 1903be5401
69 changed files with 104 additions and 2885 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/plugins/architecture.md
View File

@@ -1175,11 +1175,9 @@ authoring plugins:
OpenClaw is not yet serving a runtime snapshot.
- Generic shared primitives remain the preferred public SDK contract. A small
reserved compatibility set of bundled channel-branded helper seams still
exists, including `plugin-sdk/whatsapp-surface` for narrow WhatsApp
auth/account, directory-config, group-policy, outbound-target, and web-media
helper exports. Treat those as bundled-maintenance/compatibility seams, not
new third-party import targets; new cross-channel contracts should still land
on generic `plugin-sdk/*` subpaths or the plugin-local `api.js` /
exists. Treat those as bundled-maintenance/compatibility seams, not new
third-party import targets; new cross-channel contracts should still land on
generic `plugin-sdk/*` subpaths or the plugin-local `api.js` /
`runtime-api.js` barrels.
Compatibility note:

9
docs/plugins/sdk-channel-plugins.md
View File

@@ -494,11 +494,10 @@ Write colocated tests in `src/channel.test.ts`:
</CardGroup>
<Note>
Reserved bundled-helper seams such as `plugin-sdk/whatsapp-surface` still
exist for bundled-plugin maintenance and compatibility. They are not the
recommended pattern for new channel plugins; prefer the generic channel/setup/
reply/runtime subpaths from the common SDK surface unless you are maintaining
that bundled plugin family directly.
Some bundled helper seams still exist for bundled-plugin maintenance and
compatibility. They are not the recommended pattern for new channel plugins;
prefer the generic channel/setup/reply/runtime subpaths from the common SDK
surface unless you are maintaining that bundled plugin family directly.
</Note>
## Next steps