Summary

Fixes Mattermost thread replies failing with root_id.app_error (400) when MATTERMOST_REPLY_MODE=thread is enabled.

Problem

When a user messages the bot inside an existing Mattermost thread, reply_to is set to event.message_id — the ID of the individual reply post. But Mattermost requires root_id to be the first post that started the thread. Using a non-root post ID causes:

{"id":"api.post.create_post.root_id.app_error","message":"Invalid RootId parameter","status_code":400}

Fix

In send(), _download_and_post_file(), and _send_local_file(): prefer metadata.thread_id (which base.py already populates from event.source.thread_id, i.e. the actual thread root) over reply_to. This handles both cases:

• New thread (message in channel): no thread_id in metadata → falls back to reply_to, creating a new thread under the user's message
• Existing thread (reply in thread): thread_id is the root post → reply lands in the correct thread

Test plan

• Send a message in a channel with MATTERMOST_REPLY_MODE=thread → bot creates a new thread (reply under user's message)
• Reply to the bot inside that thread → bot replies in the same thread (no 400 error)
• Send a DM → bot responds normally (no thread behavior)
• Send an image/file in a thread → attachment lands in the correct thread