What
When OrderService and CatalogService were flattened from `Domain.Entities` to `Domain` namespace during VSA refactors, the migration designer + snapshot files were left as-is. At runtime this is invisible — EF's migration runner consults only `__EFMigrationsHistory`, never the snapshot.
But the next `dotnet ef migrations add` against either DbContext would compare the current model (flat `Domain.`) against the snapshot (`Domain.Entities.`) and emit a destructive drop+recreate diff.
When to fix
When the first new migration is needed for either CatalogService or OrderService — regenerate the snapshot or hand-edit the FQN strings. No urgency; both schemas are stable.
Acceptance
What
When OrderService and CatalogService were flattened from `Domain.Entities` to `Domain` namespace during VSA refactors, the migration designer + snapshot files were left as-is. At runtime this is invisible — EF's migration runner consults only `__EFMigrationsHistory`, never the snapshot.
But the next `dotnet ef migrations add` against either DbContext would compare the current model (flat `Domain.`) against the snapshot (`Domain.Entities.`) and emit a destructive drop+recreate diff.
When to fix
When the first new migration is needed for either CatalogService or OrderService — regenerate the snapshot or hand-edit the FQN strings. No urgency; both schemas are stable.
Acceptance