memory-eternal 0.9.16 → 0.9.17

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://anthropic.com/claude-code/plugin.schema.json",
   "name": "memory-eternal",
-  "version": "0.9.16",
+  "version": "0.9.17",
   "description": "璁板繂鏍稿績锛圡emory Eternal锛夛細鐭ヨ瘑鍗¤嚜鍔ㄦ矇娣€/鍙洖锛岀粺涓€ ~/.dsh/memory-vault锛屼細璇濈粨鏉熻嚜鍔ㄥ叆搴撹繘寰呭鏍搞€?,
   "author": {
     "name": "EternalNight996",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memory-eternal",
-  "version": "0.9.16",
+  "version": "0.9.17",
   "description": "璁板繂鏍稿績锛圡emory Eternal锛夛細鐭ヨ瘑鍗¤嚜鍔ㄦ矇娣€/鍙洖锛岀粺涓€ ~/.dsh/memory-vault锛屼細璇濈粨鏉熻嚜鍔ㄥ叆搴撹繘寰呭鏍搞€?,
   "author": {
     "name": "EternalNight996",

package/.cursor-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "memory-eternal",
-  "version": "0.9.16",
+  "version": "0.9.17",
   "description": "璁板繂鏍稿績锛圡emory Eternal锛夛細鐭ヨ瘑鍗¤嚜鍔ㄦ矇娣€/鍙洖锛岀粺涓€ ~/.dsh/memory-vault锛屼細璇濈粨鏉熻嚜鍔ㄥ叆搴撹繘寰呭鏍搞€?,
   "author": {
     "name": "EternalNight996",

package/README.en.md

@@ -312,6 +312,7 @@ Diagnostics:
 
 | Version | Date | Highlights |
 |---|---|---|
+| **v0.9.17** | 2026-09-30 | **"I updated it but the UI is still old" — fixed for good.** ① The build now injects the plugin version into the client bundle and the settings page shows a "**Page script vX**" chip; ② when the page-script version differs from the on-disk version it says so loudly: "⚠ This page is still running an older script (page v{page} / disk v{disk}): **press Ctrl+F5**"; the running-vs-disk hint now also leads with "refresh first, restart the desktop app / DSH only if the host half is old". Root cause of issue #12 ("saving shows no feedback"): the page was still executing the JS loaded before the update — the host sends `Cache-Control: no-store`, but **an already-open page never reloads its scripts**, so without a refresh you keep seeing the old UI. The standalone web service on `:7999` (an old process started 9/29) was restarted and now reports `loaded=onDisk=latest` |
 | **v0.9.16** | 2026-09-30 | **Fixed config saves silently not persisting (issue #12) + full config coverage.** ① **Save path**: the host `dsh-settings.write()` requires the revision held by the panel to match `describe()` **exactly**; once stale it throws `SettingsConflictError` and the save fails — the plugin now re-reads the latest revision and **retries once** (marked ♻ in the message). ② **Late volatile echo**: after a successful write the patch is overlaid on the local view (reopening the panel shows the new value immediately) and the overlay is dropped once the host snapshot catches up; the host POST now **re-reads after writing** and returns `pending` with an honest note ("written; restart DSH to apply from the config file") when the echo has not landed. ③ **Immediate save feedback** (requested earlier): ⏳ Saving / ✅ Saved / ⚠ error now appears right next to the Save button, including whether a retry or an echo was involved, and the button label no longer wrongly says "Exporting…". ④ **Full config coverage**: seven fields that previously could only be edited by hand are now in the panel — the **master switch `enabled`**, single-vault `vaultDir`, distillation route `captureProvider` / `captureModel`, cooldown `captureCooldownMs`, semantic recall `recallEmbedding` and `sessionBudgetChars`; the host `/config` gained 6 keys and the standalone web `/config` gained 9. ⑤ New **permanent guard tests**: `tests/config-coverage.test.mjs` asserts every Config field is covered by the host API, the standalone web API and the settings panel (missing one turns the suite red), and `tests/settings-save.test.mjs` (5 checks) pins revision retry, overlay fallback and "never swallow errors". `npm test` now runs **121 checks** |
 | **v0.9.15** | 2026-09-29 | **Server-side graph speed-ups only — rendering is identical to v0.9.13.** ① **On-disk graph cache** keyed by fingerprint at `<vault>/memory-eternal-graph-cache.json` (atomic write, invalidated by fingerprint, skipped above 8MB, failures only cost a rebuild): measured cold start **422ms → 11ms** at 596 cards; ② **hashed bigrams + counting-sorted rare-gram index**: `bigramHashSet()` packs each bigram into a 32-bit integer (`Set<number>`; **capture de-duplication still uses the string version, so semantics are unchanged**), and the rare-gram index is built with a counting sort (202 → **54ms**); ③ **MinHash + LSH** candidate generation (48-dim signatures, 24 bands, unioned with the rare-gram index and then **verified exactly**): Jaccard calls 15,148 → 6,797 and the similarity stage 210 → 130ms. Full cold build **600 → 422ms**, edges unchanged from v0.9.13 (tag 2777 / similar 4). **Zero client changes** — no sprites, no static layer, no skeleton degradation (the v0.9.14 client work was reverted and deprecated because it hurt the feel). Adds `lib/minhash.js` + `tests/minhash.test.mjs` (4 checks); `npm test` runs **108 checks** |
 | **v0.9.13** | 2026-09-28 | **Seven fixes from user feedback.** ① **Version tracking**: Plugin info now shows **running (loaded by host) / on disk / npm latest** side by side, with an amber warning when disk is newer ("X is installed on disk but the running process still has Y — restart to apply") plus a "Check for updates" button (server-side npm lookup, 10-minute cache, 4s timeout). ② **Copy failure**: the memory dialog runs inside an iframe without clipboard-write permission, so `navigator.clipboard.writeText` is always rejected — it now tries the Clipboard API, falls back to `document.execCommand('copy')`, and finally shows the text in a read-only box with a Select-all button; the iframe also gets `allow="clipboard-write; clipboard-read"`. ③ **Silent save**: the result now appears right next to the Save button (⏳ Saving… / ✅ Saved / ⚠ error) and the button label changed from the wrong "Exporting…" to "Saving…". ④ **Recycle bin**: restore / purge / empty-all now report success and failure, and the empty state explains itself and disables the buttons. ⑤ **Button feedback everywhere**: the audit centre's approve / reject / delete used to swallow everything in `catch {}`; it now counts successes/failures and reports them (and warns when nothing is selected). ⑥ **Graph zoom jank**: new `src/client/graph-lod.js` — **viewport culling** (off-screen nodes/edges are skipped) + a **label budget** (≤120 nodes draw all; ≤300 draw 160; ≤600 draw 90; more draw 60, prioritising focus, hover, search hits and highest degree) + **text-width caching** + **shadows off for large graphs**. ⑦ Adds `tests/graph-lod.test.mjs` (5 checks); `npm test` now runs **108 checks** |

package/README.md

@@ -336,6 +336,7 @@ curl http://127.0.0.1:7999/memory-eternal/api/web-info    # 独立 web 是否活
 
 | 版本 | 日期 | 关键改动 |
 |---|---|---|
+| **v0.9.17** | 2026-09-30 | **「更新了却还是旧界面」根治**。① 构建期把插件版本注入客户端 bundle，配置页新增「**页面脚本 vX**」徽标；② 当**页面脚本版本 ≠ 磁盘版本**时醒目提示「⚠ 当前页面仍在运行旧版脚本（页面 v{page} / 磁盘 v{disk}）：**按 Ctrl+F5 刷新页面即生效**」；当「运行中（宿主加载）」落后于磁盘时，提示语也改为「先刷新页面，宿主半未更新才需重启桌面版 / DSH」。起因：issue #12「保存配置没有任何反馈」的真实原因之一，就是页面里跑的还是更新前加载的旧 JS —— 宿主已设 `Cache-Control: no-store`，但**已打开的页面不会自动重新加载脚本**，不刷新永远是旧的。另：独立 web 服务（`:7999`，9/29 启动的旧进程）已重启到新版并验证 `loaded=onDisk=latest` |
 | **v0.9.16** | 2026-09-30 | **修复配置保存不生效（issue #12）+ 配置项全覆盖**。① **保存链路**：宿主 `dsh-settings.write()` 要求「面板持有的 revision 与 describe **完全一致**」，revision 一过期就抛 `SettingsConflictError` 导致保存失败 —— 现在遇到冲突会自动取最新 revision **重试一次**（提示里标 ♻）。② **宿主 volatile 回流滞后**：写成功后把改动叠加在本地视图（面板重开立刻是新值），等宿主快照追上再自动摘除；宿主 POST 新增**写入回读校验**，未回流时返回 `pending` 并提示「已写入，重启 DSH 后以配置文件为准」。③ **保存即时反馈**（你此前反馈过）：保存按钮旁直接显示 ⏳ 保存中 / ✅ 已保存 / ⚠ 错误，并标明是否重试/是否回流；按钮文案修正（原来误显示「导出中…」）。④ **配置全覆盖**：补齐 7 个以前只能手改配置文件的字段 —— **总开关 `enabled`**、单库目录 `vaultDir`、蒸馏路由 `captureProvider` / `captureModel`、沉淀冷却 `captureCooldownMs`、语义召回 `recallEmbedding`、会话预算 `sessionBudgetChars`；宿主 `/config` 补 6 项、独立 web `/config` 补 9 项。⑤ 新增**永久守卫测试**：`tests/config-coverage.test.mjs` 保证每个 Config 字段都被「宿主 API / 独立 web API / 配置页」三处覆盖（漏一个就红），`tests/settings-save.test.mjs`（5 项）钉死 revision 重试、回流兜底与「错误不吞」。`npm test` 共 **121 项** |
 | **v0.9.15** | 2026-09-29 | **只带服务器侧图谱提速（渲染与 v0.9.13 完全一致）**。① **建图落盘缓存**：按指纹缓存 nodes+edges 到 `<vault>/memory-eternal-graph-cache.json`（原子写、指纹失效、超 8MB 不缓存、写失败只影响下次重建），596 卡实测冷启动 **422ms → 11ms**；② **bigram 哈希化 + 稀有 gram 计数排序**：`bigramHashSet()` 把 bigram 压成 32 位整数入 `Set<number>`（**写卡去重仍用字符串版，判定语义不变**），稀有倒排改按 df 计数排序（202 → **54ms**）；③ **MinHash + LSH 候选生成**（48 维签名 / 24 band，与稀有倒排取并集后**精确校验**）：jaccard 调用 15,148 → 6,797，相似度段 210 → 130ms。全量冷建图 **600 → 422ms**，边数与 v0.9.13 一致（tag 2777 / similar 4）。**客户端零改动**：不做精灵/静态层/骨架降级（v0.9.14 那三项因影响手感已回退并 deprecated）。新增 `lib/minhash.js` + `tests/minhash.test.mjs`（4 项），`npm test` 共 **108 项** |
 | **v0.9.13** | 2026-09-28 | **按用户反馈修 7 项**。① **版本跟踪**：配置页「插件信息」同时显示**运行中（宿主加载）/ 磁盘安装 / npm 最新**三个版本；磁盘比运行中新时给橙色警告（「磁盘已安装 X，但当前进程仍加载 Y —— 重启后才生效」），并新增「🔄 检查更新」（服务端查 npm，10 分钟缓存 + 4s 超时）。② **复制失败**：记忆弹窗在 iframe 里、默认没有 clipboard-write 权限，`navigator.clipboard.writeText` 必然被拒 —— 现在先试 Clipboard API，失败退 `document.execCommand('copy')`，再失败就把内容摊进只读文本框并给「全选」；iframe 加 `allow="clipboard-write; clipboard-read"`。③ **保存没有提示**：保存结果显示在保存按钮旁（⏳ 保存中… / ✅ 已保存 / ⚠ 错误），文案从错误的「导出中…」改为「保存中…」。④ **回收中心**：恢复 / 彻底删除 / 清空都有成功与失败提示，空库给说明与禁用态。⑤ **通用按键反馈**：审核中心的批准 / 驳回 / 删除原先 `catch{}` 吞掉一切，现逐条统计成功失败并提示；未选卡片也提示。⑥ **图谱缩放卡顿**：新增 `src/client/graph-lod.js` —— **视口剔除**（屏幕外节点/边不画）+ **标签预算**（≤120 全画 / ≤300 画 160 / ≤600 画 90 / 更多画 60，优先焦点、悬停、搜索命中、高度数）+ **文本宽度缓存** + **大图关阴影**。⑦ 新增 `tests/graph-lod.test.mjs`（5 项），`npm test` 共 **108 项** |