[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

.github/pull_request_template.md

@@ -1,11 +1,11 @@
 ## 📝 Description of Changes
 
-Hello! 👋 Please provide a detailed description of what your pull request does.  
+Hello! 👋 Please provide a detailed description of what your pull request does.
 Explain the problem you’re solving, the motivation behind your changes, and any context that might help the maintainers understand your work.
 
 For example:
-- What issue or bug does this PR address?  
-- Why is this change important or helpful?  
+- What issue or bug does this PR address?
+- Why is this change important or helpful?
 - Are there any design decisions or trade-offs to note?
 
 Fixes #(issue number) if applicable.
@@ -14,19 +14,19 @@ Fixes #(issue number) if applicable.
 
 ## 🌟 Motivation & Context
 
-Give a little background to help reviewers understand your thought process.  
-This is your chance to explain *why* you approached the problem the way you did.  
+Give a little background to help reviewers understand your thought process.
+This is your chance to explain *why* you approached the problem the way you did.
 
 For example:
-- Did you find a more efficient solution?  
-- Are you adding new functionality that didn’t exist before?  
+- Did you find a more efficient solution?
+- Are you adding new functionality that didn’t exist before?
 - Did you improve documentation, readability, or testing?
 
 ---
 
 ## 📸 Screenshots / Output (if applicable)
 
-If your PR changes visuals, algorithm output, or logs, please add screenshots, gifs, or text samples here.  
+If your PR changes visuals, algorithm output, or logs, please add screenshots, gifs, or text samples here.
 This makes it easier for maintainers to review and understand your work.
 
 ---
@@ -35,34 +35,34 @@ This makes it easier for maintainers to review and understand your work.
 
 Please select one or more options that apply:
 
-- [ ] 🐛 Bug fix – Non-breaking change that fixes an issue  
-- [ ] ✨ New feature – Adds new functionality  
-- [ ] ⚡ Enhancement / Refactor – Improves or optimizes existing code  
-- [ ] 📝 Documentation update – Improves instructions, examples, or guides  
+- [ ] 🐛 Bug fix – Non-breaking change that fixes an issue
+- [ ] ✨ New feature – Adds new functionality
+- [ ] ⚡ Enhancement / Refactor – Improves or optimizes existing code
+- [ ] 📝 Documentation update – Improves instructions, examples, or guides
 
 ---
 
 ## 📋 Checklist
 
 Before submitting your PR, please check off the following:
 
-- [ ] I have read and understood the [CONTRIBUTING.md](CONTRIBUTING.md) guide  
-- [ ] This PR is my own work and not copied from elsewhere  
-- [ ] My code follows the project’s coding style, naming conventions, and best practices  
-- [ ] I have added or updated tests/doctests where necessary  
-- [ ] All automated tests, linting, and formatting pass successfully  
-- [ ] I have added links or references to relevant issues, documentation, or sources  
-- [ ] I have provided screenshots, output, or examples if applicable  
-- [ ] I have explained the motivation and context clearly above  
+- [ ] I have read and understood the [CONTRIBUTING.md](CONTRIBUTING.md) guide
+- [ ] This PR is my own work and not copied from elsewhere
+- [ ] My code follows the project’s coding style, naming conventions, and best practices
+- [ ] I have added or updated tests/doctests where necessary
+- [ ] All automated tests, linting, and formatting pass successfully
+- [ ] I have added links or references to relevant issues, documentation, or sources
+- [ ] I have provided screenshots, output, or examples if applicable
+- [ ] I have explained the motivation and context clearly above
 
 ---
 
 ## 🔗 Related Issues / References
 
-List any related issues, discussions, or external references here.  
+List any related issues, discussions, or external references here.
 Use the GitHub closing keywords if your PR resolves issues automatically (e.g., `Fixes #123`).
 
 ---
 
-💡 **Tip for contributors:**  
+💡 **Tip for contributors:**
 Try to make your PR description as clear as possible. Imagine you’re explaining your changes to someone seeing the project for the first time — this helps maintainers review faster and increases the chances your PR will be merged smoothly.