dsh-memoir 0.5.0 → 0.5.2

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/README.en.md CHANGED
@@ -1,265 +1,278 @@
1
- # dsh-memoir
2
-
3
- [![npm version](https://img.shields.io/npm/v/dsh-memoir.svg)](https://www.npmjs.com/package/dsh-memoir)
4
-
5
- [中文](./README.md) · English
6
-
7
- **dsh-memoir is a local project-memory layer for DeepSeek Harness: it persists an agent's work conclusions, lessons learned, and next actions, then carries them across sessions through bounded Hot Memory injection, on-demand ranked recall, and Web GUI management.**
8
-
9
- > Cache-aware local project memory for DeepSeek Harness.
10
-
11
- - **Local-only** — all data stays on your machine (`~/.dsh/dsh-memoir.json` + per-project `PROJECT_MEMORY.md`)
12
- - **Zero external memory service** — no vector database, no embedding API, no cloud memory service
13
- - **Bounded hot-memory injection** — token-budgeted Hot Memory is injected into the system prompt (default 900/1200)
14
- - **Ranked local recall** — inverted index + BM25 local ranked retrieval; `memoir_read` fetches long-tail history on demand
15
- - **Web GUI** — a sidebar "Memory" panel with project/global browsing, relevance-ranked search, Hot Memory Inspector, and Retrieval Diagnostics
16
-
17
- ## Quick Start
18
-
19
- ```bash
20
- # install into the web profile from npm (recommended)
21
- dsh plugin --profile web add dsh-memoir
22
-
23
- # or install latest source from GitHub
24
- dsh plugin --profile web add github:Qinling-Melon-Farmers/dsh-memoir
25
-
26
- # or local development (after cloning)
27
- dsh plugin --profile web add link:/absolute/path/dsh-memoir
28
- ```
29
-
30
- Restart DSH to take effect (`dsh web`), then use it normally:
31
-
32
- ```text
33
- use the Agent as usual
34
- ↓
35
- end of each worked turn: an automatic distill reminder
36
- ↓
37
- memoir_record persists work / lessons / next steps
38
- ↓
39
- future sessions auto-inherit Hot Memory (bounded, ranked, frozen per session)
40
- ↓
41
- need long-tail history? memoir_read (local relevance-ranked recall)
42
- ```
43
-
44
- ## Architecture
45
-
46
- ```text
47
- ~/.dsh/dsh-memoir.json
48
- │
49
- │ SSOT (single source of truth)
50
- ▼
51
- MemoirStore
52
- ┌─────────────┴─────────────┐
53
- │ │
54
- ▼ ▼
55
- PROJECT_MEMORY.md Retrieval Index
56
- human-readable ranked recall
57
- (git-committable) │
58
- │ ▼
59
- │ memoir_read
60
- │ GUI /search
61
- │
62
- ▼
63
- Hot Memory Selector
64
- (token budget)
65
- │
66
- ▼
67
- Session Snapshot
68
- (frozen per session)
69
- │
70
- ▼
71
- System Prompt
72
- ```
73
-
74
- ## Memory Model: Full Memory vs Hot Memory
75
-
76
- **Full Memory (complete history)** — the structured JSON SSOT plus the regenerated `PROJECT_MEMORY.md` projection. Used for: complete history, GUI browsing, git commits, manual inspection, and as the source data for ranked recall.
77
-
78
- **Hot Memory (bounded injection)** — high-value memories selected by the selector within a token budget, injected into the system prompt. Properties: **bounded / ranked / compact / session-frozen**.
79
-
80
- > v0.4+ no longer injects the full PROJECT_MEMORY.md into the model: Hot Memory goes to the prompt, long-tail history goes through ranked recall.
81
-
82
- **Session Snapshot freezing semantics**: one session's injected text is built once and frozen (stable prompt prefix, maximizing prompt-prefix cache hits); the current session does not re-consume memory it just wrote, and a new session rebuilds and sees the latest memory. Since v0.4.2, when there is no unique session identity (session.id / agent.id), freezing is skipped — a cache miss beats wrongly reusing another session's snapshot.
83
-
84
- ## v0.5.0 lifecycle and rc8 compatibility
85
-
86
- - The development and peer-dependency baseline is `@deepseek-ai/dsh-* 0.1.0-rc.8`.
87
- - Store format v3 migrates v2 entries without changing their `id`, content, or timestamp. The first mutation materializes `importance`, `pinned`, `status`, `supersedes`, and `tags`; startup reads do not rewrite old files.
88
- - Retrieval defaults to `active`. Archived and superseded history is retained and can be inspected from the Web panel. Explicit `supersedes` marks its targets as superseded; history is never deleted automatically.
89
- - `PROJECT_MEMORY.md` is a human-readable projection. Only bounded Hot Memory enters the system prompt; the full file is not injected.
90
- - GET routes no longer register browser-supplied paths as active workspaces. Only the trusted system-prompt cwd grants panel write authorization. Lock metadata now includes pid, creation time, and nonce, with conservative reclaim only after 60 seconds and a dead owner.
91
- - `memoir_read(scope: 'all')` uses a deduplicated global ranking so project and global results are not repeated.
92
-
93
- ## Tools
94
-
95
- | Tool | Purpose |
96
- | --- | --- |
97
- | `memoir_record` | write work / lessons / actions / note entries |
98
- | `memoir_read` | local relevance retrieval across project (default) / global / all, with limit and compact/full output shapes |
99
-
100
- `memoir_read`'s query description matches its real behavior: **local relevance retrieval over titles and content — supports Chinese phrases, English keywords, code identifiers, and paths, ordered by relevance**.
101
-
102
- ## Retrieval
103
-
104
- - No embeddings, no vector database, no external memory service
105
- - Tokenization: Chinese 2/3-grams + English words + code/path identifiers
106
- - BM25 (documents keep true term frequency; queries are deduplicated)
107
- - 2.5× title boost, exact-phrase boost, section weight, recency decay
108
- - Separate length normalization for titles and bodies (v0.4.2)
109
- - Epoch-aware LRU query cache with 1-hour time buckets: limit/detail stay out of the cache key, so every output shape shares one ranked result (v0.4.2)
110
- - Query-cache metrics (hits/misses/evictions/hit rate) and Last Query (latency/candidates/returned) observability (v0.4.2)
111
- - Global recall limit is a true global Top-K; output truncation preserves the top-ranked head (v0.4.2)
112
-
113
- Curated-query Top-5 hit rate: 100% (quality gate ≥ 90%, see `test/recall-quality.test.ts`).
114
-
115
- ## GUI
116
-
117
- The v0.4 Project / Global / Search / Add / Delete / Diagnostics architecture is kept; since v0.4.2:
118
-
119
- - **Search unified on RetrievalEngine**: a non-empty query calls `GET /api/dsh-memoir/search` — the same BM25 ranking as the agent's `memoir_read` — results ordered by relevance with scores shown
120
- - **Hot Memory Inspector**: expand to see the Hot Memory that will actually be injected for the current workspace (Actions / Lessons / Recent state) — i.e. "what exactly the next session inherits"
121
- - **Retrieval Diagnostics**: Retrieval Index (docs/terms/epoch), Query Cache (hits/misses/evictions/hit rate/size/capacity), Last Query (latency/returned), Session Snapshot (hash/createdAt/storeRevision)
122
-
123
- ## Screenshots
124
-
125
- **1. Plugin active & overall UI**: the sidebar gains a "Memory" entry (alongside SSH / Task Board, mutually exclusive panels); clicking opens the memory panel in the center column.
126
-
127
- ![Plugin active & overall UI](picture/插件生效和UI效果1.png)
128
-
129
- **2. Project memory**: the current project session's persistent memory grouped into Work Log / Lessons Learned / Action Guide / Notes; each entry shows time, section chip, title, content, and session origin, with search, refresh, and per-entry delete.
130
-
131
- ![Project memory](picture/项目记忆2.png)
132
-
133
- **3. Manually adding memory**: a form to pick a section, a one-line title, and content — written to the same data the agent's `memoir_record` writes; PROJECT_MEMORY.md regenerates automatically after submit.
134
-
135
- ![Manually adding memory](picture/手动添加记忆3.png)
136
-
137
- **4. Global memory management**: memory buckets for all projects (name, path, updated time, count) with cross-project search and per-entry maintenance.
138
-
139
- ![Global memory management](picture/全局记忆管理4.png)
140
-
141
- **5. Ranked search + Hot Memory Inspector + Memory Diagnostics (v0.4.2)**: a typed query triggers RetrievalEngine-ranked recall with a relevance score on each result; at the bottom you can expand the Hot Memory Inspector (what the next session will inherit for the current workspace) and the extended Memory Diagnostics (Retrieval index / Query cache / Last query / Session snapshot).
142
-
143
- ![Ranked search with Hot Memory Inspector and Memory Diagnostics](picture/hot%20memory预览与记忆诊断5.png)
144
-
145
- ## Storage & Privacy
146
-
147
- ```text
148
- ~/.dsh/dsh-memoir.json ← structured JSON (single source of truth / SSOT)
149
- <workspace>/PROJECT_MEMORY.md ← human-readable projection regenerated from the JSON (git-friendly)
150
-
151
- No cloud memory DB · No embedding API · No vector DB
152
- ```
153
-
154
- JSON is the source of truth and Markdown is the generated projection: the panel, the tools, and the agent write the same data. Since v0.4.2 the panel write API is also workspace-authorized — an absolute path submitted by the browser is not authorization by itself; only the current active cwd or an existing store project can be written to.
155
-
156
- ## Configuration
157
-
158
- Add a `config` block on the plugin row in `cordis.patch.yml` (all optional; defaults shown):
159
-
160
- ```yaml
161
- - insert:
162
- - id: memoir
163
- name: dsh-memoir
164
- config:
165
- enabled: true # master switch (tools, routes, prompt section)
166
- announceToAgent: true # system-prompt announcement section
167
- autoDistill: true # auto distill reminder after each worked turn
168
- hotMemoryTokens: 900 # Hot Memory target tokens
169
- hotMemoryMaxTokens: 1200 # Hot Memory hard ceiling (never exceeded)
170
- readDefaultLimit: 8 # memoir_read default result count
171
- readMaxLimit: 30 # memoir_read maximum result count
172
- sessionSnapshotMax: 128 # per-session snapshot LRU cap
173
- queryCacheSize: 128 # ranked-query LRU cache size
174
- ```
175
-
176
- ## Design Trade-offs
177
-
178
- - **Bounded vs full injection**: v0.3 injected the full history into the prompt and it kept growing; v0.4+ injects only budgeted Hot Memory, with long-tail history recalled on demand. Token benchmarks below.
179
- - **Frozen vs fresh**: within a session the injected text is frozen to gain prompt-prefix cache hits; without a unique session identity it is not frozen (v0.4.2), so new sessions always see new memory.
180
- - **Hot Memory quota**: Recent state (newest work, 1–3 entries) is guaranteed a floor, actions/lessons fill by ranking, and work only appears in Recent state — never injected twice (v0.4.2).
181
- - **Multi-process safety**: store record/remove runs inside a cross-process critical section on `~/.dsh/dsh-memoir.lock` (exclusive O_EXCL creation with timeout); the section force-reloads from disk before mutating, so two interleaved DSH processes lose no updates (v0.4.2).
182
- - **Windows paths**: canonical keys are fully lowercased (`C:\A` / `c:\a\` / `C:/A` share one bucket) while display paths keep the original casing (v0.4.2).
183
- - **GUI and Agent share one engine**: panel search and `memoir_read` use the same RetrievalEngine instead of separate filter logic (v0.4.2).
184
-
185
- ## Use Cases
186
-
187
- | Scenario | How to use it |
188
- | --- | --- |
189
- | Recurring environment pitfalls (encoding / escaping / paths / permissions) | record a `lessons` entry with copy-pasteable fix commands |
190
- | Project rules and conventions (no emoji, run tests before release, branch policy) | record as `actions`, auto-injected for whoever takes over |
191
- | Root cause of a hard-to-find bug | record as `lessons` / `work` to avoid re-investigation |
192
- | Fixed deployment/release checklist | record as `actions`; new sessions follow it |
193
- | Reuse experience across projects | global tab or `memoir_read(scope: 'global', query: ...)` |
194
-
195
- Typical example: after solving "console Chinese mojibake" the first time, record the diagnosis and fix commands as a `lessons` entry (e.g. `chcp 65001 first … always write UTF-8 without BOM`); every new session in this project then inherits the lesson automatically instead of re-debugging, and cross-project global search hits it too. The memory plugin distills "root cause + fix command" into project knowledge — it does not fix the terminal's own encoding defects.
196
-
197
- ## Comparison
198
-
199
- | Project | Primary focus |
200
- | --- | --- |
201
- | dsh-memory | citation / source-traceable reference memory |
202
- | dsh-mnemon | a heavier long-term memory system |
203
- | distill | distilling sessions into skills |
204
- | **dsh-memoir** | **lightweight project workflow memory: local, bounded injection, ranked recall** |
205
-
206
- Each plugin has its own focus — pick per need; no "which is stronger" narrative.
207
-
208
- ## Development / Benchmark / Tests
209
-
210
- ```bash
211
- pnpm install # install devDeps (typescript, esbuild, @deepseek-ai/* type packages)
212
- pnpm run build # tsc builds the host + esbuild builds the client bundle
213
- pnpm run typecheck # full type check (src + test)
214
- pnpm test # 131 tests: store (incl. multi-process lock) / snapshot / selector / retrieval / tools / routes / auto-distill / integration / client pure logic / bundle protocol & purity
215
- npm run bench # benchmark (100/1k/10k/100k entries); results written to bench/report.md
216
- ```
217
-
218
- Quality gates: **Top-5 recall ≥ 90% · Hot Memory ≤ configured hardMax · same-session prompt-prefix stability · global recall ≤ limit · zero lost updates across processes**.
219
-
220
- v0.4.2 benchmark summary (node v22.23.2, budget 900/1200 tokens; full report in `bench/report.md`. Methodology fixed: uncached queries measure `search()` directly; cached queries warm the same query first, then time it):
221
-
222
- | Entries | Cold load | Warm read | Hot Memory build | Index build | Uncached query | Cached query | Cache hit rate | Full markdown tokens | Injected tokens | Reduction |
223
- |---|---|---|---|---|---|---|---|---|---|---|
224
- | 100 | 1.3 ms | 2.22 µs | 0.54 ms | 2.9 ms | 0.224 ms | 2.87 µs | 50.0% | 3870 | 902 | 76.7% |
225
- | 1,000 | 1.6 ms | 0.40 µs | 0.70 ms | 15.0 ms | 1.419 ms | 1.45 µs | 50.0% | 38182 | 916 | 97.6% |
226
- | 10,000 | 25.3 ms | 0.42 µs | 2.60 ms | 142.9 ms | 11.889 ms | 1.14 µs | 50.0% | 385807 | 902 | 99.8% |
227
- | 100,000 | 158.2 ms | 0.42 µs | 31.97 ms | 2238.7 ms | 153.551 ms | 1.15 µs | 50.0% | 3907057 | 917 | 100.0% |
228
-
229
- ## Implementation
230
-
231
- - **Full-stack TypeScript**: `src/host/*.ts` (store / tools / retrieval / selector / snapshot / routes / autodistill / index — tsc emits `lib/*.js`) + `src/client/*.ts(x)` (esbuild emits the `lib/client.js` closure-factory bundle).
232
- - **Two-sided plugin**: the host half registers the agent tools, `/api/dsh-memoir` routes, the `agent/turn-stopping` auto-distill listener, and the per-project system-prompt injection section; the client half renders the panel. Runtime deps are official NPM SDK packages only.
233
- - Mounted via the `dsh.bundle.patch` manifest (`insert` row in `cordis.patch.yml`); no DSH source changes.
234
- - Auto-distill safety boundaries: top-level sessions only (subagents / nested delegations skipped), turns with tool activity that haven't recorded yet, aborted turns skipped, at most one steer per turn.
235
-
236
- ## Contributing
237
-
238
- PRs and issues are managed with templates and automation:
239
-
240
- - [CONTRIBUTING.md](CONTRIBUTING.md) — PR scope, commit conventions and checklist;
241
- - [ISSUE_TRIAGE.md](ISSUE_TRIAGE.md) — issue labels, classification and closing criteria;
242
- - `.github/ISSUE_TEMPLATE` — bug / request templates; `.github/pull_request_template.md` — PR template.
243
-
244
- Bug reports must include screenshot / log evidence, a smoke test, code references and a patch. New features and documentation-only PRs must first be discussed in an issue.
245
-
246
- ## Release
247
-
248
- Version releases run automatically in `.github/workflows/publish.yml` when a `v*` tag is pushed: install deps, verify the tag matches the `package.json` version, run typecheck/test, then publish to npm. Configure either of these auth options in the repo:
249
-
250
- - npm Trusted Publishing: GitHub repo `Qinling-Melon-Farmers/dsh-memoir`, workflow `publish.yml`
251
- - GitHub Actions secret `NPM_TOKEN`: a granular token with publish rights and 2FA bypass allowed
252
-
253
- Publishing a patch release:
254
-
255
- ```bash
256
- npm version patch
257
- git push
258
- git push origin vX.Y.Z # use the actual version printed by npm version
259
- ```
260
-
261
- `npm version patch` updates `package.json`, creates the version commit and the tag; no manual `git tag` or local `npm publish` needed.
262
-
263
- ## License
264
-
265
- Apache-2.0
1
+ # dsh-memoir
2
+
3
+ [![npm version](https://img.shields.io/npm/v/dsh-memoir.svg)](https://www.npmjs.com/package/dsh-memoir)
4
+
5
+ [中文](./README.md) · English · [Changelog](./CHANGELOG.md) · [GitHub Releases](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases)
6
+
7
+ **dsh-memoir is a local project-memory layer for DeepSeek Harness: it persists an agent's work conclusions, lessons learned, and next actions, then carries them across sessions through bounded Hot Memory injection, on-demand ranked recall, and Web GUI management.**
8
+
9
+ > Cache-aware local project memory for DeepSeek Harness.
10
+
11
+ - **Local-only** — all data stays on your machine (`~/.dsh/dsh-memoir.json` + per-project `PROJECT_MEMORY.md`)
12
+ - **Zero external memory service** — no vector database, no embedding API, no cloud memory service
13
+ - **Bounded hot-memory injection** — token-budgeted Hot Memory is injected into the system prompt (default 900/1200)
14
+ - **Ranked local recall** — inverted index + BM25 local ranked retrieval; `memoir_read` fetches long-tail history on demand
15
+ - **Web GUI** — a sidebar "Memory" panel with project/global browsing, relevance-ranked search, Hot Memory Inspector, and Retrieval Diagnostics
16
+
17
+ ## Quick Start
18
+
19
+ ```bash
20
+ # install into the web profile from npm (recommended)
21
+ dsh plugin --profile web add dsh-memoir
22
+
23
+ # or install latest source from GitHub
24
+ dsh plugin --profile web add github:Qinling-Melon-Farmers/dsh-memoir
25
+
26
+ # or local development (after cloning)
27
+ dsh plugin --profile web add link:/absolute/path/dsh-memoir
28
+ ```
29
+
30
+ Restart DSH to take effect (`dsh web`), then use it normally:
31
+
32
+ ```text
33
+ use the Agent as usual
34
+ ↓
35
+ end of each worked turn: an automatic distill reminder
36
+ ↓
37
+ memoir_record persists work / lessons / next steps
38
+ ↓
39
+ future sessions auto-inherit Hot Memory (bounded, ranked, frozen per session)
40
+ ↓
41
+ need long-tail history? memoir_read (local relevance-ranked recall)
42
+ ```
43
+
44
+ ## Architecture
45
+
46
+ ```text
47
+ ~/.dsh/dsh-memoir.json
48
+ │
49
+ │ SSOT (single source of truth)
50
+ ▼
51
+ MemoirStore
52
+ ┌─────────────┴─────────────┐
53
+ │ │
54
+ ▼ ▼
55
+ PROJECT_MEMORY.md Retrieval Index
56
+ human-readable ranked recall
57
+ (git-committable) │
58
+ │ ▼
59
+ │ memoir_read
60
+ │ GUI /search
61
+ │
62
+ ▼
63
+ Hot Memory Selector
64
+ (token budget)
65
+ │
66
+ ▼
67
+ Session Snapshot
68
+ (frozen per session)
69
+ │
70
+ ▼
71
+ System Prompt
72
+ ```
73
+
74
+ ## Memory Model: Full Memory vs Hot Memory
75
+
76
+ **Full Memory (complete history)** — the structured JSON SSOT plus the regenerated `PROJECT_MEMORY.md` projection. Used for: complete history, GUI browsing, git commits, manual inspection, and as the source data for ranked recall.
77
+
78
+ **Hot Memory (bounded injection)** — high-value memories selected by the selector within a token budget, injected into the system prompt. Properties: **bounded / ranked / compact / session-frozen**.
79
+
80
+ > v0.4+ no longer injects the full PROJECT_MEMORY.md into the model: Hot Memory goes to the prompt, long-tail history goes through ranked recall.
81
+
82
+ **Session Snapshot freezing semantics**: one session's injected text is built once and frozen (stable prompt prefix, maximizing prompt-prefix cache hits); the current session does not re-consume memory it just wrote, and a new session rebuilds and sees the latest memory. Since v0.4.2, when there is no unique session identity (session.id / agent.id), freezing is skipped — a cache miss beats wrongly reusing another session's snapshot.
83
+
84
+ ## v0.5.2 configurable auto-distill and rc2 compatibility
85
+
86
+ - The development and peer-dependency baseline is `@deepseek-ai/dsh-* 0.1.1-rc.2`.
87
+ - Auto-distill now supports per-agent worked-turn intervals, time cooldowns, and tool-call thresholds; defaults `1 / 0 / 1` preserve prior behavior.
88
+ - Store format v3 migrates v2 entries without changing their `id`, content, or timestamp. The first mutation materializes `importance`, `pinned`, `status`, `supersedes`, and `tags`; startup reads do not rewrite old files.
89
+ - Retrieval defaults to `active`. Archived and superseded history is retained and can be inspected from the Web panel. Explicit `supersedes` marks its targets as superseded; history is never deleted automatically.
90
+ - Agents can use `memoir_update` to edit an entry's section, title, content, and lifecycle in place; the Web panel also supports editing, pinning, marking superseded, archiving, and restoring.
91
+ - `PROJECT_MEMORY.md` is a human-readable projection. Only bounded Hot Memory enters the system prompt; the full file is not injected.
92
+ - GET routes no longer register browser-supplied paths as active workspaces. Only the trusted system-prompt cwd grants panel write authorization. Lock metadata now includes pid, creation time, and nonce, with conservative reclaim only after 60 seconds and a dead owner.
93
+ - `memoir_read(scope: 'all')` uses a deduplicated global ranking so project and global results are not repeated.
94
+
95
+ ## Tools
96
+
97
+ | Tool | Purpose |
98
+ | --- | --- |
99
+ | `memoir_record` | write work / lessons / actions / note entries |
100
+ | `memoir_update` | edit an existing entry while preserving its id and creation time; update content, tags, lifecycle, or explicitly supersede history |
101
+ | `memoir_read` | local relevance retrieval across project (default) / global / all, with limit and compact/full output shapes |
102
+
103
+ `memoir_read`'s query description matches its real behavior: **local relevance retrieval over titles and content — supports Chinese phrases, English keywords, code identifiers, and paths, ordered by relevance**.
104
+
105
+ ## Retrieval
106
+
107
+ - No embeddings, no vector database, no external memory service
108
+ - Tokenization: Chinese 2/3-grams + English words + code/path identifiers
109
+ - BM25 (documents keep true term frequency; queries are deduplicated)
110
+ - 2.5× title boost, exact-phrase boost, section weight, recency decay
111
+ - Separate length normalization for titles and bodies (v0.4.2)
112
+ - Epoch-aware LRU query cache with 1-hour time buckets: limit/detail stay out of the cache key, so every output shape shares one ranked result (v0.4.2)
113
+ - Query-cache metrics (hits/misses/evictions/hit rate) and Last Query (latency/candidates/returned) observability (v0.4.2)
114
+ - Global recall limit is a true global Top-K; output truncation preserves the top-ranked head (v0.4.2)
115
+
116
+ Curated-query Top-5 hit rate: 100% (quality gate ≥ 90%, see `test/recall-quality.test.ts`).
117
+
118
+ ## GUI
119
+
120
+ The v0.4 Project / Global / Search / Add / Delete / Diagnostics architecture is kept; since v0.4.2:
121
+
122
+ - **Search unified on RetrievalEngine**: a non-empty query calls `GET /api/dsh-memoir/search` — the same BM25 ranking as the agent's `memoir_read` — results ordered by relevance with scores shown
123
+ - **Hot Memory Inspector**: expand to see the Hot Memory that will actually be injected for the current workspace (Actions / Lessons / Recent state) — i.e. "what exactly the next session inherits"
124
+ - **Retrieval Diagnostics**: Retrieval Index (docs/terms/epoch), Query Cache (hits/misses/evictions/hit rate/size/capacity), Last Query (latency/returned), Session Snapshot (hash/createdAt/storeRevision)
125
+
126
+ ## Screenshots
127
+
128
+ **1. Plugin active & overall UI**: the sidebar gains a "Memory" entry (alongside SSH / Task Board, mutually exclusive panels); clicking opens the memory panel in the center column.
129
+
130
+ ![Plugin active & overall UI](picture/插件生效和UI效果1.png)
131
+
132
+ **2. Project memory**: the current project session's persistent memory grouped into Work Log / Lessons Learned / Action Guide / Notes; each entry shows time, section chip, title, content, and session origin, with search, refresh, and per-entry delete.
133
+
134
+ ![Project memory](picture/项目记忆2.png)
135
+
136
+ **3. Manually adding memory**: a form to pick a section, a one-line title, and content — written to the same data the agent's `memoir_record` writes; PROJECT_MEMORY.md regenerates automatically after submit.
137
+
138
+ ![Manually adding memory](picture/手动添加记忆3.png)
139
+
140
+ **4. Global memory management**: memory buckets for all projects (name, path, updated time, count) with cross-project search and per-entry maintenance.
141
+
142
+ ![Global memory management](picture/全局记忆管理4.png)
143
+
144
+ **5. Ranked search + Hot Memory Inspector + Memory Diagnostics (v0.4.2)**: a typed query triggers RetrievalEngine-ranked recall with a relevance score on each result; at the bottom you can expand the Hot Memory Inspector (what the next session will inherit for the current workspace) and the extended Memory Diagnostics (Retrieval index / Query cache / Last query / Session snapshot).
145
+
146
+ ![Ranked search with Hot Memory Inspector and Memory Diagnostics](picture/hot%20memory预览与记忆诊断5.png)
147
+
148
+ ## Storage & Privacy
149
+
150
+ ```text
151
+ ~/.dsh/dsh-memoir.json ← structured JSON (single source of truth / SSOT)
152
+ <workspace>/PROJECT_MEMORY.md ← human-readable projection regenerated from the JSON (git-friendly)
153
+
154
+ No cloud memory DB · No embedding API · No vector DB
155
+ ```
156
+
157
+ JSON is the source of truth and Markdown is the generated projection: the panel, the tools, and the agent write the same data. Since v0.4.2 the panel write API is also workspace-authorized — an absolute path submitted by the browser is not authorization by itself; only the current active cwd or an existing store project can be written to.
158
+
159
+ ## Configuration
160
+
161
+ Add a `config` block on the plugin row in `cordis.patch.yml` (all optional; defaults shown):
162
+
163
+ ```yaml
164
+ - insert:
165
+ - id: memoir
166
+ name: dsh-memoir
167
+ config:
168
+ enabled: true # master switch (tools, routes, prompt section)
169
+ announceToAgent: true # system-prompt announcement section
170
+ autoDistill: true # auto distill reminder after each worked turn
171
+ autoDistillEvery: 1 # remind at most once per N worked turns
172
+ autoDistillCooldownMin: 0 # require M minutes between successful reminders
173
+ autoDistillMinTools: 1 # triggering turn must contain at least K tool calls
174
+ hotMemoryTokens: 900 # Hot Memory target tokens
175
+ hotMemoryMaxTokens: 1200 # Hot Memory hard ceiling (never exceeded)
176
+ readDefaultLimit: 8 # memoir_read default result count
177
+ readMaxLimit: 30 # memoir_read maximum result count
178
+ sessionSnapshotMax: 128 # per-session snapshot LRU cap
179
+ queryCacheSize: 128 # ranked-query LRU cache size
180
+ ```
181
+
182
+ The three auto-distill frequency conditions are combined with AND and isolated per agent. Idle, aborted, subagent, and prior-`memoir_record` turns do not advance the interval. A worked turn below `autoDistillMinTools` advances the interval but cannot trigger by itself. Cooldown changes only after a successful steer.
183
+
184
+ ## Design Trade-offs
185
+
186
+ - **Bounded vs full injection**: v0.3 injected the full history into the prompt and it kept growing; v0.4+ injects only budgeted Hot Memory, with long-tail history recalled on demand. Token benchmarks below.
187
+ - **Frozen vs fresh**: within a session the injected text is frozen to gain prompt-prefix cache hits; without a unique session identity it is not frozen (v0.4.2), so new sessions always see new memory.
188
+ - **Hot Memory quota**: Recent state (newest work, 1–3 entries) is guaranteed a floor, actions/lessons fill by ranking, and work only appears in Recent state — never injected twice (v0.4.2).
189
+ - **Multi-process safety**: store record/remove runs inside a cross-process critical section on `~/.dsh/dsh-memoir.lock` (exclusive O_EXCL creation with timeout); the section force-reloads from disk before mutating, so two interleaved DSH processes lose no updates (v0.4.2).
190
+ - **Windows paths**: canonical keys are fully lowercased (`C:\A` / `c:\a\` / `C:/A` share one bucket) while display paths keep the original casing (v0.4.2).
191
+ - **GUI and Agent share one engine**: panel search and `memoir_read` use the same RetrievalEngine instead of separate filter logic (v0.4.2).
192
+ - **Auto-distill cadence**: the default still reminds after every worked turn; research-heavy sessions can combine interval, cooldown, and activity thresholds to reduce interruptions (v0.5.2).
193
+
194
+ ## Use Cases
195
+
196
+ | Scenario | How to use it |
197
+ | --- | --- |
198
+ | Recurring environment pitfalls (encoding / escaping / paths / permissions) | record a `lessons` entry with copy-pasteable fix commands |
199
+ | Project rules and conventions (no emoji, run tests before release, branch policy) | record as `actions`, auto-injected for whoever takes over |
200
+ | Root cause of a hard-to-find bug | record as `lessons` / `work` to avoid re-investigation |
201
+ | Fixed deployment/release checklist | record as `actions`; new sessions follow it |
202
+ | Reuse experience across projects | global tab or `memoir_read(scope: 'global', query: ...)` |
203
+
204
+ Typical example: after solving "console Chinese mojibake" the first time, record the diagnosis and fix commands as a `lessons` entry (e.g. `chcp 65001 first … always write UTF-8 without BOM`); every new session in this project then inherits the lesson automatically instead of re-debugging, and cross-project global search hits it too. The memory plugin distills "root cause + fix command" into project knowledge — it does not fix the terminal's own encoding defects.
205
+
206
+ ## Comparison
207
+
208
+ | Project | Primary focus |
209
+ | --- | --- |
210
+ | dsh-memory | citation / source-traceable reference memory |
211
+ | dsh-mnemon | a heavier long-term memory system |
212
+ | distill | distilling sessions into skills |
213
+ | **dsh-memoir** | **lightweight project workflow memory: local, bounded injection, ranked recall** |
214
+
215
+ Each plugin has its own focus — pick per need; no "which is stronger" narrative.
216
+
217
+ ## Development / Benchmark / Tests
218
+
219
+ ```bash
220
+ pnpm install # install devDeps (typescript, esbuild, @deepseek-ai/* type packages)
221
+ pnpm run build # tsc builds the host + esbuild builds the client bundle
222
+ pnpm run typecheck # full type check (src + test)
223
+ pnpm test # 147 tests: store (incl. multi-process lock) / snapshot / selector / retrieval / tools / routes / auto-distill / integration / client pure logic / bundle protocol & purity / release notes
224
+ npm run bench # benchmark (100/1k/10k/100k entries); results written to bench/report.md
225
+ ```
226
+
227
+ Quality gates: **Top-5 recall ≥ 90% · Hot Memory ≤ configured hardMax · same-session prompt-prefix stability · global recall ≤ limit · zero lost updates across processes**.
228
+
229
+ v0.4.2 benchmark summary (node v22.23.2, budget 900/1200 tokens; full report in `bench/report.md`. Methodology fixed: uncached queries measure `search()` directly; cached queries warm the same query first, then time it):
230
+
231
+ | Entries | Cold load | Warm read | Hot Memory build | Index build | Uncached query | Cached query | Cache hit rate | Full markdown tokens | Injected tokens | Reduction |
232
+ |---|---|---|---|---|---|---|---|---|---|---|
233
+ | 100 | 1.3 ms | 2.22 µs | 0.54 ms | 2.9 ms | 0.224 ms | 2.87 µs | 50.0% | 3870 | 902 | 76.7% |
234
+ | 1,000 | 1.6 ms | 0.40 µs | 0.70 ms | 15.0 ms | 1.419 ms | 1.45 µs | 50.0% | 38182 | 916 | 97.6% |
235
+ | 10,000 | 25.3 ms | 0.42 µs | 2.60 ms | 142.9 ms | 11.889 ms | 1.14 µs | 50.0% | 385807 | 902 | 99.8% |
236
+ | 100,000 | 158.2 ms | 0.42 µs | 31.97 ms | 2238.7 ms | 153.551 ms | 1.15 µs | 50.0% | 3907057 | 917 | 100.0% |
237
+
238
+ ## Implementation
239
+
240
+ - **Full-stack TypeScript**: `src/host/*.ts` (store / tools / retrieval / selector / snapshot / routes / autodistill / index — tsc emits `lib/*.js`) + `src/client/*.ts(x)` (esbuild emits the `lib/client.js` closure-factory bundle).
241
+ - **Two-sided plugin**: the host half registers the agent tools, `/api/dsh-memoir` routes, the `agent/turn-stopping` auto-distill listener, and the per-project system-prompt injection section; the client half renders the panel. Runtime deps are official NPM SDK packages only.
242
+ - Mounted via the `dsh.bundle.patch` manifest (`insert` row in `cordis.patch.yml`); no DSH source changes.
243
+ - Auto-distill safety boundaries: top-level sessions only (subagents / nested delegations skipped), turns with tool activity that haven't recorded yet, aborted turns skipped, at most one steer per turn.
244
+
245
+ ## Contributing
246
+
247
+ PRs and issues are managed with templates and automation:
248
+
249
+ - [CONTRIBUTING.md](CONTRIBUTING.md) — PR scope, commit conventions and checklist;
250
+ - [ISSUE_TRIAGE.md](ISSUE_TRIAGE.md) — issue labels, classification and closing criteria;
251
+ - `.github/ISSUE_TEMPLATE` — bug / request templates; `.github/pull_request_template.md` — PR template.
252
+
253
+ Bug reports must include screenshot / log evidence, a smoke test, code references and a patch. New features and documentation-only PRs must first be discussed in an issue.
254
+
255
+ ## Release
256
+
257
+ Current stable release: **v0.5.2** (2026-08-22) · [GitHub Release](https://github.com/Qinling-Melon-Farmers/dsh-memoir/releases/tag/v0.5.2) · [npm](https://www.npmjs.com/package/dsh-memoir/v/0.5.2). Full history is in [CHANGELOG.md](./CHANGELOG.md).
258
+
259
+ Every version keeps Chinese and English release notes in sync. GitHub Releases show Chinese by default and place the English notes in a collapsible `English` section.
260
+
261
+ Version releases run automatically in `.github/workflows/publish.yml` when a `v*` tag is pushed: install deps, verify the tag matches the `package.json` version, run typecheck/test, publish to npm, then create a same-tag GitHub Release with the tarball asset. Configure either of these auth options in the repo:
262
+
263
+ - npm Trusted Publishing: GitHub repo `Qinling-Melon-Farmers/dsh-memoir`, workflow `publish.yml`
264
+ - GitHub Actions secret `NPM_TOKEN`: a granular token with publish rights and 2FA bypass allowed
265
+
266
+ Publishing a patch release:
267
+
268
+ ```bash
269
+ npm version patch
270
+ git push
271
+ git push origin vX.Y.Z # use the actual version printed by npm version
272
+ ```
273
+
274
+ `npm version patch` updates `package.json`, creates the version commit and the tag; no manual `git tag` or local `npm publish` needed.
275
+
276
+ ## License
277
+
278
+ Apache-2.0