open-memex 0.3.0-alpha.3 → 0.3.0

package/AGENTS.md

@@ -34,7 +34,7 @@ node --experimental-strip-types scripts\smoke-pure.ts   # runs pure-logic checks
 node --experimental-strip-types scripts\smoke-mcp.ts    # MCP handshake + tool round-trip (temp dirs, no real data)
 ```
 
-After `npm i -g open-memex@alpha` (or `npm link` from source), the `open-memex` bin is on
+After `npm i -g open-memex` (or `npm link` from source), the `open-memex` bin is on
 PATH: `open-memex mcp` starts the MCP server, `open-memex mcp --print-config <client>`
 prints a client config snippet (client: vscode|cursor|claude|opencode|visualstudio),
 `open-memex init [--client vscode|cursor|opencode|visualstudio] [--instructions personal|project] [--force] [--yes]`

package/README.md

@@ -21,16 +21,15 @@ plus a generic MCP server (VS Code Copilot, Cursor, Claude Code, Visual Studio,
 **npm (recommended):**
 
 ```sh
-npm install -g open-memex@alpha
+npm install -g open-memex
 ```
 
-This installs the `0.3.0-alpha` prerelease channel. (`latest` still points at the older
-`0.1.0` stable.)
+This installs the `0.3.0` stable release.
 
 **No install — run via npx:**
 
 ```sh
-npx -y open-memex@alpha <command>   # e.g. npx -y open-memex@alpha init --client vscode
+npx -y open-memex <command>   # e.g. npx -y open-memex init --client vscode
 ```
 
 **From source** (bleeding edge, `V2-dev-p2` branch):
@@ -42,9 +41,6 @@ npm install
 node --experimental-strip-types src/cli.ts <command>
 ```
 
-> The `0.3.0-alpha` npm publish is cut from this branch — if `npx` still resolves an
-> older alpha, install from source until the publish lands.
-
 #### "`open-memex` is not recognized" — PATH setup
 
 A global `npm install -g` puts the `open-memex` launcher in npm's global bin folder.
@@ -65,6 +61,15 @@ If your terminal can't find it, that folder isn't on your `PATH`:
 3. No admin rights / don't want to touch `PATH`? Use the npx form above — npx
    resolves the package itself and needs no `PATH` changes.
 
+#### "`EBUSY` / `EPERM` on `better_sqlite3.node`" — Windows reinstall
+
+On Windows a loaded DLL is locked: if the open-memex MCP server is running
+(VS Code MCP panel, Cursor, etc.), `npm install -g open-memex` cannot
+replace `better_sqlite3.node` and fails with `EBUSY` / `EPERM`. Stop the MCP
+server first (or quit the editor), then re-run the install. If it still fails,
+delete `node_modules/open-memex` and any `node_modules/.open-memex-*` temp
+folders under your global npm root and install again.
+
 ### Step 2 — One-command setup for your editor
 
 Run from your **project root** (so the project scope resolves to this repo):
@@ -74,7 +79,7 @@ Run from your **project root** (so the project scope resolves to this repo):
 ```sh
 open-memex init --client vscode
 # …or without a global install:
-npx -y open-memex@alpha init --client vscode
+npx -y open-memex init --client vscode
 ```
 
 Writes `.vscode/mcp.json` and user-level Copilot instructions, then reload the
@@ -136,8 +141,8 @@ above works too.
 - Existing config files are **merged, never clobbered** — re-running is safe.
   `--force` overwrites.
 - With no durable `open-memex` on `PATH` (e.g. one-shot npx), `init` writes an
-  `npx -y open-memex@alpha mcp` server command into the config so the setup keeps
-  working. `npm i -g open-memex@alpha` + `open-memex init --force` switches to the
+  `npx -y open-memex mcp` server command into the config so the setup keeps
+  working. `npm i -g open-memex` + `open-memex init --force` switches to the
   faster direct command later.
 
 ### Step 3 — Verify it works
@@ -280,7 +285,7 @@ no host-specific plugin needed. Any MCP client can use open-memex.
 
 ```sh
 open-memex mcp               # after a global install
-npx -y open-memex@alpha mcp  # no install needed
+npx -y open-memex mcp  # no install needed
 ```
 
 The project scope is resolved from the process working directory, so configure the
@@ -293,11 +298,11 @@ server with cwd set to your project root (`init` handles this for you).
 
 ## Roadmap
 
-**`0.3.0-alpha` (this release):** generic MCP server, `open-memex` bin/CLI, one-command
+**`0.3.0` (this release):** generic MCP server, `open-memex` bin/CLI, one-command
 `init` setup, Chinese keyword capture with personal/project routing, `config` /
 `capture --dry-run` / `doctor` helpers, Visual Studio support.
 
-**Coming — `0.3.0-beta`:** team sync — shared memory via git (`propose` / `promote` /
+**Coming — `0.4.0`:** team sync — shared memory via git (`propose` / `promote` /
 `resolve` workflow, in-repo memory dir), 1–2 colleague pilot.
 
 **Coming — `0.3.0` (stable):** org layer — org memory repo, curator convention,

package/README.zh-CN.md

@@ -21,15 +21,15 @@
 **npm（推荐）：**
 
 ```sh
-npm install -g open-memex@alpha
+npm install -g open-memex
 ```
 
-安装的是 `0.3.0-alpha` 预览通道。（`latest` 仍指向旧的 `0.1.0` 稳定版。）
+安装的是 `0.3.0` 正式版。
 
 **免安装——用 npx 直接跑：**
 
 ```sh
-npx -y open-memex@alpha <命令>   # 例如 npx -y open-memex@alpha init --client vscode
+npx -y open-memex <命令>   # 例如 npx -y open-memex init --client vscode
 ```
 
 **从源码安装**（最新开发版，`V2-dev-p2` 分支）：
@@ -41,9 +41,6 @@ npm install
 node --experimental-strip-types src/cli.ts <命令>
 ```
 
-> `0.3.0-alpha` 的 npm 发布从该分支切出——如果 npx 还解析到旧的 alpha 版，
-> 请先用源码安装，等发布落地。
-
 #### 提示 "'open-memex' 不是内部命令"？——PATH 设置
 
 `npm install -g` 会把 `open-memex` 启动器放到 npm 的全局 bin 目录。
@@ -63,6 +60,14 @@ node --experimental-strip-types src/cli.ts <命令>
 3. 没有管理员权限 / 不想动 `PATH`？用上面的 npx 形式——npx 自己解析包，
    不需要改 `PATH`。
 
+#### Windows 重装报 "`EBUSY` / `EPERM`（`better_sqlite3.node`）"
+
+Windows 下被进程加载的 DLL 是锁死的：如果 open-memex MCP server 正在运行
+（VS Code MCP 面板、Cursor 等），`npm install -g open-memex` 替换不了
+`better_sqlite3.node`，就会报 `EBUSY` / `EPERM`。先停掉 MCP server
+（或退出编辑器），再重跑安装。还不行的话，手动删掉全局 npm 目录下的
+`node_modules/open-memex` 和 `node_modules/.open-memex-*` 临时目录，再装。
+
 ### 第二步——给你的编辑器一键配置
 
 在**项目根目录**下运行（这样 project scope 会解析到这个仓库）：
@@ -72,7 +77,7 @@ node --experimental-strip-types src/cli.ts <命令>
 ```sh
 open-memex init --client vscode
 # ……没装全局包的话：
-npx -y open-memex@alpha init --client vscode
+npx -y open-memex init --client vscode
 ```
 
 自动写 `.vscode/mcp.json` 和用户级 Copilot instructions，然后重新加载窗口，
@@ -132,8 +137,8 @@ Visual Studio 也会自动发现 `.vscode/mcp.json` 和 `.cursor/mcp.json`，
 - 已有配置文件会被**合并，不会被覆盖**——重复运行是安全的。
   `--force` 强制覆盖。
 - 如果 `PATH` 上没有可用的 `open-memex`（比如一次性 npx），`init` 会把
-  `npx -y open-memex@alpha mcp` 写进配置，配置照样能用。
-  以后 `npm i -g open-memex@alpha` + `open-memex init --force` 可切换到更快
+  `npx -y open-memex mcp` 写进配置，配置照样能用。
+  以后 `npm i -g open-memex` + `open-memex init --force` 可切换到更快
   的直接调用。
 
 ### 第三步——验证
@@ -280,7 +285,7 @@ CLI 跑在 Node 22 下。从源码 checkout 使用时走内置的实验性 TypeS
 
 ```sh
 open-memex mcp               # 全局安装后
-npx -y open-memex@alpha mcp  # 免安装
+npx -y open-memex mcp  # 免安装
 ```
 
 project scope 从进程工作目录解析，所以配置 server 时 cwd 要指向项目根目录
@@ -292,11 +297,11 @@ project scope 从进程工作目录解析，所以配置 server 时 cwd 要指
 
 ## 路线图（Roadmap）
 
-**`0.3.0-alpha`（本版）：** 通用 MCP server、`open-memex` bin/CLI、
+**`0.3.0`（本版）：** 通用 MCP server、`open-memex` bin/CLI、
 一键 `init` 配置、中文关键词捕获（含 personal/project 路由）、
 `config` / `capture --dry-run` / `doctor` 助手命令、Visual Studio 支持。
 
-**Coming —— `0.3.0-beta`：** 团队同步——用 git 做共享记忆
+**Coming —— `0.4.0`：** 团队同步——用 git 做共享记忆
 （`propose` / `promote` / `resolve` 工作流、仓库内记忆目录），
 找 1–2 个同事做 pilot。
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "open-memex",
-  "version": "0.3.0-alpha.3",
+  "version": "0.3.0",
   "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",