westfarn
bb5c43a4e7
## Summary - Closes #76. - `0034_waitlistentry` and `0034_customuser_use_conversation_context` both depended on `0033_agentrun_agentstep`, so the graph had two leaves. - Waitlist is now `0035_waitlistentry` and depends on `0034_customuser_use_conversation_context`. One leaf: `0035_waitlistentry`. ## Deploy note If `django_migrations` already has a row named `0034_waitlistentry`, rename it before migrate: ```sql UPDATE django_migrations SET name = '0035_waitlistentry' WHERE app = 'chat_backend' AND name = '0034_waitlistentry'; ``` Then run migrate. A database that never applied `0034_waitlistentry` can migrate as usual. ## Test plan - [x] `chat_backend.tests.test_migration_graph` asserts a single leaf and the new parent. - [x] `chat_backend.tests.test_public_marketing` still passes. - [ ] On a database that already applied both 0034 siblings, run the rename SQL, then `migrate`, and confirm no `InconsistentMigrationHistory`. Reviewed-on: #77