apply pre-commit hooks to entire repository

Author: harryswift01

.github/CONTRIBUTING.md

@@ -10,7 +10,7 @@ This guide explains how to set up your environment, make changes, and submit the
 
 ## Getting Started
 
-Before contributing, please review the [Developer Guide]().  
+Before contributing, please review the [Developer Guide]().
 It covers REPO-NAME’s architecture, setup instructions, and contribution workflow.
 
 If you’re new to the project, we also recommend:
@@ -23,19 +23,19 @@ If you’re new to the project, we also recommend:
 
 When you’re ready to submit your work:
 
-1. **Push your branch** to GitHub.  
-2. **Open a [pull request](https://help.github.com/articles/using-pull-requests/)** against the `main` branch.  
+1. **Push your branch** to GitHub.
+2. **Open a [pull request](https://help.github.com/articles/using-pull-requests/)** against the `main` branch.
 3. **Fill out the PR template**, including:
-   - A concise summary of what your PR does  
-   - A list of all changes introduced  
-   - Details on how these changes affect the repository (features, tests, documentation, etc.)  
+   - A concise summary of what your PR does
+   - A list of all changes introduced
+   - Details on how these changes affect the repository (features, tests, documentation, etc.)
 4. **Verify before submission**:
-   - All tests pass  
-   - Pre-commit checks succeed  
-   - Documentation is updated where applicable  
+   - All tests pass
+   - Pre-commit checks succeed
+   - Documentation is updated where applicable
 5. **Review process**:
-   - Your PR will be reviewed by the core development team.  
-   - At least **one approval** is required before merging.  
+   - Your PR will be reviewed by the core development team.
+   - At least **one approval** is required before merging.
 
 We aim to provide constructive feedback quickly and appreciate your patience during the review process.
 
@@ -45,12 +45,12 @@ We aim to provide constructive feedback quickly and appreciate your patience dur
 
 Found a bug or have a feature request?
 
-1. **Open a new issue** on GitHub.  
-2. Provide a **clear and descriptive title**.  
+1. **Open a new issue** on GitHub.
+2. Provide a **clear and descriptive title**.
 3. Include:
-   - Steps to reproduce the issue (if applicable)  
-   - Expected vs. actual behavior  
-   - Relevant logs, screenshots, or input files  
+   - Steps to reproduce the issue (if applicable)
+   - Expected vs. actual behavior
+   - Relevant logs, screenshots, or input files
 
 Well-documented issues help us address problems faster and keep REPO-NAME stable and robust.
 

.github/pull_request_template.md

@@ -5,16 +5,16 @@
 <!-- List all the changes introduced in this PR. -->
 ### Change 1 <!-- Rename Change 1 to reflect change title -->:
 - <!-- Bullet point the changes in update 1. -->
--  
+-
 
 ### Change 2 <!-- Rename Change 2 to reflect change title -->:
 - <!-- Bullet point the changes in update 2. -->
--  
+-
 
 ### Change 3 <!-- Rename Change 3 to reflect change title -->:
 - <!-- Bullet point the changes in update 3. -->
--  
+-
 
 ## Impact
 - <!-- Bullet point the expected impact this PR will have on the codebase. -->
--  
+-