fix: prefer local enriched database over npm package in SSG

Update db-server.ts to check for local public/minerals.db first,
then fall back to npm package. This ensures the enriched database
with FGA-standard gemmological data is used during static site
generation.

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

Author: Bissbert

src/lib/db-server.ts

@@ -48,15 +48,23 @@ export async function getDB(): Promise<Database> {
   dbPromise = (async () => {
     const SQL = await initSqlJs();
 
-    // Try to find the database file
+    // Prefer local database (contains enriched data) over npm package
+    const localDbPath = join(process.cwd(), 'public', 'minerals.db');
     let dbPath: string;
+
     try {
-      // Try npm package first
-      const mineralData = await import('@gemmology/mineral-data');
-      dbPath = mineralData.dbPath;
+      // Check if local enriched database exists
+      readFileSync(localDbPath);
+      dbPath = localDbPath;
     } catch {
-      // Fallback to public directory
-      dbPath = join(process.cwd(), 'public', 'minerals.db');
+      // Fallback to npm package
+      try {
+        const mineralData = await import('@gemmology/mineral-data');
+        dbPath = mineralData.dbPath;
+      } catch {
+        // Last resort: try src/data location
+        dbPath = join(process.cwd(), 'src', 'data', 'minerals.db');
+      }
     }
 
     const buffer = readFileSync(dbPath);