Task 3 found Prisma's generated migration SQL never emits an explicit ENGINE=... clause, same root cause as the already-accepted collation exception (no schema-level attribute exists). No practical impact: the baseline never executes this SQL against the real DB, and any fresh deploy still gets InnoDB from the server default. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>