open-memex 0.7.1-alpha.1 → 0.7.1

package/AGENTS.md

@@ -172,9 +172,9 @@ Context injection happens exactly once per session in `experimental.chat.system.
 
 ## Design constraints — read the frozen design first
 
-`docs/V2-DESIGN.md` is the frozen protocol v0.2 (decisions settled through D73; open questions tracked at the end of the doc). Per its §12:
+`docs/V2-DESIGN.md` is the frozen protocol v0.2 (decisions settled through D74; open questions tracked at the end of the doc). Per its §12:
 AGENTS.md answers "how should AI work here"; the design doc answers "why is it
-built this way" (principles, iron rules, the append-only decision log, currently D1–D73). Before changing
+built this way" (principles, iron rules, the append-only decision log, currently D1–D74). Before changing
 architecture, scope semantics, lifecycle, or the protocol surface (frontmatter
 schema, MCP tools, CLI contract), read the relevant design section — the decision
 log records what was already considered and rejected.

package/CHANGELOG.md

@@ -9,6 +9,8 @@ the `@alpha` tag are development snapshots and are not listed individually.
 
 ## [Unreleased]
 
+## [0.7.1] - 2026-10-04
+
 ## The Node floor is 22.14, because the driver says so (D74)
 
 - **Fixed: every command could die with no output on Node older than 22.14.** `better-sqlite3` 13 (the D72 N-API line) is compiled against Node-API 10, which Node only gained in **22.14.0**. Below that, `require()` succeeds and the first `new Database()` segfaults the process - no message, no stack, exit 139 on macOS/Linux and `0xC0000005` on Windows. Reproduced on win32-x64 with Node 22.12.0; Node 22.23.3 and 24.20.0 are fine, and Node 20 can never work with v13 (upstream [WiseLibs/better-sqlite3#1514](https://github.com/WiseLibs/better-sqlite3/issues/1514), open). open-memex now refuses to load the driver below the floor and says exactly what to do (upgrade Node, or pin `better-sqlite3@^12.11.1`) instead of dying.

package/README.md

@@ -929,6 +929,14 @@ the Copilot instructions. With no `--client` it cleans up every detected
 editor; `--global` limits the cleanup to user-level wiring. Your memories are
 never touched.
 
+**I upgraded Node, or switched versions with nvm. Do I need to reinstall?**
+The package itself doesn't care: its SQLite driver is a Node-API prebuild, so
+it loads on any supported Node (≥ 22.14) with no recompiling, and your
+memories live outside the install. But version managers (nvm and friends)
+keep a separate global package folder per Node version, so after a switch
+`open-memex` may simply be "not found". Run `npm install -g open-memex` once
+under the new Node, then `open-memex doctor` to confirm the driver loads.
+
 ## Project status
 
 open-memex is stable and in daily use; the current stable line is published on

package/README.zh-CN.md

@@ -610,6 +610,9 @@ Windows 上已加载的 DLL 是锁定的：如果 open-memex 的 MCP 服务器
 **VS Code——`init` 跑一次还是每个项目跑？**
 跑一次就够。直接 `open-memex init` 会自动检测 VS Code 并把 MCP 服务器条目写进 VS Code 的用户级 `mcp.json`（Windows 在 `%APPDATA%/Code/User/mcp.json`，macOS 在 `~/Library/Application Support/Code/User/mcp.json`，Linux 在 `~/.config/Code/User/mcp.json`），服务器在每个项目都会启动。项目里有项目级 `.vscode/mcp.json` 时仍以它优先，而该条目保留 `cwd=${workspaceFolder}`，所以项目作用域按窗口各自解析。如果你的 用户级 `mcp.json` 里有注释（VS Code 接受 JSONC），`init` 不动它，会打印确切片段让你手动添加。空文件会被当作空白，直接写入。
 
+**我升级了 Node，或者用 nvm 切换了版本，需要重装 open-memex 吗？**
+包本身不用：它的 SQLite 驱动是 Node-API 预编译的，在任何受支持的 Node（≥ 22.14）上都能直接加载、不需要重新编译；你的记忆也不在安装目录里。但 nvm 这类版本管理器会给每个 Node 版本留一份独立的全局包目录，切换之后 `open-memex` 可能就"找不到"了。在新 Node 下跑一次 `npm install -g open-memex`，再用 `open-memex doctor` 确认驱动能正常加载。
+
 **怎么移除编辑器接线？**
 `open-memex uninstall` 撤销 `init`：移除 MCP 服务器条目、opencode 插件行、Agent Skill 目录，以及 Copilot 指令里的 open-memex 段落。不带 `--client` 时清理所有检测到的编辑器；`--global` 把清理限制在用户级接线。你的记忆永不被动。
 

package/dist/.build-stamp

@@ -1 +1 @@
-e9cc36b1db649d899fdd7298be01622709e4f6d8d4e583764c294bd009cfd0e6
+f8c82ea850a33c28a396d33675b9d22b1b99cf19cef5e828252fb0400b1154e6

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-memex",
-  "version": "0.7.1-alpha.1",
+  "version": "0.7.1",
   "description": "Local-first memory layer and protocol for AI coding agents. Markdown source of truth, SQLite FTS5 index, zero cloud.",
   "type": "module",
   "license": "Apache-2.0",

package/src/runtime-floor.ts

@@ -53,4 +53,4 @@ export function nativeDriverFloorMessage(version: string = process.versions.node
     `&& nvm use ${MIN_NODE_VERSION.split(".").slice(0, 2).join(".")}), or pin the driver ` +
     `down with: npm install better-sqlite3@^12.11.1`
   );
-}
+}