docs: add cursor agent instructions and rules for tests and alembic migrations

Generated-by: aiautocommit

Author: iloveitaly

.cursor/rules/alembic-migrations.mdc

@@ -0,0 +1,32 @@
+---
+description:
+globs: migrations/versions/*.py
+alwaysApply: false
+---
+
+## Alembic Migrations
+
+### Data Migrations
+
+For migrations that include data mutation, and not only schema modifications, use this pattern to setup a session:
+
+```python
+from alembic import op
+from sqlmodel import Session
+from activemodel.session_manager import global_session
+from app import log
+
+def run_migration_helper():
+  pass
+
+def upgrade() -> None:
+  session = Session(bind=op.get_bind())
+
+  with global_session(session):
+      run_migration_helper()
+      flip_point_coordinates()
+      backfill_screening_host_data()
+
+  # flush before running any other operations, otherwise not all changes will persist to the transaction
+  session.flush()
+```

.cursor/rules/fix-tests.mdc

@@ -0,0 +1,9 @@
+---
+description:
+globs:
+alwaysApply: false
+---
+
+Focus on all unit + command tests. Make sure they pass and fix errors. If you run into anything very odd stop, and let me know. Mutate test code first and let me know if you think you should update application code.
+
+Then, focus on integration tests in tests/integration. If an integration test fails, run it again just to be sure it wasn't a flakey test (integration tests are not deterministic). If it fails because of a visual error, check the 'tmp/test-results/playwright/' directory for a screenshot relating to the failing test that you can inspect.

.cursor/rules/general.mdc

@@ -37,5 +37,5 @@ session_id = client_secret_id.split("_secret")[0]
 
 ### Agent instructions
 
-- When running python tests, use an already open terminal and the `pytest` binary.
+- Run python tests with `pytest` only. If tests fail because of a configuration or system error, do not attempt to fix and let me know. I will fix it.
 - If you added models, generate a migration with `just migration {add,delete,update}_model_other_description`

.cursor/rules/pytest-tests.mdc

@@ -0,0 +1,11 @@
+---
+description:
+globs: tests/**/*.py
+alwaysApply: false
+---
+## Pytest Tests
+
+- Look to tests/factories.py to generate any required database state
+  - Here's an example of how to create + persist a factory `DistributionFactory.build().save()`
+- Use the `faker` factory to generate emails, etc.
+- Do not mock or patch unless I instruct you to. Test as much of the application stack as possible in each test.