Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(i18n): address RFC translation review

Browse Source
This commit is contained in:
Tianyi Cui
2026-07-22 22:29:39 +08:00
parent 0b1857904a
commit 1a39953f69
447 changed files with 1106 additions and 1106 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/rfc/implemented/simplification/2026-06-19-drop-mutable-session-summary.md
View File

@@ -1,9 +1,9 @@
# RFC: Drop the mutable session summary
English | [中文](2026-06-19-drop-mutable-session-summary.zh.md)
Status: implemented
English | [中文](2026-06-19-drop-mutable-session-summary.zh.md)
## Problem
The [session-persistence seam](../architecture/2026-06-14-session-persistence.md) split a session's out-of-log metadata into two types owned by `dsh-session`: an immutable `SessionHeader` (`version`, `id`, `createdAt`, `cwd?`, `parentSession?`) written once at creation, and a mutable `SessionSummary` (`updatedAt`, `title?`, `firstPrompt?`) "updateable without touching the append-only log". Their union was `SessionMeta = SessionHeader & SessionSummary`, and the abstract `SessionPersistence` service carried a seventh method — `update(id, summary)` — for rewriting the summary. Each backend implemented the mutable store its own way: JSONL wrote a separate atomic `.summary.json` **sidecar** beside the log (temp-write + rename, best-effort), SQLite kept `updated_at`/`title`/`first_prompt` **columns** bumped inside the append transaction.