v0.2.2

0.2.2 — 2026-10-27

• Three interface switches on the plugin's settings form. showSidebarEntry,
  showCommitStatus and showRecallPanel (all default true) independently hide
  the Studio entry in the left sidebar, the per-session commit pill under the
  composer, and the Memory recall tab in the right sidebar. They are persisted by
  the same Configure form and applied live through ctx.configForms — saving
  mounts or unmounts the surface with no reload or restart. The form itself is
  never hidden: a switched-off surface can always be switched back on there.
  Hiding the sidebar entry unmounts the Studio page (it loads fresh when shown
  again); hiding the recall tab closes an open recall page once the conversation
  is back on screen (a page open in a background pane has to be closed by hand,
  because the harness exposes no tab enumeration). A deployment
  without the settings client keeps every surface visible, exactly as before the
  switches existed. The release was exercised in the running desktop GUI: the host
  Config was hot-reloaded without an app restart, each surface disappeared and
  returned on save, and switching the recall tab off closed an already-open recall
  page once the conversation came back; the test-written overrides were then
  removed, so the defaults are in force.

• 插件设置里新增三个界面开关。 showSidebarEntry、showCommitStatus、
  showRecallPanel（默认都是 true）分别控制左侧边栏的 Studio 入口、输入框下方的
  提交状态胶囊、右侧边栏的「记忆召回」tab。开关与连接参数在同一个 Configure 表单里
  保存，客户端通过 ctx.configForms 实时生效——保存即挂载或卸载对应界面，不需要重载
  窗口或重启应用。配置表单本身永远可见，关掉的入口随时能在这里开回来。隐藏左侧入口会
  一并卸载 Studio 页面（重新打开后重新加载）；隐藏召回 tab 后不再提供该页，已打开的召回页
  会在回到对话时自动收起（若它在后台分屏里、不是激活页，则需手动关闭——框架没有提供枚举
  标签页的接口）。没有 settings 客户端的部署保持三个入口全部显示，与加开关之前完全一致。
  本版本在运行中的桌面 GUI 里实测过：宿主 Config 无需重启 App 即热重载，三个入口在保存后
  当场消失/恢复，关掉召回开关后已打开的召回页会在回到对话时自动关闭；随后清除了测试写入的
  覆盖值，默认值（全开）生效。

• Verified against DSH 0.2.1-rc.3. The desktop app moved one prerelease
  forward on the 0.2.1 line. No plugin code changed: the same sources type-check
  against the 0.2.1-rc.3 type packages and the whole suite passes on rc.3 — 88
  unit/component tests, 160 client-smoke checks, 24 packaging-contract checks, the
  live OpenViking smoke (status, commits, timeline, probe, recall, diff) and the
  six-request route fence. The development dependencies now pin 0.2.1-rc.3; the
  peer range and both engines.dsh entries already admitted that release (same
  0.2.1 tuple), so no new range branch was needed. The running app confirms it:
  the sidebar row, Studio panel, commit pill and recall tab all mount on the rc.3
  GUI, and the host routes answer ok: true / healthy: true. The requirements
  table now names OpenViking 0.5.1.1, the server the live smoke ran against.

• 已在 DSH 0.2.1-rc.3 上验证。 桌面端在 0.2.1 线上又前进一个预发布版本。
  插件代码没有改动：同一份源码对 0.2.1-rc.3 类型包通过类型检查，整套测试也在
  rc.3 上全绿——88 项单测/组件测试、160 项客户端冒烟、24 项打包契约、真实
  OpenViking 在线冒烟（状态、提交、时间线、探测、召回、差异）与 6 项路由 fence。
  开发依赖现在钉到 0.2.1-rc.3；peer 范围与两处 engines.dsh 本就覆盖该版本
  （同为 0.2.1 元组），无需新增范围分支。运行中的 app 也确认：左侧栏行、
  Studio 面板、提交状态胶囊与召回 tab 都在 rc.3 界面上正常挂载，宿主路由返回
  ok: true / healthy: true。前置条件表里的 OpenViking 实测版本更新为
  0.5.1.1（本次在线冒烟所用服务端）。

v0.2.1

0.2.1 — 2026-10-18

• Declared compatibility with DSH 0.2.1-rc.2. The development dependencies
  now track the 0.2.1 line (0.2.1-rc.2, @deepseek-ai/cordis 4.0.5,
  @deepseek-ai/schemastery 3.18.5), and both the peer range and engines.dsh
  name that prerelease line as well as 0.2.0's. No plugin code changed: the same
  sources type-check against both versions, and the full suite — including the
  live OpenViking smoke — passes on 0.2.1-rc.2.

• 声明支持 DSH 0.2.1-rc.2。 开发依赖升到 0.2.1 线（0.2.1-rc.2、
  @deepseek-ai/cordis 4.0.5、@deepseek-ai/schemastery 3.18.5），peer 范围与
  engines.dsh 同时标出 0.2.1 预发布线与 0.2.0 线。插件代码没有改动：同一份
  源码在两套类型下都通过类型检查，并在 0.2.1-rc.2 上跑完整套测试（含真实
  OpenViking 在线冒烟）。

v0.2.0

0.2.0 — 2026-10-02

• Recall detail in the right sidebar — a per-session 记忆召回 tab showing what
  OpenViking retrieves for the session in view: the query it searched with (the
  session's own most recent user turn, or one you type), every hit in each of the
  three sources with its score (graded red through green), file name, kind and
  abstract, the server's own retrieval plan, and one entry's full text on click. It asks the same
  session-aware route the memory plugin calls, so the ranking is the server's
  rather than a second implementation of it. Reached through the right sidebar's
  guide; nothing is written.

• Two routes behind the same trust fence: /recall and /recall/content (the
  latter refuses anything that is not a viking:// path, and truncates).

• The interface is bilingual. Every string this plugin renders — the panel,
  the pill and its popover, the recall tab, the configuration form — now follows
  the language DSH is set to, with Chinese and English dictionaries and English as
  the fallback. Host-side messages became codes plus parameters, so the half that
  has no language no longer decides the wording.

• The plugin's settings are editable in the GUI. Its row on the Plugins
  page now has a Configure form — endpoint, key, identity, Studio path and the
  two cache lifetimes — with a check button that probes the address before
  saving, and a per-field reset that clears the override instead of writing an
  empty value. The same values can still be written by hand in the profile patch.

• The host half is self-contained: @deepseek-ai/schemastery is bundled instead
  of being imported at runtime, so the plugin no longer assumes a harness hands it
  a schema library the profile may not have.

• The package is publishable: private removed, LICENSE added, and the official
  @deepseek-ai/* dependency replaced by an explicit @deepseek-ai/dsh peer.

• 界面中英双语：本插件渲染的每一处文字（面板、胶囊及其弹窗、召回面板、配置表单）现在都跟随
  DSH 的语言设置，内置中英两套字典，其他语言退回英文。宿主侧消息改成"码 + 参数"，
  不再由那个没有语言概念的半部分决定措辞。

• 插件设置可以在界面里改了：Plugins 页里本插件那一行多了 Configure 表单
  （地址、Key、身份、Studio 路径、两个缓存时长），地址旁有 检测 按钮可在保存前试连，
  每个字段的 默认 按钮是清除覆盖、恢复继承，而不是写入空值。同样的值仍可手写在 profile patch 里。

• 宿主半部分自包含：@deepseek-ai/schemastery 改为打进 bundle，不再假设 harness 会提供它。

• 包已可发布：移除 private、补 LICENSE、把官方 @deepseek-ai/* 依赖换成显式的
  @deepseek-ai/dsh peer。

• 右侧边栏的记忆召回面板：按会话显示 OpenViking 为当前会话召回了什么——检索用的那句话
  （默认本会话最近一次提问，也可自己输入）、三个来源里每条命中的分数与 viking:// 路径及摘要、
  服务端自己的检索计划，以及点开任意一条看全文。它调用的是记忆插件本身所用的那条会话感知接口，
  所以看到的是服务端的真实排序，而不是另写一套检索。从右侧边栏的引导页进入，全程不写入。

• 新增两个走同一道信任围栏的接口：/recall 与 /recall/content（后者只接受 viking://
  路径，并做长度截断）。