PR #81596: fix(telegram): expose CLI thread remap

• Repository: openclaw/openclaw
• Author: hclsys
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/81596

Description (problem / solution / changelog)

Summary

• forward Telegram's channel-owned resolveCliActionRequest through the exported Telegram plugin actions adapter
• preserve the existing default action/args behavior when no runtime or static remap exists
• add a plugin-surface contract test proving CLI thread-create remaps to Telegram topic-create

Fixes #81581.

Verification

• pnpm exec oxfmt --check extensions/telegram/src/channel.ts extensions/telegram/src/channel-actions.contract.test.ts
• pnpm vitest run extensions/telegram/src/channel-actions.contract.test.ts src/cli/program/message/register.thread.test.ts
• pnpm check:changed
• git diff --check

Real behavior proof

Behavior addressed: Before this patch, the static Telegram action implementation contained the thread-create -> topic-create remap, but the exported telegramPlugin.actions wrapper did not expose resolveCliActionRequest. The shared CLI asks the exported channel plugin for the remap, so Telegram thread creation could fall through as bare thread-create and reach the gateway unsupported.

Real setup tested: Local OpenClaw checkout at /home/chenglunhu/code/openclaw, branch fix/telegram-thread-create-cli-remap-81581, commit 1a534aa741cf0a7f65358e5d159d357d9e9f1822, using the real registerMessageThreadCommands CLI registration and exported telegramPlugin action surface through pnpm exec tsx.

Exact steps or command run after the patch: Registered the exported Telegram plugin in a test registry, registered the real message thread create command, parsed thread create --channel telegram -t -1003894873578 --thread-name "Test topic" --json, and captured the action/options that the CLI would dispatch.

Evidence after fix: Terminal output from the live command:

{
  "action": "topic-create",
  "target": "-1003894873578",
  "name": "Test topic",
  "hasThreadName": false
}

Observed result after fix: The CLI dispatch target is topic-create, the Telegram forum topic name is mapped to name, and the generic threadName field is removed before gateway dispatch. This is the action shape the Telegram runtime already supports.

Not tested: I did not call the live Telegram Bot API; the reporter already verified raw createForumTopic works and the bug is in OpenClaw's CLI/plugin dispatch boundary.

Scout audit

• Audit A (existing helper): existing remap helper found in extensions/telegram/src/channel-actions.ts; reused by forwarding it through the exported wrapper.
• Audit B (shared callers): no shared helper contract changed; ChannelMessageActionAdapter.resolveCliActionRequest contract preserved with default { action, args } fallback.
• Audit C (broader rival): gh pr list --search "81581 in:body" found no open rival PR.

Changed files

• extensions/telegram/src/channel-actions.contract.test.ts (modified, +21/-1)
• extensions/telegram/src/channel.ts (modified, +8/-0)

PR #81604: fix(telegram): forward resolveCliActionRequest in action wrapper

• Repository: openclaw/openclaw
• Author: kagura-agent
• State: open | merged: False
• Link: https://github.com/openclaw/openclaw/pull/81604

Description (problem / solution / changelog)

Summary

The telegramMessageActions wrapper in channel.ts delegates resolveExecutionMode, describeMessageTool, extractToolSend, and handleAction to the implementation in channel-actions.ts, but omits resolveCliActionRequest. This causes the CLI thread-create → topic-create remap to silently fail: getChannelPlugin('telegram').actions.resolveCliActionRequest is undefined, so the bare thread-create action reaches the gateway and is rejected as unsupported.

Related Issue

Closes #81581

Changes

• extensions/telegram/src/channel.ts: Add resolveCliActionRequest forwarding to the wrapper object, delegating to the existing implementation in channel-actions.ts
• extensions/telegram/src/channel-actions.test.ts: Add tests verifying the thread-create → topic-create remap and passthrough for other actions

Testing

✓ channel-actions.test.ts (8 tests, all pass)
✓ register.thread.test.ts (2 tests, all pass)

Real behavior proof

I don't have a Telegram bot configured to reproduce end-to-end. However, the root cause is verifiable by code inspection:

1. register.thread.ts:10 calls getChannelPlugin(channel)?.actions?.resolveCliActionRequest
2. channel.ts:219-244 defines the telegramMessageActions wrapper — before this fix, it had no resolveCliActionRequest property
3. Therefore, the optional chain always returned undefined, and the fallback at line 21 dispatched the bare thread-create action
4. handleAction in the same wrapper (line 234) calls resolveTelegramMessageActionName(action) which has no mapping for thread-create (only topic-create), throwing Unsupported Telegram action: thread-create

The fix adds the missing forwarding — the implementation in channel-actions.ts:164 already handles the remap correctly and is covered by the new unit tests.

CI Notes

• checks-fast-contracts-plugins-d: Pre-existing failure — codex-mcp-projection and codex-native-task-runtime are undocumented in the SDK guardrail test. Unrelated to this change.
• Real behavior proof: No Telegram bot available for live verification. Requesting proof: override if the code-level proof above is sufficient.

Changed files

• extensions/telegram/src/channel-actions.test.ts (modified, +22/-0)
• extensions/telegram/src/channel.ts (modified, +2/-0)