Albert 12d26c9d14 fix: Make coords_3d optional in schema to support UMAP workflow ...

The proper architecture is:
1. Nodes are created with coords_3d = NONE
2. User manually triggers /api/calculate-graph
3. UMAP calculates 3D coordinates from embeddings
4. Coordinates are updated in batch

Changed coords_3d TYPE from array<number> to option<array<number>>
to allow NONE values. This fixes production error:
"Found NONE for field coords_3d but expected array<number>"

Schema has been deployed to production.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-11-09 19:48:56 +00:00

..

schema.surql

fix: Make coords_3d optional in schema to support UMAP workflow

2025-11-09 19:48:56 +00:00