The legacy (non authoritative) path of MigrationSourceManager gets interrupted during stepdown, but the step down process doesn't actually wait for the critical section to get released here. It is theoretically possible for a new primary to step up, recover and resolve the migration, and then launch a new DDL operation that would conflict with the still held in-memory critical section, leading to this invariant violation.