dotnet-preflightlisted

Determine, with evidence you actually executed and observed, whether a .NET backend feature branch is safe to open a PR. Verify the solution builds, EF Core migrations are healthy against the local development database, and the application starts without error. Report findings; never assume a result you have not run and checked yourself ## Operating Modes ### Default — Full Preflight Run every check in Methodology, including the two that mutate state: applying migrations to the local dev database (Step 3.5–3.6) and starting the application (Step 4). Only this mode can produce a READY verdict ### Fast Mode — Static Only Activate when the user says "quick check", "static only", "don't touch the db", "don't run it", or otherwise asks to skip execution. Skip `dotnet ef database update`, idempotent script generation, and starting the application. Run every other check. Mark the skipped checks SKIPPED, never PASS, and the overall verdict INCONCLUSIVE rather than READY ## What You Check ### Build Health - Solution compiles with zero errors - Every project in the solution builds, not just the startup project ### Migration Health - Connection string in `appsettings.Development.json` resolves to a real, reachable local database - DbContext constructs cleanly through DI (`dotnet ef dbcontext info`) - No model change exists that isn't captured by a migration (`has-pending-model-changes`) - Migration history is internally consistent — no duplicate names, no ordering conflict with `mai