From 60206817b381be3957716fd2f58f27374ecbb690 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Sat, 4 Apr 2026 14:38:23 +0100 Subject: [PATCH] docs: refresh telegram command sdk refs --- docs/plugins/architecture.md | 4 ++++ docs/plugins/sdk-channel-plugins.md | 3 +++ docs/plugins/sdk-migration.md | 3 +++ docs/plugins/sdk-overview.md | 2 ++ 4 files changed, 12 insertions(+) diff --git a/docs/plugins/architecture.md b/docs/plugins/architecture.md index 6d4c638e502..e07b63a5d7c 100644 --- a/docs/plugins/architecture.md +++ b/docs/plugins/architecture.md @@ -1051,6 +1051,7 @@ authoring plugins: - Domain subpaths such as `openclaw/plugin-sdk/channel-config-helpers`, `openclaw/plugin-sdk/allow-from`, `openclaw/plugin-sdk/channel-config-schema`, + `openclaw/plugin-sdk/telegram-command-config`, `openclaw/plugin-sdk/channel-policy`, `openclaw/plugin-sdk/approval-runtime`, `openclaw/plugin-sdk/config-runtime`, @@ -1062,6 +1063,9 @@ authoring plugins: `openclaw/plugin-sdk/status-helpers`, `openclaw/plugin-sdk/runtime-store`, and `openclaw/plugin-sdk/directory-runtime` for shared runtime/config helpers. + `telegram-command-config` is the narrow public seam for Telegram custom + command normalization/validation and stays available even if the bundled + Telegram contract surface is temporarily unavailable. - Approval-specific channel seams should prefer one `approvalCapability` contract on the plugin. Core then reads approval auth, delivery, render, and native-routing behavior through that one capability instead of mixing diff --git a/docs/plugins/sdk-channel-plugins.md b/docs/plugins/sdk-channel-plugins.md index 145aa3f1b25..364b1c45148 100644 --- a/docs/plugins/sdk-channel-plugins.md +++ b/docs/plugins/sdk-channel-plugins.md @@ -105,6 +105,9 @@ surfaces: and adapter registration - `openclaw/plugin-sdk/agent-media-payload` only when a legacy agent/media payload field layout is still required +- `openclaw/plugin-sdk/telegram-command-config` for Telegram custom-command + normalization, duplicate/conflict validation, and a fallback-stable command + config contract Auth-only channels can usually stop at the default path: core handles approvals and the plugin just exposes outbound/auth capabilities. Native approval channels such as Matrix, Slack, Telegram, and custom chat transports should use the shared native helpers instead of rolling their own approval lifecycle. diff --git a/docs/plugins/sdk-migration.md b/docs/plugins/sdk-migration.md index 8501d463f9f..2f1486af0db 100644 --- a/docs/plugins/sdk-migration.md +++ b/docs/plugins/sdk-migration.md @@ -173,6 +173,7 @@ Current bundled provider examples: | `plugin-sdk/channel-reply-pipeline` | Reply prefix + typing wiring | `createChannelReplyPipeline` | | `plugin-sdk/channel-config-helpers` | Config adapter factories | `createHybridChannelConfigAdapter` | | `plugin-sdk/channel-config-schema` | Config schema builders | Channel config schema types | + | `plugin-sdk/telegram-command-config` | Telegram command config helpers | Command-name normalization, description trimming, duplicate/conflict validation | | `plugin-sdk/channel-policy` | Group/DM policy resolution | `resolveChannelGroupRequireMention` | | `plugin-sdk/channel-lifecycle` | Account status tracking | `createAccountStatusSink` | | `plugin-sdk/inbound-envelope` | Inbound envelope helpers | Shared route + envelope builder helpers | @@ -192,6 +193,8 @@ Current bundled provider examples: | `plugin-sdk/process-runtime` | Process helpers | Shared exec helpers | | `plugin-sdk/cli-runtime` | CLI runtime helpers | Command formatting, waits, version helpers | | `plugin-sdk/gateway-runtime` | Gateway helpers | Gateway client and channel-status patch helpers | + | `plugin-sdk/config-runtime` | Config helpers | Config load/write helpers | + | `plugin-sdk/telegram-command-config` | Telegram command helpers | Fallback-stable Telegram command validation helpers when the bundled Telegram contract surface is unavailable | | `plugin-sdk/approval-runtime` | Approval prompt helpers | Exec/plugin approval payload, approval capability/profile helpers, native approval routing/runtime helpers | | `plugin-sdk/approval-auth-runtime` | Approval auth helpers | Approver resolution, same-chat action auth | | `plugin-sdk/approval-client-runtime` | Approval client helpers | Native exec approval profile/filter helpers | diff --git a/docs/plugins/sdk-overview.md b/docs/plugins/sdk-overview.md index a0701898b33..bf944273031 100644 --- a/docs/plugins/sdk-overview.md +++ b/docs/plugins/sdk-overview.md @@ -86,6 +86,7 @@ explicitly promotes one as public. | `plugin-sdk/channel-reply-pipeline` | `createChannelReplyPipeline` | | `plugin-sdk/channel-config-helpers` | `createHybridChannelConfigAdapter` | | `plugin-sdk/channel-config-schema` | Channel config schema types | + | `plugin-sdk/telegram-command-config` | Telegram custom-command normalization/validation helpers with bundled-contract fallback | | `plugin-sdk/channel-policy` | `resolveChannelGroupRequireMention` | | `plugin-sdk/channel-lifecycle` | `createAccountStatusSink` | | `plugin-sdk/inbound-envelope` | Shared inbound route + envelope builder helpers | @@ -172,6 +173,7 @@ explicitly promotes one as public. | `plugin-sdk/cli-runtime` | CLI formatting, wait, and version helpers | | `plugin-sdk/gateway-runtime` | Gateway client and channel-status patch helpers | | `plugin-sdk/config-runtime` | Config load/write helpers | + | `plugin-sdk/telegram-command-config` | Telegram command-name/description normalization and duplicate/conflict checks, even when the bundled Telegram contract surface is unavailable | | `plugin-sdk/approval-runtime` | Exec/plugin approval helpers, approval-capability builders, auth/profile helpers, native routing/runtime helpers | | `plugin-sdk/reply-runtime` | Shared inbound/reply runtime helpers, chunking, dispatch, heartbeat, reply planner | | `plugin-sdk/reply-dispatch-runtime` | Narrow reply dispatch/finalize helpers |