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 useful README link fixes, improving documentation accuracy and reliability for contributors and license readers.

📊 Key Changes

• Updated the Contributing Guide link in README.md to use the corrected docs URL without the trailing slash.
• Fixed the AGPL-3.0 license reference link in README.md to point to the correct Open Source Initiative page.
• No code, features, or package behavior were changed—this is a documentation-only update.

🎯 Purpose & Impact

• ✅ Ensures users reach the correct contribution instructions more reliably.
• 🔗 Improves trust and clarity around licensing by linking to the proper AGPL-3.0 reference.
• 📚 Polishes the project README, making the repository more professional and easier to navigate for new and existing users.
• ⚠️ No runtime impact: this change does not affect application behavior, APIs, or performance.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/source-trace 🚀 PR! This is an automated message to help streamline review, and an engineer will assist you shortly 😊 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/source-trace 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 PR. The README changes are limited to documentation link normalization and a corrected OSI license target, and I don't see any functional or maintainability issues in the diff.

[UltralyticsAssistant]

🎉 Merged — thank you @pderrenger, with contributions from @glenn-jocher, for these thoughtful README fixes.

As Leonardo da Vinci said, “Details make perfection, and perfection is not a detail.” This update is a great example of that: small documentation corrections that improve clarity, trust, and the overall contributor experience without changing runtime behavior.

Really appreciate the care put into keeping the project polished and reliable.