fix(web): externalize ao-core and better-sqlite3 from Next.js bundle (#1944)

* fix(web): externalize ao-core and better-sqlite3 from Next.js bundle

Fixes #1930.

Next.js bundles @aoagents/ao-core (via transpilePackages) and bakes
import.meta.url as the build machine's absolute path into the output.
At runtime on any other machine (especially Windows), createRequire()
receives a non-existent file:// URL and fails.

Adding @aoagents/ao-core and better-sqlite3 to serverExternalPackages
tells Next.js to not bundle these — they're resolved at runtime from
node_modules, so import.meta.url resolves to the actual install path.

This fixes:
- events-db.ts: createRequire(import.meta.url)("better-sqlite3")
- update-cache.ts: createRequire(fileURLToPath(import.meta.url))
- The Windows ERR_INVALID_ARG_VALUE error in the user report

* fix(web): move ao-core from transpilePackages to serverExternalPackages

Next.js errors when a package is in both lists:
  'transpilePackages' conflicts with 'serverExternalPackages'

Remove @aoagents/ao-core from transpilePackages and keep it only
in serverExternalPackages. This prevents webpack from bundling
ao-core and baking import.meta.url as the build machine's path.

packages/web/next.config.js

@@ -9,7 +9,6 @@ const homeDir = os.homedir().replace(/\\/g, "/");
 const nextConfig = {
   outputFileTracingRoot: path.join(__dirname, "../.."),
   transpilePackages: [
-    "@aoagents/ao-core",
     "@aoagents/ao-plugin-agent-claude-code",
     "@aoagents/ao-plugin-agent-codex",
     "@aoagents/ao-plugin-agent-opencode",
@@ -22,6 +21,8 @@ const nextConfig = {
   serverExternalPackages: [
     "yaml",
     "zod",
+    "@aoagents/ao-core",
+    "better-sqlite3",
   ],
   webpack: (config, { isServer }) => {
     if (process.platform === "win32") {