memhouse 0.3.1 → 0.3.2

package/README.md

@@ -42,6 +42,25 @@ install scripts by default, so without the flag those five read nothing and you
 silently ship a partial history. `memhouse discover` and `memhouse doctor` both
 say so when the binding is missing.
 
+If that install fails with `EACCES`, `sudo` is the right answer for only one of the
+two causes, and the thing that tells them apart is **who owns the prefix root** —
+not the path, and not the failing file. The path proves nothing: Homebrew's prefix
+is `/usr/local` on Intel and `/opt/homebrew` on Apple Silicon, and is yours in both
+cases. The failing file proves nothing either: an earlier `sudo npm` leaves
+root-owned files *inside* a prefix that is still yours.
+
+```bash
+ls -ld "$(npm prefix -g)"     # the prefix ROOT — this is the deciding one
+```
+
+- **Prefix root owned by `root`** — a genuinely system-managed Node (distro
+  packages under `/usr`). Re-run with `sudo`.
+- **Prefix root owned by you** — the prefix is yours (Homebrew, fnm, nvm, volta),
+  so whatever root-owned file npm tripped on is a stray from an earlier `sudo npm`.
+  Another `sudo` adds more of them. Repair just that path:
+  `sudo chown -R "$(id -u):$(id -g)" <the path npm named>`. The same applies to the
+  cache (`~/.npm`).
+
 To try it without installing, npx takes the same flag — it has to come before the
 package name:
 

package/editors/zed.js

@@ -81,6 +81,44 @@ function queryDb(sql) {
   }
 }
 
+// Zed's `threads` schema varies by version: `worktree_branch` exists in some builds
+// and not others, and older builds lack `created_at`. Naming a column that is not
+// there fails the WHOLE query with "no such column", which cost every Zed thread on
+// this machine — silently, until the adapter started reporting. So ask the table what
+// it has rather than assuming. Cached: the schema cannot change while we scan.
+let threadColumns = null;
+function getThreadColumns() {
+  if (threadColumns) return threadColumns;
+  if (!fs.existsSync(THREADS_DB)) return new Set();
+  try {
+    const db = new Database(THREADS_DB, { readonly: true });
+    const cols = db.prepare('PRAGMA table_info(threads)').all().map((r) => r.name);
+    db.close();
+    // PRAGMA on a missing or renamed table SUCCEEDS with zero rows rather than
+    // throwing. Left unreported, that would cache an empty set, return no sessions,
+    // and look exactly like an unused Zed install — the same silent whole-adapter
+    // drop this function exists to end. Do not cache it either: the next scan should
+    // look again rather than inherit the verdict.
+    if (cols.length === 0) {
+      adapterErrors.record('zed', new Error('threads table missing or unreadable — incompatible Zed schema'), THREADS_DB);
+      return new Set();
+    }
+    threadColumns = new Set(cols);
+    return threadColumns;
+  } catch (e) {
+    adapterErrors.record('zed', e, THREADS_DB);
+    return new Set();
+  }
+}
+
+// index.js calls this between passes of a long-running `ship --loop`. Without it the
+// column set would be fixed for the life of the process, so a Zed upgrade mid-run
+// would keep querying a column that no longer exists — or keep ignoring one newly
+// added — until someone restarted the shipper.
+function resetCache() {
+  threadColumns = null;
+}
+
 function queryBlob(id) {
   if (!fs.existsSync(THREADS_DB)) return null;
   try {
@@ -103,22 +141,33 @@ function queryBlob(id) {
 const name = 'zed';
 
 function getChats() {
-  const rows = queryDb(
-    'SELECT id, summary, updated_at, data_type, length(data) as data_size, parent_id, worktree_branch FROM threads ORDER BY updated_at DESC'
-  );
+  const cols = getThreadColumns();
+  if (cols.size === 0) return [];
+
+  // Only these are relied on. Anything else is taken when the build provides it.
+  const select = ['id', 'summary', 'updated_at', 'data_type', 'length(data) as data_size', 'parent_id'];
+  const hasBranch = cols.has('worktree_branch');
+  const hasCreated = cols.has('created_at');
+  if (hasBranch) select.push('worktree_branch');
+  if (hasCreated) select.push('created_at');
+
+  const rows = queryDb(`SELECT ${select.join(', ')} FROM threads ORDER BY updated_at DESC`);
 
   return rows.map(row => ({
     source: 'zed',
     composerId: row.id,
     name: row.summary || null,
-    createdAt: row.updated_at ? new Date(row.updated_at).getTime() : null,
+    // created_at when the build has it. Falling back to updated_at is not a
+    // creation time — it just keeps the field non-null on builds that lack it.
+    createdAt: (hasCreated && row.created_at) ? new Date(row.created_at).getTime()
+      : (row.updated_at ? new Date(row.updated_at).getTime() : null),
     lastUpdatedAt: row.updated_at ? new Date(row.updated_at).getTime() : null,
     mode: 'thread',
     folder: null,
     encrypted: false,
     bubbleCount: 0,
     _dataType: row.data_type,
-    _gitBranch: row.worktree_branch,
+    _gitBranch: hasBranch ? row.worktree_branch : null,
   }));
 }
 
@@ -226,4 +275,4 @@ function getMCPServers() {
   return results;
 }
 
-module.exports = { name, labels, getChats, getMessages, getMCPServers };
+module.exports = { name, labels, getChats, getMessages, getMCPServers, resetCache };

package/mem-house/delivery/AGENT-INSTALL.md

@@ -17,6 +17,24 @@ the install script that builds the native binding. Without it those five silentl
 return zero sessions and you ship a partial history. Verify with step 4 —
 `memhouse discover` names any adapter it had to skip.
 
+On `EACCES`, decide by **who owns the prefix root**. Not the path — Homebrew's
+prefix is `/usr/local` on Intel and `/opt/homebrew` on Apple Silicon and is
+user-owned in both. Not the failing file either — an earlier `sudo npm` leaves
+root-owned files inside a prefix that is still the user's, and judging by those
+misreads it as system-managed.
+
+```bash
+ls -ld "$(npm prefix -g)"     # the prefix ROOT decides
+```
+
+Prefix root owned by `root` → a system-managed Node; re-run as
+`sudo npm install -g memhouse --allow-scripts=better-sqlite3`.
+
+Prefix root owned by the current user → the prefix is theirs (Homebrew, fnm, nvm,
+volta), so the root-owned file npm tripped on is a stray from an earlier `sudo npm`
+and another `sudo` adds more. Repair that path instead:
+`sudo chown -R "$(id -u):$(id -g)" <path npm named>` (same for `~/.npm`).
+
 From a checkout instead (contributors): `npm install --no-audit --no-fund` in the
 repo root — its `allowScripts` field already covers the binding — then substitute
 `node bin/memhouse.js` for `memhouse` below.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "memhouse",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "memhouse — agent conversation memory across 17 editors: parse-on-client shippers, a typed ClickHouse store, kernel-agency install, and the agentlytics dashboard",
   "main": "bin/memhouse.js",
   "bin": {