a6ff0036b5
The DingTalk adapter only ever classified incoming messages as text and did not implement FileDownloader, so files sent to the bot were never saved to the channel's configured knowledge base — unlike WeCom, which worked. Users saw the file received and read, but never stored. Parse file/picture msgtypes in both the webhook and stream paths (set MessageTypeFile/Image, FileName, FileKey=downloadCode, robot_code), and implement DownloadFile: exchange the downloadCode for a temporary URL via robot/messageFiles/download, then fetch it. robotCode comes from the callback (webhook) or the app client ID (stream). Pictures get a MsgID-derived name, mirroring the WeCom adapter.