Replace the accidental from-empty migration (which duplicated all 16 prior migrations and would break a fresh `migrate deploy`) with a proper incremental migration adding only the new objects: Post.contentLanguage, the MessageReaction and MutedWord tables, their indexes, and the MessageReaction foreign keys. Verified the DDL against the live schema. NOTE: a fresh full `migrate deploy` still fails on a PRE-EXISTING migration-history drift — 20260514174000_repair_scheduled_posts_schema references "ScheduledPost" which no earlier migration creates. That predates this work; the running stack baselines the schema (applied + migrations marked resolved) to sidestep it. Reconciling the older migration history with schema.prisma is separate follow-up. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>