Migration history reconciliation: The autonomous-build migration history was corrupted — 20260109185732 dropped 13 tables still in the schema (Account, Advertisement, ScheduledPost, Chat, Organization, Report, …) plus their enums/constraints without recreating them, so a fresh `prisma migrate deploy` failed on the later repair/ALTER migrations (ScheduledPost, Advertisement, AccountType, …). Squashed the 16 broken migrations into a single clean 00000000000000_init generated from the current schema (93 tables, 19 enums, incl. MutedWord/MessageReaction/Post.contentLanguage). Verified: fresh `migrate deploy` applies cleanly on an empty DB; the running DB was re-baselined (resolve --applied init) and the backend boots healthy. context7: Switch the compose service from a broken raw node:20-alpine + read-only-volume + npm-install setup to the package's upstream pnpm Dockerfile (build context = context7 monorepo root), serving StreamableHTTP on container :8080 (host :3100); point aitm-mcp's CONTEXT7_URL at :8080. Now Up/healthy. Result: all 9 compose services healthy (gitgram backend+web, postgres, redis, aitm-api/mcp/website, gitnexus, context7). E2e through containers still 201/200. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>