fix(feishu): keep media replies in threads

[sweetcornna]

Summary

• preserve a generic reply_to_message_id in non-Telegram thread metadata
• apply the fix to both BasePlatformAdapter media delivery and GatewayRunner post-stream media delivery
• add Feishu image-media regression coverage for both delivery paths

Fixes #39526

Tests

• .venv\Scripts\python.exe -m pytest tests\gateway\test_tts_media_routing.py tests\gateway\test_telegram_thread_fallback.py::test_base_gateway_metadata_marks_telegram_dm_topics_as_reply_fallback tests\gateway\test_telegram_thread_fallback.py::test_gateway_runner_busy_ack_replies_to_triggering_message_for_telegram_dm_topic tests\gateway\test_telegram_thread_fallback.py::test_media_group_dm_topic_reply_not_found_retry_drops_thread_id -q --timeout-method=thread
• .venv\Scripts\ruff.exe check gateway\platforms\base.py gateway\run.py tests\gateway\test_tts_media_routing.py
• .venv\Scripts\python.exe -m py_compile gateway\platforms\base.py gateway\run.py tests\gateway\test_tts_media_routing.py
• git diff --check (passes with Windows CRLF working-copy warnings only)

Notes

• tests\gateway\test_feishu.py full-file run on Windows currently fails before assertions when tests clear HOME/LOCALAPPDATA and Path.home() cannot resolve a home directory; not caused by this change.

[teknium1]

Thanks for tracing both response-media delivery paths; the anchor propagation addresses the current omission in gateway/platforms/base.py:55-77 and gateway/run.py:14357-14401.

Problems

• The PR does not change plugins/platforms/feishu/adapter.py:4626-4635, where a Feishu thread with no reply anchor still builds CreateMessage(receive_id_type="thread_id"). The standalone sender supplies only {"thread_id": thread_id} at plugins/platforms/feishu/adapter.py:5418 and then sends media at :5431-5439, so that sibling remains exposed to the 99992402 failure reported in Feishu: MEDIA attachments sent via topic/thread reply land in main conversation instead of thread #39526/Feishu: image/file MEDIA delivery in thread fails with 99992402 — receive_id_type='thread_id' invalid #61000.

Suggested changes

• Preserve this response-media anchor work, and pair it with a safe no-anchor fallback in the Feishu adapter that never sends receive_id_type="thread_id"; add a regression for that branch.
• The proposed helper condition covers every non-Telegram platform. Please scope it to Feishu unless the generic metadata contract is intentional and audited.

Automated hermes-sweeper review.

[tchivs]

I rebased this PR's commit onto current main with the original authorship preserved, scoped reply-anchor metadata to Feishu per the automated review, and added the missing adapter-side strict no-fallback behavior plus live/topic regression coverage. The consolidated follow-up is #64343. Thank you for the original media-path fix.

[sweetcornna]

Closing in favor of #64343, which rebases and preserves this PR’s original commit, then completes the adapter-side strict routing and regression coverage requested during review. Thanks for consolidating the Feishu topic fix.