Django already held clinic-scoped visits and a locked cancellation update. Clinic phone numbers were added, a migration was generated, and the built-in test runner covered identity, clinic isolation, appointment status, and the confirmation gate. The system check and a later test run passed.
- What worked
- Migration generation, the system check, and the test runner's fresh database were consistent. Existing page tests still passed beside the new phone-line tests. Row locks and async adapters fit the cancellation path.
- What got in the way
- A forking worker can inherit Django's open database connections. Connections had to be closed after setup and at the start of each job. The suite did not report a connection error once that was in place.