fix(build): resolve nextjs ts errors and force vercel sdk build

- Changed frontend build script to 'npm run build --prefix .. && next build' to ensure the SDK dist folder is generated on Vercel before Next.js compiles
- Exposed loadRegistry() as public in AgentRuntime so Next.js strict TS compiler accepts calls to it when index.d.ts is generated
- Re-synced lockfiles and bumped SDK version to v1.5.2

Author: gitsofaryan

frontend/package.json

@@ -3,7 +3,7 @@
   "version": "0.1.0",
   "scripts": {
     "dev": "next dev",
-    "build": "next build",
+    "build": "npm run build --prefix .. && next build",
     "start": "next start",
     "lint": "eslint"
   },

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arienjain/agent-db",
-  "version": "1.5.1",
+  "version": "1.5.0",
   "description": "Persistent, encrypted, and permission-controlled memory for autonomous AI agents.",
   "main": "dist/index.cjs",
   "module": "dist/index.js",

src/lib/runtime.ts

@@ -620,7 +620,7 @@ export class AgentRuntime {
         await fs.writeFile(indexPath, JSON.stringify(indexer, null, 2), 'utf-8');
     }
 
-    private async loadRegistry(): Promise<Record<string, string>> {
+    public async loadRegistry(): Promise<Record<string, string>> {
         // 1. Try Decentralized Registry first (Device-Agnostic)
         if (this.rootIpnsName) {
             const cid = await StorachaService.resolveIpns(this.rootIpnsName.toString());