diff --git a/.github/ISSUE_TEMPLATE/help_wanted.md b/.github/ISSUE_TEMPLATE/help_wanted.md
index 2ee010f2e..939dbba0a 100644
--- a/.github/ISSUE_TEMPLATE/help_wanted.md
+++ b/.github/ISSUE_TEMPLATE/help_wanted.md
@@ -1,10 +1,10 @@
 ---
 name: help wanted 
-about: >
+about: > 
   A template issue for when you're blocked on certain lines of code. 
-  This template has many sections to get you thinking about your problem, you don't need to fill all of them.
+  This template has many sections to get you thinking about your problem, 
+  you don't need to fill all of them. 
 labels: "help wanted"
-
 ---
 
 <!--
diff --git a/.github/ISSUE_TEMPLATE/meeting_agenda.md b/.github/ISSUE_TEMPLATE/meeting_agenda.md
index 0510b2737..f3e0399d1 100644
--- a/.github/ISSUE_TEMPLATE/meeting_agenda.md
+++ b/.github/ISSUE_TEMPLATE/meeting_agenda.md
@@ -1,10 +1,11 @@
 ---
 name: meeting agenda 
 about: A template issue for planning meetings 
-title: "Agenda: __" 
+title: "Agenda: \_\_" 
 labels: agenda
 ---
 
+
 <!-- Make your issue easy to find:
 
   - milestone: any milestones you will be addressing
diff --git a/.github/ISSUE_TEMPLATE/new_challenge.md b/.github/ISSUE_TEMPLATE/new_challenge.md
index eb465585b..856fa5ec1 100644
--- a/.github/ISSUE_TEMPLATE/new_challenge.md
+++ b/.github/ISSUE_TEMPLATE/new_challenge.md
@@ -1,9 +1,8 @@
 ---
 name: new challenge 
-about: >
-  A template issue for describing a new challenge on the project board.
+about: > 
+  A template issue for describing a new challenge on the project board. 
   Place this issue in the TODO column of your group's project board. 
-title: ''
 ---
 
 <!--
diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
index cefe7ca45..2fb0558eb 100644
--- a/.github/ISSUE_TEMPLATE/question.md
+++ b/.github/ISSUE_TEMPLATE/question.md
@@ -1,6 +1,6 @@
 ---
 name: question 
-about: >
+about: > 
   A template issue for topics you'd like to discuss or learn more about. 
   specific topics, general knowledge, it does not even need to be about code. 
   There are no bad questions! 
diff --git a/.github/workflows/ci-checks.yml b/.github/workflows/ci-checks.yml
index d56775453..b3d7b0052 100644
--- a/.github/workflows/ci-checks.yml
+++ b/.github/workflows/ci-checks.yml
@@ -55,9 +55,26 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+      
       - name: python version
         run: python --version
         shell: bash
+      
+      - name: Check for test files
+        id: check_tests
+        run: |
+          test_files=$(find ./solutions/tests -type f -name "test_*.py")
+          if [ -n "$test_files" ]; then
+            echo "Found test files:"
+            echo "$test_files"
+            echo "has_tests=true" >> $GITHUB_OUTPUT
+          else
+            echo "No test files found matching pattern ./solutions/tests/test_*.py"
+            echo "has_tests=false" >> $GITHUB_OUTPUT
+          fi
+        shell: bash
+      
       - name: Python - Run Tests
+        if: steps.check_tests.outputs.has_tests == 'true'
         run: python -m unittest
         shell: bash
diff --git a/.vscode/settings.json b/.vscode/settings.json
index 5a90e202f..bbda5188d 100644
--- a/.vscode/settings.json
+++ b/.vscode/settings.json
@@ -113,5 +113,14 @@
   },
 
   // Enable/disable update table of contents on save
-  "markdown.extension.toc.updateOnSave": false
+  "markdown.extension.toc.updateOnSave": false,
+
+  "[python]": {
+    "editor.defaultFormatter": "charliermarsh.ruff",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.ruff": true,
+      "source.organizeImports.ruff": true
+    }
+  }
 }
diff --git a/collaboration/guide/0_repository_setup.md b/collaboration/guide/0_repository_setup.md
index 4044fe979..aae9cb76e 100644
--- a/collaboration/guide/0_repository_setup.md
+++ b/collaboration/guide/0_repository_setup.md
@@ -6,18 +6,18 @@ take the time to do this correctly at the beginning.
 
 ## Setup and Share a Repository
 
-As a team you will choose the name for your team and select
-someone from your team to be the repo owner. This person will fork this
-repository and configure it for collaboration:
+As a team you will choose the name for your team and select someone from your
+team to be the repo owner. This person will fork this repository and configure
+it for collaboration:
 
 - Public face of your repository
   - Change your
     [repository description](https://stackoverflow.com/questions/7757751/how-do-you-change-a-repository-description-on-github)
   - Add or remove topics from your repository
-  - Update your main README with your group name and an initial overview of your project. (You can change this as much as you want.)
+  - Update your main README with your group name and an initial overview of your
+    project. (You can change this as much as you want.)
 - Under settings in your repository select:
   - _Issues_
-  - _Discussions_
   - _Projects_
   - _Always suggest updating pull request branches_
 - Collaboration Settings
diff --git a/solutions/__init__.py b/solutions/__init__.py
new file mode 100644
index 000000000..8b1378917
--- /dev/null
+++ b/solutions/__init__.py
@@ -0,0 +1 @@
+
diff --git a/solutions/tests/__init__.py b/solutions/tests/__init__.py
new file mode 100644
index 000000000..8b1378917
--- /dev/null
+++ b/solutions/tests/__init__.py
@@ -0,0 +1 @@
+