feat(qq): qq channel supports directly pushing local multimedia files, such as images and files

[zboya]

📝 Description

Supports directly pushing local multimedia files, such as images and files, to QQ Channels without the need for an external image host.

🗣️ Type of Change

• [x ] ✨ New feature (non-breaking change which adds functionality)

🤖 AI Code Generation

• 🛠️ Mostly AI-generated (AI draft, Human verified/modified)

🔗 Related Issue

📚 Technical Context (Skip for Docs)

• Reference URL: https://bot.q.qq.com/wiki/develop/api-v2/server-inter/message/send-receive/rich-media.html

🧪 Test Environment

• Hardware: mac pro
• OS: darwin
• Model/Provider: glm-5
• Channels: QQ

📸 Evidence (Optional)

Click to view Logs/Screenshots

☑️ Checklist

• [ x] My code/docs follow the style of this project.
• [ x] I have performed a self-review of my own changes.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ zboya
❌ boydzheng

---

boydzheng seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[yinwm]

🔔 PR #1722 has been merged

QQ local file upload support has been implemented in #1722 which was just merged to main.

What's already covered:

• Local file → base64 upload via /files API
• max_base64_file_size_mib config option
• Inbound attachment download and storage
• Two-step upload flow (upload → send with file_info)
• Comprehensive test coverage

Potential follow-ups:

If you'd like to contribute additional features, can rebase onto latest main and focus on:

• File caching (file_info cache to avoid duplicate uploads) - this is in your PR
• Retry mechanism with exponential backoff
• File name preservation

Your media.go implementation has some nice ideas (caching, retries). Would you like to close this PR or rebase and contribute those features as a follow-up?