hermes - 💡(How to fix) Fix DingTalk sampleFile returns "robot 不存在" (robot not found) for internal apps

Bug Description

When attempting to send a file (PDF) via DingTalk REST API using msgKey, the API returns (robot not found). This affects both the group endpoint and the private chat endpoint.

Steps to Reproduce

1. Configure a DingTalk internal app with Stream Mode
2. Upload a file to the OAPI media server () — this works
3. Get robot access token via — this works
4. Send a message with:
   • Endpoint:
   • Headers:
   • Body with and containing mediaId, fileName, fileType, fileSize
5. Response:

Expected Behavior

File should be sent via , similar to how works.

Actual Behavior

• Stream Mode connects and works fine (incoming messages, markdown replies)
• works fine
• fails with robot not found
• The AlibabaCloud SDK () also fails with auth issues — it does not pass by default

Environment

• Hermes: v0.14.0 (2026.5.16)
• dingtalk-stream: 0.24.3
• App type: internal (企业内部应用)
• Client secret: full 64-char (not truncated)
• Stream Mode connection: working
• Media upload (type=file): working

Impact

The gateway code () has and stubbed to return "not supported" errors. If this is a confirmed DingTalk server-side limitation for internal apps, the docs should be updated.