Consolidate CI workflow to use Makefile targets

- Replace direct `pip install -e ".[dev]"` with `make install` in install step
- Remove redundant formatting check and test steps
- Consolidate into single unified `make ${MAKE_TARGET}` call with ARGS support
- Pass `--junitxml=reports/junit.xml` to generate test reports in one pass
- Create reports directory before running tests
- Reduces CI execution time and maintenance surface

🤖 Generated with Claude Code

Co-Authored-By: Claude <noreply@anthropic.com>

Author: elifarley

.github/workflows/test.yml

@@ -56,8 +56,7 @@ jobs:
         # Keep this step hermetic and simple: install editable package with dev extras
         run: |
           python -m pip install --upgrade pip setuptools wheel
-          # Use editable install so `make` targets that call python modules run against current source
-          python -m pip install -e ".[dev]"
+          make install
         # If your project needs additional build steps (e.g. C extensions) add them here.
 
       - name: Show environment (quick debug)
@@ -67,32 +66,17 @@ jobs:
           pip list --format=columns | sed -n '1,200p'
           echo "Make target: ${MAKE_TARGET}"
 
-      - name: Run formatting check (black --check)
-        # split steps so logs are clearer and failures pinpointed
-        run: |
-          set -eo pipefail
-          make format || true
-          # enforce check: black --check to ensure CI fails on unformatted code
-          black --check src tests
-
-      - name: Run static checks & tests via Makefile
+      - name: Run CI pipeline (Makefile)
         # Use MAKE_TARGET env to run the aggregate CI target from your Makefile
         run: |
           set -eo pipefail
+          mkdir -p reports
           # run the Makefile target (defaults to 'ci')
-          make ${MAKE_TARGET}
+          # Pass ARGS to generate junit xml during the test phase
+          make ${MAKE_TARGET} ARGS="--junitxml=reports/junit.xml"
         env:
           MAKE_TARGET: ${{ env.MAKE_TARGET }}
 
-      - name: Run tests again with explicit pytest xml for artifact (optional)
-        # Some repos emit junit xml for test reporting; optional but useful.
-        if: always()
-        run: |
-          set -eo pipefail
-          # create junit xml and coverage xml in addition to html (pytest.ini already requests coverage xml)
-          pytest -q --junitxml=reports/junit.xml || true
-        continue-on-error: false
-
       - name: Upload coverage HTML (artifact)
         if: always()
         uses: actions/upload-artifact@v4