Replace tasks banner with new YOLO26 design

[raimbekovm]

summary

in-place replacement of the tasks banner with the new design that adds the semantic task (now 7 tasks: detect, segment, semantic, classify, pose, obb, track). filenames intentionally unchanged so all published touchpoints (github readme en/zh, docs.ultralytics.com/tasks/, pypi, examples/YOLOv8-ONNXRuntime-Rust readme) pick up the new image automatically with no url changes.

files

• docs/ultralytics-yolov8-tasks-banner.avif — 3200×648 @ q80 = 227 kb (vs previous 258 kb)
• im/banner-tasks.png — 1920×388 indexed-palette png = 252 kb (vs previous 226 kb), used by the rust onnxruntime example readme

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🖼️ This PR appears to update a documentation/banner asset in ultralytics/assets, likely refreshing visual content used in Ultralytics docs or promotional materials.

📊 Key Changes

• Updated the generated image file docs/ultralytics-yolov8-tasks-banner.avif.
• No source code, model logic, training behavior, or API changes are shown in the provided diff.
• The change is limited to an asset/media file, suggesting a documentation or branding refresh rather than a functional update.

🎯 Purpose & Impact

• Improves or refreshes the visual presentation of Ultralytics documentation or related pages ✨
• Has no expected impact on package behavior, model performance, or developer workflows ✅
• Low-risk change: users and contributors should not need to update any code or usage patterns 🔧
• May help make documentation more polished, clear, or visually consistent for readers 📚

📋 Skipped 1 file (lock files, generated, images, etc.)

• docs/ultralytics-yolov8-tasks-banner.avif

[UltralyticsAssistant]

👋 Hello @raimbekovm, thank you for submitting a ultralytics/assets 🚀 PR! This is an automated message to help streamline review; an engineer will assist you soon. Please review the checklist below to help ensure a smooth integration:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/assets main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀🎉

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

All 1 changed files are generated/vendored (skipped review)

📋 Skipped 1 file (lock files, generated, images, etc.)

• docs/ultralytics-yolov8-tasks-banner.avif

[glenn-jocher]

Closed in favor of #164