@kenz1117/dsh-engram 0.13.4 → 0.13.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +19 -0
- package/README.md +3 -1
- package/i18n/ru.txt +5 -0
- package/lib/client.js +1 -1
- package/lib/client.js.map +1 -1
- package/lib/index.js +241 -4
- package/package.json +2 -1
- package/scripts/check-css-classes.mjs +85 -0
package/CHANGELOG.md
CHANGED
|
@@ -8,6 +8,25 @@
|
|
|
8
8
|
|
|
9
9
|
> **v0.x 阶段的版本约定**:`0.MINOR.PATCH` 里的 `MINOR` 是**功能批次**而不是稳定性刻度——0.7.x 整批是「记忆宫殿信息架构」,0.8.x 整批是「面板重构」,0.9.x 整批是「稳定性与可审计」,0.10.x 整批是「多语言与数据驱动」。同一批次内的 `PATCH` 位通常是修复与加固。
|
|
10
10
|
|
|
11
|
+
## [0.13.6] - 2026-11-06
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- **数据目录不再无视 `DSH_HOME`(#51)**:`dbDir` 默认值此前写死 `~/.dsh/engram`,而宿主把用户数据放在 `$DSH_HOME`(缺省 `~/.dsh`)。把 home 搬到别的盘之后,记忆库、词典与模型缓存仍然静默留在旧盘上——人以为在用新盘,插件读的是旧盘。现在默认值跟着 `$DSH_HOME` 走(契约与宿主的 `@deepseek-ai/dsh-home-paths` 一致:显式值 > `$DSH_HOME` > `~/.dsh`,空白视同未设置);显式写了 `dbDir` 的人不受影响。
|
|
16
|
+
- **旧目录收编,避免库静默分裂**:默认值改跟 home 之后,旧盘上还留着的库会变成「另一处的一份」——插件读新盘,人以为记忆丢了。插件启动时先把 `~/.dsh/engram` 收编过来:同盘直接改名,跨盘先复制到临时目录、逐个文件核对大小再改名并删旧;两边都有库时不自动合并(继续用旧目录并报出两个路径),搬运失败也继续用旧目录——数据看不见比数据待在新盘上更糟。每个结局都写进启动日志。`legacyMigration: conservative` 只报不动。
|
|
17
|
+
- **面板说清数据在哪儿**:「系统 · 存储」同时报出数据目录与宿主数据根,库不在 home 之下时明确提示(此前这件事完全静默,只能去读源码才知道)。
|
|
18
|
+
|
|
19
|
+
## [0.13.5] - 2026-11-06
|
|
20
|
+
|
|
21
|
+
### Fixed
|
|
22
|
+
|
|
23
|
+
- **回归:记忆列表与批量操作条的布局规则被误删**(0.13.0–0.13.4 均受影响)。0.13.0 的「死 CSS 清理」脚本在删单行规则时,越过了本该停下的位置,把中间所有活着的规则一起吃掉——包括 `.item` 的基础布局(列表行不再是复选框 / 正文 / 操作三列网格,而是塌成一列)、`.itemList`、`.batchBar` 的计数与按钮排版,以及 `@keyframes itemIn` / `barUp` 两个动画。结果:选中行只剩一条竖线、批量操作条里的「已选 N 条」字号失控、按钮是默认尺寸,行内操作按钮掉到下一行。全部恢复。
|
|
24
|
+
- 顺带补上两条一直缺失的规则:热力图零级格子(`.heatmapL0`,此前 className 里带着 `undefined`)与导入预览行(`.importRow`)。
|
|
25
|
+
|
|
26
|
+
### Added
|
|
27
|
+
|
|
28
|
+
- **CSS 类覆盖门禁**(`scripts/check-css-classes.mjs`,已接入 CI):CSS Modules 的类名是字符串,类型检查完全看不见——规则被删掉时,编译、单测、lint 全绿,只有真机才发现。这次事故之后补上这道门:凡是代码里 `styles.X` 用到的类,必须在某个客户端样式模块里有对应规则,否则 CI 红灯。门禁同时报出「声明了但没人用」的类(信息项,供后续清理)。
|
|
29
|
+
|
|
11
30
|
## [0.13.4] - 2026-11-06
|
|
12
31
|
|
|
13
32
|
### Fixed
|
package/README.md
CHANGED
|
@@ -203,11 +203,13 @@ DeepSeek Harness 跨会话长期记忆插件 —— 把记忆宫殿的**信息
|
|
|
203
203
|
|
|
204
204
|
可选配置(cordis.yml):
|
|
205
205
|
|
|
206
|
+
> **数据目录跟宿主数据根走**:不写 `dbDir` 时,插件用宿主的数据根 `$DSH_HOME`(缺省 `~/.dsh`)下的 `engram/`——和会话、配置、其它插件的数据放在同一个根里。把 `DSH_HOME` 搬到别的盘,记忆库也跟着搬。若旧目录 `~/.dsh/engram` 里还留着库,插件启动时先把它收编过来(同盘直接改名、跨盘复制后校验再删旧),并把结果写进启动日志;显式写了 `dbDir` 的人不受影响,那一行说了算。面板「系统 · 存储」会同时报出数据目录与宿主数据根,库不在 home 之下时会明确提示。
|
|
207
|
+
|
|
206
208
|
```yaml
|
|
207
209
|
- id: dsh-engram
|
|
208
210
|
name: '@kenz1117/dsh-engram'
|
|
209
211
|
config:
|
|
210
|
-
dbDir: '~/.dsh/engram' #
|
|
212
|
+
dbDir: '~/.dsh/engram' # 分库与模型缓存根目录;不写则默认 $DSH_HOME/engram
|
|
211
213
|
injectProfile: true # 会话开始注入用户画像摘要
|
|
212
214
|
profileTopN: 8 # 注入条数上限(1-64)
|
|
213
215
|
injectTokenBudget: 1024 # 注入 token 预算(128-8192,中文按 1.5 token/字、其余按 4 字符/token 估算,装不下的条目降级为索引行)
|
package/i18n/ru.txt
CHANGED
|
@@ -124,6 +124,11 @@ invalid: jev.timeoutMs must be an integer number of milliseconds between 1000 an
|
|
|
124
124
|
[dsh-engram] The model registry skipped {count} problem line(s): {sample} [dsh-engram] Реестр моделей: пропущено строк с замечаниями — {count}; {sample}
|
|
125
125
|
|
|
126
126
|
// ==== store ====
|
|
127
|
+
[dsh-engram] the data directory moved with the harness home to {to} (was {from}); memories, dictionaries and the model cache moved along. [dsh-engram] каталог данных переехал вместе с домом Harness в {to} (был {from}); воспоминания, словари и кэш моделей переехали тоже.
|
|
128
|
+
[dsh-engram] the data directory was copied to {to} (was {from}; a cross-device move cannot be a rename); the old directory was removed after verification. [dsh-engram] каталог данных скопирован в {to} (был {from}; перенос между дисками не может быть переименованием); старый каталог удалён после проверки.
|
|
129
|
+
[dsh-engram] conservative mode deferred the adoption: the data is still in {from}, and that directory is used for now. [dsh-engram] conservative-режим отложил перенос: данные всё ещё в {from}, пока используется этот каталог.
|
|
130
|
+
[dsh-engram] both locations hold memory databases ({from} and {to}); nothing was merged automatically, the old directory {from} is used for now — confirm and clean up by hand. [dsh-engram] в обоих местах есть базы памяти ({from} и {to}); автоматического слияния не было, пока используется старый каталог {from} — проверьте и уберите лишнее вручную.
|
|
131
|
+
[dsh-engram] the data directory adoption failed ({from} → {to}): {detail}; the old directory is used for now and no data was lost. [dsh-engram] не удалось перенести каталог данных ({from} → {to}): {detail}; пока используется старый каталог, данные не потеряны.
|
|
127
132
|
engram database schema version {found} is newer than the version supported by the plugin ({supported}): upgrade the plugin, or back up and delete the old database file ({path}) Версия schema базы engram {found} выше поддерживаемой плагином ({supported}): обновите плагин либо сделайте резервную копию и удалите старый файл базы ({path})
|
|
128
133
|
engram database schema version {found} cannot be upgraded to {supported} (migration step missing): back up and delete the old database file ({path}), then retry Версию schema базы engram {found} нельзя поднять до {supported} (нет шага миграции): сделайте резервную копию, удалите старый файл базы ({path}) и повторите
|
|
129
134
|
content must not be empty content не может быть пустым
|