给你的 Harness 一棵会生长的记忆树 A growing memory tree for your Harness

01它做什么01What it does

六个机制，全部落在你自己的机器上。

Six mechanisms, all on your own machine.

02数据互通02Interoperability

存储就是 memory.jsonl + emb.f32 侧车——Rust memlite CLI 写的库，插件直接读；插件写的库，Rust 直接 recall。同一份记忆，CLI、Harness、未来的 Kimi/ZCode 插件共享。

Storage is plain memory.jsonl + an emb.f32 sidecar — libraries written by the Rust memlite CLI read directly in the plugin and vice versa. One memory, shared across CLI, Harness, and future Kimi/ZCode plugins.

03命令03Commands

DSH 命令名为单 token——13 个核心 dash 名 + 3 个 Obsidian 命令，全部返回 CommandResult。

DSH command names are single tokens — 13 core dash names plus 3 Obsidian commands, all returning CommandResult.

04配置04Configuration

侧栏「插件」→ Memlite 记忆行 → 配置：插件自带浏览器半区，表单暂存草稿、只读生效值，保存才写入 profile 的 cordis.patch.yml。密钥走 credentials——永不写入配置文件或数据仓。

Sidebar → Plugins → the Memlite Memory row → Configure: the plugin ships its own browser half; the form stages a draft, shows effective values, and only Save writes to the profile's cordis.patch.yml. Keys live in credentials, never in config files or the data store.

05安装与上手05Install & quick start

# 本地开发装载（npm 发布前）
pnpm -C dsh-memlite build     # 宿主 + 浏览器 bundle（dist/index.js、dist/client.js）
dsh plugin --profile <profile> add ./dsh-memlite

# 发布后
dsh plugin --profile <profile> add @rsrsai/dsh-memlite

# 图形配置：侧栏「插件」→ Memlite 记忆 → 配置
# 对话里
/memlite-remember nginx 504 排查手册 --title nginx题
/memlite-remember 下游结论 --parent <id>
/memlite-recall 网关超时
/memlite-tree --outline

记住一条因，补一条果——下次相关对话开始时，记忆已经在 prompt 里。

Record a cause, append an effect — next time a related conversation starts, the memory is already in the prompt.

060.3.1 实测记06Field notes

从 0.1.0 的 API 漂移，到 0.3.1 的 GUI 配置页与展示名——每一条都先在真机坐实，再回写代码与文档。

From the 0.1.0 API drifts to the 0.3.1 GUI settings page and display name — every item was confirmed on a real host before being written back into code and docs.

• GUI 配置页GUI settings page 真机用 UI 自动化验证：把 recallLimit 改成 6 保存，profile 的 cordis.patch.yml 出现 - id: memlite / config: recallLimit: 6；改回 5 保存，覆盖被 unset 移除。verified with UI automation: setting recallLimit to 6 wrote - id: memlite / config: recallLimit: 6 into the profile's cordis.patch.yml; setting it back to 5 removed the override via unset.
• volatile 投影Volatile projection settings 只投影 .volatile() 字段，且同一 schema 内不允许嵌套 volatile——所以根 Config 整体 volatile，插件按次读快照。settings projects only .volatile() fields and forbids nested volatile inside one schema — so the root Config is volatile and the plugin reads a snapshot per call.
• 展示名称Display name 来自 locale/<lang>.json 的 meta.title/meta.description；包有 exports 时必须导出 ./locale/*.json，否则静默回退包名。bundle 卡片与行共用同一份 meta。comes from meta.title/meta.description in locale/<lang>.json; when the package declares exports, ./locale/*.json must be exported or it silently falls back to the package name. Bundle cards and rows share the same meta.
• 重载方式Reloading a row 本 profile 下 set_plugin 对 bundle 内行返回 overridden 且不生效；用 set_bundle 关/开组合包，行才会重启并重读 manifest 与客户端 bundle。on this profile set_plugin reports overridden for a row inside a bundle and does nothing; toggling the bundle with set_bundle restarts the row and re-reads its manifest and client bundle.
• credentials.resolve(ref) 返回 {value, source}——不是 get(ref)（0.1.0 实测）。returns {value, source} — not get(ref) (0.1.0 finding).
• AssembleContext 类型面无 agent 字段，运行时实传 {agent, scope, signal}——防御性读取。has no agent field in types, but the runtime passes {agent, scope, signal} — read defensively.
• 无 providers 服务No providers service ——dsh-llm 只有 chat，无 embeddings；host 档明示回退。— dsh-llm is chat-only; the host tier falls back explicitly.
• COMMAND_NAME 单 token 正则——命令名含空格注册即拒。is a single-token regex — spaced names are rejected at registration.