Update formatting, headers, and redirects

[pderrenger]

Updates repository maintenance artifacts:

• formats supported source and config files
• applies public AGPL source headers
• formats Python docstrings
• updates links to final redirect destinations

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🛠️ This PR makes small but important documentation and template link fixes across the repository to keep contributor and deployment guidance accurate and up to date.

📊 Key Changes

• 🔗 Updated the Ultralytics Contributing Guide link in:
  • .github/ISSUE_TEMPLATE/bug-report.yml
  • .github/ISSUE_TEMPLATE/feature-request.yml
  • README.md
• 🔐 Updated the Replicate API token link in README.md to point to the current sign-in/token access flow.
• 📄 Corrected the AGPL-3.0 license reference in README.md to use the proper OSI license page URL.

🎯 Purpose & Impact

• ✅ Reduces broken or outdated links in issue templates and documentation.
• 👥 Makes it easier for contributors to find the right Ultralytics contributing instructions when reporting bugs, requesting features, or submitting PRs.
• 🚀 Helps users deploying models to Replicate reach the correct API token page with fewer steps or confusion.
• 📚 Improves documentation reliability and professionalism, even though no code behavior or model functionality changes in this PR.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/replicate 🚀 PR! This is an automated message to help streamline review; an engineer will assist you shortly. Please review the checklist below to support a smooth integration of your documentation updates ✨

• ✅ 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/replicate 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}

Clean documentation-only PR. The changes are consistent, scoped to link/formatting maintenance, and I didn't find any actionable issues in the modified lines.

[UltralyticsAssistant]

🎉 Merged! Huge thanks to @pderrenger for these thoughtful documentation and link fixes, with support from @glenn-jocher.

As Leonardo da Vinci said, “Details make perfection, and perfection is not a detail.” This PR is a great example of that: small updates to contributor guidance, token access, and license references that make the repo clearer, smoother, and more reliable for everyone.

Really appreciate the care here—these polish improvements have a meaningful impact.