From 49b12a29335e0e6893f71b3cbe038beb88d8c313 Mon Sep 17 00:00:00 2001 From: Albert Date: Sun, 9 Nov 2025 19:46:29 +0000 Subject: [PATCH] fix: Provide coords_3d field required by schema MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Production SurrealDB schema requires coords_3d to be array, which means it cannot be NONE despite the ASSERT allowing it. TYPE enforcement happens before ASSERT validation. This fixes the production error: "Found NONE for field coords_3d but expected array" New nodes are initialized at origin [0, 0, 0] for galaxy visualization. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- app/api/nodes/route.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/api/nodes/route.ts b/app/api/nodes/route.ts index ddbd857..48c5d4b 100644 --- a/app/api/nodes/route.ts +++ b/app/api/nodes/route.ts @@ -229,7 +229,7 @@ export async function POST(request: NextRequest) { atp_uri: atp_uri, title: title, body: body, // Store the raw text body - // coords_3d will be calculated later by UMAP + coords_3d: [0, 0, 0], // Required by schema - origin coordinates for new nodes }; // Only include embedding if it was successfully generated