hermes - 💡(How to fix) Fix [Feishu] First chunk of long messages sent as msg_type=text instead of post, breaking Markdown rendering [1 pull requests]

Bug Description

When Hermes sends a long message to Feishu that requires chunking (splitting into multiple parts), the first chunk is sent with msg_type=text instead of msg_type=post. Because only post type messages render Markdown in Feishu, the first chunk is displayed as raw Markdown syntax (e.g., **bold**, ## heading, code blocks all appear literally).

Subsequent chunks appear to be sent correctly as post type.

Steps to Reproduce

1. Ask the Hermes agent a question that produces a long, Markdown-rich response (e.g., a detailed explanation with headers, bold text, and code blocks)
2. Observe the response in the Feishu client
3. The first message chunk shows raw Markdown text; later chunks render correctly

Expected Behavior

All chunks — including the first — should be sent with msg_type=post so Markdown renders consistently.

Actual Behavior

First chunk uses msg_type=text, resulting in raw Markdown being displayed to the user.

Diagnosis

Use +chat-messages-list to inspect the msg_type field of outgoing messages and confirm the first chunk uses text type while subsequent chunks use post type.

Environment

• Platform: Feishu / Lark
• Component: Gateway — Feishu adapter (message chunking/splitting path)