openclaw - 💡(How to fix) Fix [Bug]: registerCommand handler: no way to suppress "No response generated" when plugin owns its own transport send

name: "pulse",
description: "Liveness check",
acceptsArgs: false,
async handler(ctx) {
const chatId = telegramChatId(ctx.to ?? ctx.from);
await sendViaBotAPI(chatId, "✅ OK");
// returns undefined
},
});

### Expected behavior

**Expected behavior:**
Handler delivers the response. OpenClaw suppresses the fallback. 
User sees exactly one message.

### Actual behavior

**Actual behavior:**
User sees two messages: the correct handler response, then 
"No response generated. Please try again."

### OpenClaw version

2026.5.10-beta.5 (1ba6893)

### Operating system

Windows 11 Pro (win32 x64)

### Install method

npm install -g [email protected]

### Model

**Model:** anthropic/claude-sonnet-4-6 (primary) **Model routing:** Gemini 2.5 Flash-Lite for boot acknowledgment and  non-procurement triage; Haiku for lightweight calls; Sonnet for  email drafting, document review, BCC extraction **Note:** Issue is not model-dependent — registerCommand handlers that  return undefined trigger the fallback regardless of whether a model  call occurred

### Provider / routing chain

**Provider / routing chain:** Telegram inbound → registerCommand handler → Telegram Bot API direct send  (custom https.request with IPv4 forcing + retry loop) → returns undefined  → OpenClaw Telegram channel adapter sends fallback

### Additional provider/model setup details

**Request:**
Add a first-class silent result for registerCommand handlers that own 
their own transport delivery:
- `return { suppressReply: true }` — suppress fallback, send nothing
- or `return { handled: true }` — same semantics as before_dispatch

Confirmed with krill in Discord as a known gap worth filing.

**Why the plugin owns transport:**
Custom send logic required: IPv4 family forcing (`family: 4`) to avoid 
Happy Eyeballs dual-stack failure on Windows, 3-attempt retry with 
exponential backoff, chunked message splitting for long responses, 
MarkdownV1 escaping. These aren't available through the return payload path.

### Logs, screenshots, and evidence

```shell