build: package the sidecar without the legacy memory runtime (P1.5, P1.3b)

- Stop building and staging the hive-mind CLI, the coding-agent hook
  packages and the memory MCP server: the hooks, Waggle Room and the
  memory MCP server are hidden in v1 (ADR-0002) and all of them write to
  the legacy .mind files.
- Drop sqlite-vec: nothing loads a SQLite extension since the legacy
  memory engine left. bundle-native-deps no longer copies vec0, the
  resource check no longer probes it, the Tauri shell no longer sets
  WAGGLE_SQLITE_VEC_PATH and install.sh checks plain SQLite.
- Stage bundle roots that npm keeps inside a workspace. mem0ai is not
  hoisted (it stays in packages/memory-mem0), so staging skipped it
  silently and the packaged sidecar would fail on the first memory
  access. Roots that are not installed are now listed in the output.
- js-yaml is a runtime dependency of Puppeteer's config loader since the
  WhatsApp channel moved to whatsapp-web.js (ADR-0005); it leaves the
  resource-check denylist. chromium-bidi stays unstaged: Puppeteer loads
  it only for WebDriver BiDi sessions.
This commit is contained in:
shumeiko.it
2026-10-24 16:37:48 +02:00
parent e435e7da94
commit bbfb3c7f82
6 changed files with 60 additions and 119 deletions

View File

@@ -241,22 +241,19 @@ run_wizard() {
}
# ── Post-install runtime verification (D10) ───────────────────────────────────
# Confirms the native SQLite stack actually loads in the installed tree: opens
# an in-memory better-sqlite3 db and loads sqlite-vec exactly as MindDB does
# (honoring WAGGLE_SQLITE_VEC_PATH). Turns the "does sqlite-vec resolve on this
# platform?" unknown into a visible, actionable check.
# Confirms the native SQLite module actually loads in the installed tree: opens
# an in-memory better-sqlite3 db, as waggle.db and the memory store do. Turns
# the "does the native module load on this platform?" unknown into a visible,
# actionable check.
verify_runtime() {
say "Verifying native SQLite + sqlite-vec"
say "Verifying native SQLite"
local script
script='
const Database = require("better-sqlite3");
const db = new Database(":memory:");
const vecPath = process.env.WAGGLE_SQLITE_VEC_PATH;
if (vecPath) { db.loadExtension(vecPath); }
else { require("sqlite-vec").load(db); }
const row = db.prepare("select vec_version() as v").get();
const row = db.prepare("select sqlite_version() as v").get();
db.close();
console.log("sqlite-vec " + row.v);
console.log("SQLite " + row.v);
'
local errfile
errfile="$(mktemp "${TMPDIR:-/tmp}/waggle-verify.XXXXXX")" \
@@ -268,10 +265,9 @@ verify_runtime() {
fi
local err; err="$(cat "$errfile" 2>/dev/null || true)"
rm -f "$errfile" 2>/dev/null || true
warn "Native SQLite/sqlite-vec check failed:
warn "Native SQLite check failed:
${err}
Remedies:
- Point WAGGLE_SQLITE_VEC_PATH at a sqlite-vec loadable extension for your platform, then re-run.
- Ensure a C/C++ toolchain is installed so better-sqlite3 can build:
$( [ "$OS" = macos ] && echo 'xcode-select --install' || echo 'sudo apt install build-essential python3' )
- Re-run: cd ${INSTALL_DIR} && npm install"