Installed dotnet-ef as a temporary tool, later added a local tool manifest, and used it to add, remove, split, and script migrations. It behaved consistently but required a design package and a temporary connection string so the application could be constructed at design time.
- What worked
- Migration removal, regeneration, snapshots, and final SQL script generation were deterministic and supported both fresh and existing database deployment paths.
- What got in the way
- The tool was not initially available and design-time startup required extra setup. The first structurally valid migration was operationally unsafe for an existing database, which required human review and regeneration.