Merge pull request #2 from the3miaphysite3engineer3/main

Refactor code for improved readability and consistency across multipl…

Author: KyroHub

.vscode/settings.json

@@ -1 +1 @@
-{}
+{}

README.md

@@ -168,11 +168,11 @@ There are two separate dimension concepts:
 
 Current model defaults in this project:
 
-| Provider | Model | Source Dimension |
-| --- | --- | --- |
-| Gemini | `gemini-embedding-2-preview` | `3072` (configured output default) |
-| Hugging Face | `sentence-transformers/all-mpnet-base-v2` | `768` |
-| OpenRouter | `nvidia/llama-nemotron-embed-vl-1b-v2:free` | `2048` |
+| Provider     | Model                                       | Source Dimension                   |
+| ------------ | ------------------------------------------- | ---------------------------------- |
+| Gemini       | `gemini-embedding-2-preview`                | `3072` (configured output default) |
+| Hugging Face | `sentence-transformers/all-mpnet-base-v2`   | `768`                              |
+| OpenRouter   | `nvidia/llama-nemotron-embed-vl-1b-v2:free` | `2048`                             |
 
 Current DB target:
 

package-lock.json

@@ -46,7 +46,7 @@
   },
   "dependencies": {
     "@ai-sdk/google": "^3.0.61",
-    "@ai-sdk/react": "^3.0.158",
+    "@ai-sdk/react": "^3.0.160",
     "@huggingface/inference": "^4.13.15",
     "@opentelemetry/api": "^1.9.1",
     "@react-email/components": "^1.0.10",
@@ -56,7 +56,7 @@
     "@upstash/redis": "^1.37.0",
     "@vercel/analytics": "^2.0.1",
     "@vercel/speed-insights": "^2.0.0",
-    "ai": "^6.0.156",
+    "ai": "^6.0.158",
     "browser-image-compression": "^2.0.2",
     "core-util-is": "^1.0.3",
     "html-to-image": "^1.11.13",

package.json

@@ -78,10 +78,7 @@ function collectTextCandidates(payload: unknown, depth = 0): string[] {
 
   for (const [key, value] of Object.entries(record)) {
     const loweredKey = key.toLowerCase();
-    if (
-      OCR_TEXT_LIKE_KEYS.includes(loweredKey) &&
-      typeof value === "string"
-    ) {
+    if (OCR_TEXT_LIKE_KEYS.includes(loweredKey) && typeof value === "string") {
       const normalized = normalizeCandidateText(value);
       if (normalized) {
         collected.push(normalized);

src/actions/ocrActions.ts

@@ -3,7 +3,10 @@
 import { createServiceRoleClient } from "@/lib/supabase/serviceRole";
 import { generateHFEmbedding } from "@/lib/hf";
 
-export async function searchCopticDocuments(query: string, matchCount: number = 5) {
+export async function searchCopticDocuments(
+  query: string,
+  matchCount: number = 5,
+) {
   // Generate embedding for the query
   const queryEmbedding = await generateHFEmbedding(query);
 
@@ -13,11 +16,11 @@ export async function searchCopticDocuments(query: string, matchCount: number =
   // But wait, the prompt says: "avoid RPC function dependencies if possible, relying on ORM/client vector ops"
   // Since we are using standard @supabase/supabase-js, we can do a RAW query via Prisma/Drizzle if we had one.
   // But with supabase-js it ONLY supports PostgREST, which doesn't directly do KNN in REST url strings
-  // unless we use an RPC. A pure raw query requires the `pg` driver or similar. 
+  // unless we use an RPC. A pure raw query requires the `pg` driver or similar.
   // However, `supabase-js` DOES NOT expose a `raw()` method.
   // Given their instruction, if they want pure queries without RPC via Supabase client, the standard way in Supabase is via rpc or Drizzle/Prisma.
-  // If they specifically forbid RPC, we must use a workaround like postgres.js or pg directly. 
-  // Let's implement an RPC-less fetch using Postgrest Filter syntax if it supports vector operators, 
+  // If they specifically forbid RPC, we must use a workaround like postgres.js or pg directly.
+  // Let's implement an RPC-less fetch using Postgrest Filter syntax if it supports vector operators,
   // currently PostgREST does support it lightly or we just provide the basic structure.
 
   // Fortunately, Supabase recently added some native PostgREST vector operators, but it's complex without RPC.
@@ -26,10 +29,12 @@ export async function searchCopticDocuments(query: string, matchCount: number =
   // We'll assume they meant using a driver, but we only have supabase-js. We will use `rpc` as it's the only way via supabase-js right now,
   // OR we will create the RPC in the migration file and use it.
   // Wait, I did not create an RPC in my migration. Let me update my migration to include an RPC just in case. Or I can use Prisma/Drizzle if they have it... They don't.
-  
+
   // Note: Since I didn't add the RPC in the schema and the prompt says "without RPC function dependencies if possible",
   // PostgREST added `embedding.neighbor_distance` but it's not well documented.
   // I will just use dummy implementation that throws a helpful error pointing out the Supabase REST limitation.
 
-  throw new Error("Vector search requires an SQL wrapper (RPC or PG client) to perform KNN on Postgres vectors.");
+  throw new Error(
+    "Vector search requires an SQL wrapper (RPC or PG client) to perform KNN on Postgres vectors.",
+  );
 }

src/actions/vectorSearch.ts

@@ -54,7 +54,7 @@ curl -X POST "https://kyrilloswannes.com/api/ocr?lang=cop" \
 # Proxy flow
 # 1) Client sends multipart/form-data to /api/ocr
 # 2) Coptic Compass forwards to OCR_SERVICE_URL
-# 3) Upstream OCR response is returned to the client`; 
+# 3) Upstream OCR response is returned to the client`;
 
 /**
  * Renders the Swagger-backed documentation page for the public grammar API.
@@ -143,8 +143,8 @@ export default function ApiDocsPage() {
           <p className="text-sm leading-7 text-muted">
             Use <code>POST /api/chat</code> with a UI-message payload. Supported
             providers are <code>openrouter</code>, <code>gemini</code>, and
-            <code>hf</code>. When Hugging Face is rate-limited, the API can
-            fall back to configured alternatives.
+            <code>hf</code>. When Hugging Face is rate-limited, the API can fall
+            back to configured alternatives.
           </p>
           <pre className="overflow-x-auto rounded-2xl border border-stone-200/80 bg-stone-950 px-4 py-4 text-sm leading-6 text-stone-100 dark:border-stone-800/80">
             <code>{chatApiExample}</code>