Overlaps significantly with #14336 (proactive messaging + media support) and subsumes #14892 / #10392 (Feishu media routing fix). Consider consolidating with the #12769 umbrella series.

Hi @alt-glitch, thanks for the detailed cross-referencing! 🙏

You're spot on — this PR touches the send_message_tool.py to add native DingTalk and Feishu routing with media support, which overlaps with #14336's scope and subsumes #14892 / #10392.

We're the DingTalk (钉钉) Open Platform team at Alibaba — @PeterGuy326 and @spike2204 are colleagues. This is the final piece of our fine-grained PR series, extracted from the original stacked #14336.

What this PR specifically does:

1. MEDIA tag enhancement — adds MEDIA:/path/to/file tag support + bare absolute path auto-detection (BasePlatformAdapter.extract_local_files()) to the send_message tool schema
2. DingTalk native routing — routes through dingtalk_send_proactive() (from feat(dingtalk): proactive messaging via Robot OpenAPI #17370) with full media upload support, instead of the limited legacy webhook-only path
3. Feishu native routing — adds media_files passthrough to _send_feishu(), fixing fix(send_message): route media attachments through Feishu adapter #14892 / fix: enable Feishu media delivery in send_message #10392
4. Legacy fallback — preserves DINGTALK_WEBHOOK_URL for single-group deployments without OpenAPI access

Regarding consolidation with #12769: We fully agree — all 8 PRs in this series (#17364–#17371) are tracked under the umbrella #12769. Once reviewed, we'll close the original stacked PRs (#14333–#14336). The 8 fine-grained PRs can be merged in any order since each is self-contained against main.

Looking forward to your feedback! 🚀

Hi @alt-glitch 👋 — just a gentle follow-up on this PR series (#17364 – #17371).

We'd really appreciate it if these could be prioritized for review. Here's why:

1. Production-critical fixes — These PRs address real issues we're hitting in our production deployment serving thousands of DingTalk users daily (HTTP 429 storms from missing QPS throttle, lost conversational context from unparsed quoted-replies, broken media pipelines with 403s on signed OSS URLs, etc.).

2. Clean, self-contained PRs — We've already re-structured the original stacked PRs (fix(dingtalk): adapter reliability — websockets proxy, card QPS throttle, inbound queue #14333–feat(dingtalk): proactive messaging via Robot OpenAPI + send_message_tool media support #14336) into 8 independent, well-tested PRs against main, each reviewable and mergeable on its own — specifically to make the review process easier.

3. Upstream alignment — We're the DingTalk Open Platform team at Alibaba. These changes are ported from our production connector and reflect official platform behaviors and best practices. We're committed to long-term maintenance and upstream contribution.

We're happy to hop on a quick call, do a live walkthrough, or address any feedback asynchronously — whatever works best for the team. Thanks again for all the work on Hermes! 🙏