Created a migration script that removes and redefines the coords_3d field
to make it optional (TYPE option<array<number>>) in production database.
This fixes the issue where coords_3d was required but should be NONE
until UMAP coordinates are calculated.
Migration successfully executed on production database.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
