Skip to content

Commit d4b51d6

Browse files
committed
docs: v0.10.2 发布准备——README 主题、新闻头条与 CHANGELOG 去重
README 版本表把占位符换成这一版的真实主题:仓库地志从骨架到消费面,含 T1 语义正文、三张消费脸、提纲注入与 opt-in 总闸。 根 README 中英两表各加一条头条。 顺手删掉 CHANGELOG [0.10.2] 里整段重复的 M0 条目——7192f3f 一次提交里同一段被插了两遍。
1 parent 1862696 commit d4b51d6

3 files changed

Lines changed: 3 additions & 8 deletions

File tree

‎README.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@
3131

3232
| 日期 | 版本 | 头条 |
3333
|------|------|------|
34+
| 2026-11-05 | **v0.10.2** | **记忆开始读得懂一个仓库** — 这一版把仓库地志(chorography)从零推到能看能查:读一个 JS/TS 仓库的文件树与 import 图,划分模块、在 `<repo>/.chorography/` 下写出 Markdown 地志页(T0 骨架零模型零网络,`plan.yaml` 做正面控制,`CHORO:HUMAN` 保留区跨重生成逐字节存活),再由 T1 逐模块跑一次 headless 会话补上架构/约定/技术栈/构建四段语义正文与可核验的 claims——生成吃的是宿主已有的模型额度,不要求额外模型商密钥。消费面三张脸同时接上:面板第二座位、三个只读工具、`/choro/*` 读路由,以及每轮开局那一小块标题级提纲注入与只读 `/choro` 命令(**只提示过期、绝不自动重跑**)。`chorographyEnabled` 默认关,wiki 行与记忆行物理隔离、永不进巩固与质量过滤的任何行池。另修 [#573](https://github.com/slow-stack/mneme/issues/573):宽态侧栏的记忆入口落在「更多」行下面,点开更多时被菜单盖住。 |
3435
| 2026-11-03 | **v0.10.1** | **打开记忆详情不再崩掉整个宿主** — 0.10.0 里点开侧边栏任意一条记忆的详情抽屉,渲染进程立刻抛 `ReferenceError: provenance is not defined`,整个宿主跟着重启、进行中的会话被打断,100% 复现([#553](https://github.com/slow-stack/mneme/issues/553))。根因是两个隔了三千多行的组件:`MemoryDrawer` 的归因 effect 与渲染块在读 `provenance` / `setProvenance`,而那句 `useState` 落在了同文件**上一个**组件 `EntityPanel` 里——`EntityPanel` 里那份是纯死代码,整个函数体除声明外对 `provenance` 零引用。这个形状躲得过眼睛(隔三千行、同名 state 看着完全正常)、语法检查(`provenance` 是合法标识符,只是不在作用域里)和原有用例(只读源码字符串,从不执行组件),所以补的不是「锁一个名字」的用例,而是按组件扫「调了 `setXxx(` 却没有声明」。同版带上 v0.10.0 之后合入的图谱锚定层收尾([#24](https://github.com/slow-stack/mneme/issues/24)):Tag 与向量两路起点接线、被动确认补上复核出口 |
3536
| 2026-11-02 | **v0.10.0** | **记忆开始按「哪一轮」算账,而不只是「哪一段」** — 这一版补的都是同一件事:给已经发生的事补上它自己的身份。① **蒸馏有了运行身份**([#512](https://github.com/slow-stack/mneme/issues/512)):此前归因只到「会话区间」——那是**输入**的坐标,不是**运行**的身份,于是「这段原文被重蒸过几次、哪一轮失败了」库里一个字都没存。现在窗口级记 `distill_runs`(含 `ok`/`degraded`/`noop`/`failed`/`aborted` 与 `audit_id`),行级另开 `memory_mints` 记「这条记忆出生自哪一轮巩固」;历史行一律留空**不猜**,模型流失败与解析失败也真记一行。② **溯源补上反方向**([#524](https://github.com/slow-stack/mneme/issues/524)):`GET /memory/provenance?sessionId=<sid>` 让「这个会话蒸出了哪几个窗口」可直接查,此前只能从一条记忆往回找;两个主键互斥,`limit` 越界直接 400 而不静默截断,撞上限带 `truncated: true`。③ **闸门落到单个会话**([#539](https://github.com/slow-stack/mneme/issues/539)):`sessionGateEnabled` 让指定会话与子代理「不进不出」(不注入、不蒸馏,`memory_*` 与 `set_scope_state` 调用一律被拒),其余会话照常——此前能关的只有全局,关插件会连带打死别的会话。子代理判据只认宿主自己的委派标记,`parentSession` **不是**判据:本机 641 个真实会话头逐条核过,用它会把 3 个 fork 出来的主会话判成子代理。④ **防谄媚补到写入面**([#530](https://github.com/slow-stack/mneme/issues/530)):蒸馏与总览的提示词此前对谄媚一字未提,而这两处写出的内容完全不过写入准入——现在补上「立场纪律」四条(不记对用户性格能力的评价、助手推断不写成事实、冲突如实记录、`importance` 只看事实对后续工作的影响面而不因用户满意或情绪抬高)与「叙述纪律」,且排在与时间换算的指令之前。另修 `differentiate` 的正反馈闭环(同一段注记追加到两侧正文 → 向量靠拢 → 下一轮再判重复,实测单条堆 19 段、正文膨胀到 2200+ 字,现在只落账本不改正文,#533)、sleep 冲突相位的输入侧预算与续排(单请求曾打满 163,054 / 163,840 token,分批后隔夜才轮到,现在一轮跑完接着追,#529)、面板「最近巩固」不再把一次整理的回执冒充巩固([#495](https://github.com/slow-stack/mneme/issues/495)),以及面板在 320–519px 上原本根本没有断点([#542](https://github.com/slow-stack/mneme/issues/542))。 |
3637
| 2026-10-30 | **v0.9.5** | **记忆能安全地递出去,也能整包收回来** — 「分享记忆」从一个文件变成有协议的动作([#386](https://github.com/slow-stack/mneme/issues/386)):包只含活跃行,scope 与 home 前缀不进包,命中密钥 / PII 的行整条不进;出包先给报告再给文件,超水位回 413、按类型或标签分批;收包一条不合格整包拒、干跑为默认、按 `share_external_id` 幂等,`undo-share` 整包物删,所以收回后还能再导。来源也第一次可查:`GET /memory/provenance`([#421](https://github.com/slow-stack/mneme/issues/421),@z2Ace0107 实现),409 与 503 分开答「用户关了」与「装配坏了」。另修同标题重复入库(#505)、扫描谎报「没东西可扫」(#515)与未围栏的巩固 prompt(#501)。 |
@@ -314,6 +315,7 @@ dsh-mneme 的机制设计与下列公开研究相互印证(以下引用均逐
314315

315316
| Date | Version | Headline |
316317
|------|---------|----------|
318+
| 2026-11-05 | **v0.10.2** | **Memory learns to read a repository** — this release pushes the repository chorography subsystem from zero to something you can browse and query: it reads a JS/TS repo's file tree and import graph, partitions it into modules, and writes Markdown chorography pages under `<repo>/.chorography/` (the T0 skeleton uses no model and no network, `plan.yaml` is the positive control, and the `CHORO:HUMAN` preserved region survives regeneration byte for byte). A T1 pass then runs one headless session per module to add the four semantic sections — architecture, conventions, stack, build — plus verifiable claims, spending the host's existing model quota rather than asking for another vendor key. Three consumer faces land at once: a second panel seat, three read-only tools, and `/choro/*` read routes, together with a small title-level outline injected each turn and a read-only `/choro` command that **reports staleness and never re-runs by itself**. `chorographyEnabled` is off by default, and wiki rows stay physically separate from memory rows — they never enter any consolidation or quality-filter pool. Also fixes [#573](https://github.com/slow-stack/mneme/issues/573): in the wide sidebar the memory entry landed below the "More" row and was covered when the menu opened. |
317319
| 2026-11-03 | **v0.10.1** | **Opening a memory no longer takes the whole host down** — in 0.10.0, opening the detail drawer of any memory in the sidebar made the renderer throw `ReferenceError: provenance is not defined` immediately, restarting the whole host and cutting off the session in progress, reproducible 100% of the time ([#553](https://github.com/slow-stack/mneme/issues/553)). The cause was two components thousands of lines apart: `MemoryDrawer`'s provenance effect and render block read `provenance` / `setProvenance`, while that `useState` had landed in the **previous** component in the same file, `EntityPanel` — where it was pure dead code, with zero references to `provenance` anywhere else in the function body. That shape slips past the eye (thousands of lines apart, and a same-named state looks perfectly normal), past syntax checks (`provenance` is a valid identifier, just not in scope) and past the existing tests (which read source strings and never run a component), so the regression test does not pin a name — it scans every component for "calls `setXxx(` without declaring it". This release also carries the graph anchoring follow-up merged after 0.10.0 ([#24](https://github.com/slow-stack/mneme/issues/24)): the Tag and vector seed paths are wired up, and passive confirmation gained a review surface |
318320
| 2026-11-02 | **v0.10.0** | **Memory now keeps accounts per run, not only per span** — everything in this release adds one missing thing: an identity for what already happened. ① **Distillation gets a run identity** ([#512](https://github.com/slow-stack/mneme/issues/512)): provenance only reached "which session span", a coordinate of the **input**, never of the **run** — so "how many times was this text re-distilled, and which rounds failed" was nowhere in the store. Window level now records `distill_runs` (`ok` / `degraded` / `noop` / `failed` / `aborted`, plus `audit_id`), row level gets its own `memory_mints` table for "which consolidation run minted this memory"; historical rows stay NULL rather than guessed, and failed rounds are recorded too. ② **Provenance gains the other direction** ([#524](https://github.com/slow-stack/mneme/issues/524)): `GET /memory/provenance?sessionId=<sid>` answers "which windows did this session produce", where before you could only walk back from one memory. The two keys are mutually exclusive, an out-of-range `limit` is a 400 rather than a silent truncation, and hitting the cap sets `truncated: true`. ③ **The gate reaches individual sessions** ([#539](https://github.com/slow-stack/mneme/issues/539)): `sessionGateEnabled` makes chosen sessions and subagents receive nothing and record nothing — no injection, no distillation, and any `memory_*` or `set_scope_state` call is refused — while every other session carries on; previously the only switch was global, and turning the plugin off took other sessions down with it. Subagent detection uses only the host's own delegation markers, never `parentSession`: verified against 641 real session headers on one machine, where it misclassified 3 forked main sessions. ④ **Anti-sycophancy reaches the write side** ([#530](https://github.com/slow-stack/mneme/issues/530)): the distillation and overview prompts said nothing about flattery, and what they write never passes write admission — now they carry a stance discipline (no judging the user's character or ability, assistant inference is not written as fact, conflicts recorded rather than adjudicated, and `importance` driven only by how much a fact affects later work — never raised by user satisfaction or mood) and a narration discipline, placed ahead of the timestamp-conversion instruction. Also fixed: the `differentiate` positive-feedback loop (the same note appended to both sides → vectors converge → judged duplicate again; one row carried 19 notes and grew from 150 to 2200+ characters — the note now lives in a ledger, not in the text, #533), the sleep conflict phase's missing input budget and catch-up (one request filled 163,054 of 163,840 tokens and the rest waited overnight; a clean round now continues immediately, #529), the panel's "last consolidation" card no longer passing an organize receipt off as consolidation ([#495](https://github.com/slow-stack/mneme/issues/495)), and the panel gaining its first breakpoints for 320–519px ([#542](https://github.com/slow-stack/mneme/issues/542)). |
319321
| 2026-10-30 | **v0.9.5** | **Memory can be handed over safely — and taken back** — sharing memory stops being a file and becomes a protocolled action ([#386](https://github.com/slow-stack/mneme/issues/386)): the pack carries active rows only, with no scopes, no home prefixes and no secret/PII rows; shipping returns a report before the file, answers 413 over the watermark and batches by type or tag; receiving rejects the whole pack on one bad row, dry-runs by default, stays idempotent on `share_external_id`, and `undo-share` deletes outright, so a withdrawn pack can be re-imported. Provenance becomes readable too: `GET /memory/provenance` ([#421](https://github.com/slow-stack/mneme/issues/421), by @z2Ace0107), where 409 and 503 answer "the user switched it off" and "the wiring is missing" apart. Plus #505, #515 and the unfenced consolidation prompts (#501). |

‎dsh-mneme/CHANGELOG.md‎

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -66,13 +66,6 @@
6666
- **未到 / 已知为空必须分开**:`sinkStats === null` 时既不画柱也不画图例(否则加载态先画 8 根零高柱子再「长出来」,用户看到的是一次假抖动);`{}` 且三总量全 0 才画空态那句话。`days` 缺省 56(正好 8 周,与热力同窗),钳 1..365,`days=0` 回落缺省而不是钳到 1(与 `llm-audit/stats` 同一套写法,两条曲线对同一个参数给同样的窗口)。
6767
- **两根柱的颜色进图形锁**:柱高差就是结论本身(新增高、巩固矮 = 库在膨胀),掉回浅灰等于把结论擦掉。`.mneme-sinkbar--added` / `--merged` 用 `--mneme-chart-3` / `--mneme-chart-2`,并加进 `test/contrast.test.js` 的 GRAPHICS 表按 3:1 审(不引入任何新字面量色)。
6868
- **验证**:`npm test` 2719 tests / 2718 pass / 0 fail / 1 skipped;`check-sync` 85 文件一致。变异自证六处,全部当场变红:`merged` 退回数行数 → 红「同一 record_id 的两条 receipt 只能算 1 条巩固」;`added` 去掉 imported 排除 → 红;前端把 `if (!sinkStats) return null` 改成 `return []` → 红;删掉 `@container (max-width:960px)` 回落 → 红;把全零空态分支改成 `false` → 红;柱子改回 `--dsw-alias-label-tertiary` → 红(对比度锁 + 语义层锁双杀)。
69-
- **chorography(仓库地志)M0:T0 确定性骨架 + `choro_*` 五表 + `dsh-mneme-choro` CLI**:对标 Qoder 知识库/Repo Wiki 的 mneme 子系统第一批(spec:仓库根 `docs/specs/2026-11-04-chorography-design.md`,实现计划与 P1–P7 决策:仓库根 `docs/plans/2026-11-04-chorography-m0.md`)。读一个 JS/TS 仓库,把文件树 + import 图(ESM 静态/副作用/动态、CJS require、Vue SFC `<script>`、workspace/exports)编译成模块划分与仓库内 `<repo>/.chorography/` 的骨架页(frontmatter 带源文件清单与 git 基线),全程零模型零网络可离线;语义段落(架构/约定/技术栈)由 M2 的 headless 生成轮补。「生成吃宿主模型额度、不要求额外模型商 key」是整条线成立的前提(用户 2026-11-04 拍板),T0 这一步刻意一分钱不花。
70-
71-
- **与记忆行物理隔离是硬边界不是实现细节**:wiki 行永不进 saveWithDedupe / dream / 质量过滤的任何池子——autoDream 的「对核心知识库长期参考价值较低」归档理由一旦够得着 wiki 行,机器生成页就会被巩固流程自己归档掉(`dream-archive-guardrail` 测的正是这个语义)。五张 `choro_*` 表在 store.js 独立成段,`replaceChoroGraph` 整仓替换(重跑幂等 = 单事务删了重插,划分变了不留孤儿行)。
72-
- **保留区机制**:页面里 `CHORO:HUMAN` 标记对包住的内容跨重生成逐字节存活(抽整块、按原相对顺序回填页尾),块外手改不保留是明说语义不是事故。可重建不变量(同状态两次生成逐字节相同)由「`generatedAt` 只进 state.json、失败不推进、下次沿用」撑住——spec §4 的 frontmatter 字段清单与 §9 的字节稳定要求表面冲突,在实现计划 P3 拆掉。渲染层有一条自反雷已排:页面说明行不得出现成对的标记字面量,否则下一轮抽取会把说明行当成保留区(回归锁在 `test/wiki-t0.test.js` 的字节稳定用例里)。
73-
- **plan.yaml 是正面控制**(D7):include/exclude(gitignore 子集:无斜杠模式任意层级、前导斜杠锚定、反选、目录尾斜杠)+ pages 白名单(未列出的模块不建页,模板与笔记原文进页)+ `max_files_per_page`;**未知键整轮拒绝**并报出键名与允许列表——拼错的键等于失效的控制,不能静默忽略。
74-
- **CLI 独立成 bin**(CONTRIBUTING「cli.mjs 零依赖契约」禁止加 import,循 `dsh-mneme-serve` 先例):`dsh-mneme-choro <repo> [--apply] [--db <path>] [--json]`,缺省 dry-run(reclaim 同款纪律);非 git 仓库整轮拒绝(锚点无法核验);写路径断言 `.chorography/` 前缀,契约测试对整仓做树快照——apply 后除 `.chorography/**` 外一个字节都不变、不得出现 `.github/`、`.gitignore`、`AGENTS.md`(openwiki 那两个坏习惯在这里判死)。新增唯一运行时依赖 `yaml`(plan.yaml 是用户手写的配置面,手写子集解析器会静默错解,实现计划 P1)。
75-
- **验证**:39 例新测试(`test/wiki-{plan,scan,partition,store,t0}.test.js`:单元 + 字节稳定 + 红线契约 + 库幂等);V2(import 图在三个真实仓库上的划分质量要人判)待人跑,跑法记在实现计划「待实测回填」。M1(面板 + 只读工具 + 检索)、M2(T1 生成轮)、M3(注入)不在本批次。
7669

7770
- **记忆库从「侧栏 footer 挤一个入口 + 居中浮层」改成宿主原生面板位:侧栏一颗图标进 `sidebar.panellist`,正文落 `main` 整页(参照 dsh-baleen,用户 2026-11-04 提的)**:此前唯一的完整入口是 `sidebar.footer.action`,点开是一个 `createPortal` 到 `document.body` 的居中浮层——它不是宿主的面板,占着屏幕中央却不参与宿主的布局与导航状态,Esc/焦点环/背板点击都得自己实现一遍,而截图里它看起来又很像「一个新窗口」。宿主早就给了成对的座位:`sidebar.panellist`(侧栏面板列表,list 槽)与 `main`(正文区,keyed 槽),侧栏一行的点击由宿主 `PanelRow` 自己调 `layout.selectPanel(id)`,插件只交一颗图标和一片内容。**main 的 `key` 必须与侧栏的 `id` 逐字相同**(两者都取 `dsh-mneme`)——宿主按 `options.key` 在 keyed 槽里找 entry,对不上会抛 `layout.selectPanel: main panel "…" is not registered`;这条不是防御性写作,是宿主 `layout.js` 里真会抛的那一行。
7871

0 commit comments

Comments
 (0)