yuneng-jiang d4e30a9119 Remove dangerous schema diff force-apply from Prisma migration startup ... The `_resolve_all_migrations` method was generating a diff between the DB and schema.prisma and force-applying it via `prisma db execute`, bypassing migration tracking entirely. This caused schema thrashing during rolling deployments when two versions with different schemas were running. - Remove `_resolve_all_migrations` and its post-deploy "sanity check" call - Replace with `_mark_all_migrations_applied` (marks only, no diff/apply) - P3005 handler now uses `_mark_all_migrations_applied` + `prisma migrate deploy` - P3009 non-idempotent errors now fail fast with actionable error messages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>		2026-03-12 11:03:11 -07:00
..
test_litellm_proxy_extras_utils.py	Remove dangerous schema diff force-apply from Prisma migration startup	2026-03-12 11:03:11 -07:00