cursor(rules[dev-loop]): Format, Test, then Typecheck and Lint

why: Reordering development workflow prioritizes code correctness over style conformance. This prevents wasting time fixing linting/typing issues in code that may still need substantial changes based on test results. Ensures developers focus on getting functionality correct first before polishing.

what:
- Restructured development workflow to prioritize formatting and test correctness first
- Moved linting and type checking to occur after initial tests pass
- Added explicit verification of tests after linting/type fixes
- Established clear commit points in the workflow (after initial tests and after linting)
- Added numbered steps for clearer process flow
- Improved section headers and organization for better readability
- Maintained requirement to fix failures at each step before proceeding

refs: Supports improved developer workflow efficiency and reduces unnecessary rework

Author: tony

.cursor/rules/dev-loop.mdc

@@ -3,35 +3,56 @@ description: QA every edit
 globs: *.py
 ---
 
-# First: QA Every edit
+# Development Process
 
-Run these commands between edits:
+## 1. Start with Formatting
 
-Check typings:
+Format your code first:
 
 ```
-uv run mypy
+uv run ruff format .
+```
+
+## 2. Run Tests
+
+Verify that your changes pass the tests:
+
+```
+uv run py.test
+```
+
+## 3. Commit Initial Changes
+
+Make an atomic commit for your changes using conventional commits.
+Use `@git-commits.mdc` for assistance with commit message standards.
+
+## 4. Run Linting and Type Checking
+
+Check and fix linting issues:
+
+```
+uv run ruff check . --fix --show-fixes
 ```
 
-Lint:
+Check typings:
 
 ```
-uv run ruff check . --fix --show-fixes; uv run ruff format .;
+uv run mypy
 ```
 
-Check tests:
+## 5. Verify Tests Again
+
+Ensure tests still pass after linting and type fixes:
 
 ```
 uv run py.test
 ```
 
-Between every edit, rerun:
-- Type checks
-- Lint
-- Tests
+## 6. Final Commit
 
-If there's any failures *due to the edits*, fix them first, then:
+Make a final commit with any linting/typing fixes.
+Use `@git-commits.mdc` for assistance with commit message standards.
 
-# When your edit is complete: Commit it
+## Development Loop Guidelines
 
-Make an atomic commit for the edit, using conventional commits.
+If there are any failures at any step due to your edits, fix them before proceeding to the next step.