[Bug] WeChat channel leaks internal <bubble/> marker instead of splitting messages

[necoarc-000]

Bug Description

The WeChat channel is exposing the internal <bubble/> marker in user-facing messages.

The <bubble/> tag appears to be an internal message separator used for splitting one AI response into multiple WeChat bubbles, but currently it is not being processed correctly before sending to WeChat.

Instead of receiving multiple messages, users receive the raw marker text.

Environment

• Platform: MaxClaw / OpenClaw
• Channel: @tencent-weixin/openclaw-weixin
• Model provider: MiniMax
• Client: WeChat

Current Behavior

Example message:
行。你先点，加我最爱吃的几样。
The user receives exactly this text in WeChat.

The message is not split into two bubbles, and the <bubble/> marker is visible.

Expected Behavior

One of the following behaviors should happen:

Option 1:
行
(second bubble)
你先点，加我最爱吃的几样。

Option 2:

If bubble splitting is disabled, the internal marker should at least be removed:
行。你先点，加我最爱吃的几样。
The internal <bubble/> tag should never appear to end users.

Additional Investigation

I tested the same message flow in the MiniMax app.

Observation:

1. MiniMax chat UI does not display <bubble/>.
2. However, copying the same message from MiniMax app includes the raw <bubble/> text.
3. Sending through WeChat channel exposes the raw <bubble/>.

This suggests:

• <bubble/> exists in the underlying message payload.
• MiniMax UI renderer hides it correctly.
• The WeChat channel does not sanitize or parse this internal marker before sending.

Frequency

The issue started recently.

Previously, messages sent through WeChat did not contain <bubble/>.

Possible Cause

The WeChat channel may have lost the processing step for internal message markers.

Possible fixes:

• Parse <bubble/> before sending messages.
• Split messages based on <bubble/>.
• Or sanitize internal markers before sending to external channels.