Code Review

MEDIUM Issues

1. README links now depend on a new filename; ensure the asset is actually shipped/published everywhere

File: readme.md:34-34

<strong>💬 Community:</strong> <a href="https://discord.gg/2QAwJn7Egx" target="_blank">Discord (English)</a> | <a href="./resources/wechat_group_5.png" target="_blank">微信 (中文群)</a> | <a href="https://twitter.com/AionUI" target="_blank">Twitter</a>

Problem: This PR renames the QR image from wechat_group4.png to wechat_group_5.png and updates multiple README variants accordingly. That’s fine for GitHub rendering, but it can break in other distribution contexts if resources/ is not included (or is filtered) in any docs publishing pipeline, website sync, or release packaging scripts that previously referenced/whitelisted the old filename. Since the change spans 8 README files, any missed pipeline will result in a broken community link/image.

Fix: Verify/update any docs/site/release asset inclusion rules to include resources/wechat_group_5.png (and remove the old one if explicitly listed). Concretely:

• Search for wechat_group4.png and wechat_group_5.png in CI/docs scripts and website build configs.
• If there is an allowlist (common in static site generators), add resources/wechat_group_5.png.
• Optionally keep a compatibility copy (or symlink where supported) for one release cycle if external references might exist.

Summary

🤖 This review was generated by AI and may contain inaccuracies. Please focus on issues you agree with and feel free to disregard any that seem incorrect. Thank you for your contribution!

Note: The following inputs were truncated due to size limits: file contents (>80K chars).
Please review the omitted portions manually.