dsh-loadout 0.12.1 → 0.12.2

package/CHANGELOG.md

@@ -2,6 +2,10 @@
 
 「装备栏」是一个 DeepSeek Harness 插件：给每个对话选一套工具（套装），只把用得上的工具投给模型。
 
+## 0.12.2
+
+- **修「绑定到已不存在的套装」**：如果某个对话绑的套装在应用关着的时候被删掉（旧版本、手改 loadout.json、或别的机器同步过来的文件），启动后它会被当成「空套装」套用——等于把这对话的工具连同内置工具一起裁光，只剩 kit_*。现在这种绑定在第一次被读到时回退到「全部」，并把 ssignments 里那个失效名字改成 
+ull，日志里留一行说明。回归断言： binding to a deleted kit falls back to 全部（用第二个模块实例模拟重启）。
 ## 0.12.1
 
 - **修卡死**：编辑（覆盖保存）、重命名或删除一个正在被对话使用的套装时，宿主会遍历「正在用它的对话」并逐个重新套用工具；这个遍历边改边往 `Map` 里重写条目，迭代器被塞回一个已经走过的键，于是永远走不完——表现是界面点下去没有任何反应、进程占满一个核。现在遍历快照（`[...state]`），编辑与删除都会立刻返回。

package/index.js

@@ -1132,8 +1132,19 @@ export function apply(ctx, config = {}) {
    */
   function ensureBindingApplied(agent) {
     if (agent === undefined || agent === null) return
-    const value = ensureBinding(agent)
+    let value = ensureBinding(agent)
     if (value === undefined) return
+    // A stored binding can name a kit that no longer exists — an older build, a
+    // hand-edited store, or a kit deleted while the app was closed. Applying it
+    // would compute an empty allow list and strip the conversation down to the
+    // kit_* tools, so such a conversation falls back to 全部 and the dangling
+    // name is rewritten to stop it resurfacing on every read.
+    if (value !== null && value !== DEFAULT_DSH && resolveKit(lastAgent, value) === undefined) {
+      book.assignments[sessionIdOf(agent)] = null
+      save()
+      ctx.logger?.warn(`dsh-loadout: 套装「${value}」已不存在，这个对话回到「全部」`)
+      value = null
+    }
     const selection = selectionForBinding(value)
     const current = state.get(agent)?.selection
     if (current !== undefined && sameSelection(current, selection)) return

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-loadout",
-  "version": "0.12.1",
+  "version": "0.12.2",
   "description": "Loadout for DeepSeek Harness: group tools into kits, keep only the current kit's tools visible in each conversation, and manage everything from a settings panel.",
   "type": "module",
   "main": "./index.js",

package/scripts/selftest.mjs

@@ -846,6 +846,24 @@ try {
 check('a preset name cannot be taken by a user kit',
   /预置/u.test(presetClashError ?? ''), presetClashError)
 
+// T22: a binding that names a kit removed outside the app falls back to 全部.
+// Simulated the way it really happens: the kit is gone from the store file when
+// the app starts again, so a fresh module instance has to cope with it.
+await ctxV2.registered.get('kit_create').execute(
+  { name: 'ghost-kit', title: '已删除的', builtins: ['read'], plugins: [] }, exec(agentB))
+await ctxV2.registered.get('kit_assign').execute({ sessionId: 'session-ghost', kit: 'ghost-kit' }, exec(agentB))
+const storeWithGhost = storeOf()
+storeWithGhost.kits = storeWithGhost.kits.filter((kit) => kit.name !== 'ghost-kit')
+writeFileSync(join(v2Home, '.dsh', 'loadout.json'), JSON.stringify(storeWithGhost), 'utf8')
+const v2b = await import('../index.js?v2=2')
+const ctxV2b = makeCtx()
+v2b.apply(ctxV2b, { defaultKit: '', kits: config.kits })
+const agentGhost = makeAgent(undefined, { id: 'session-ghost' })
+for (const handler of ctxV2b.handlers.get('agent/created') ?? []) handler(agentGhost)
+check('a binding to a deleted kit falls back to 全部',
+  storeOf().assignments['session-ghost'] === null && keptOf(agentGhost).includes('web_search'),
+  JSON.stringify({ assignments: storeOf().assignments, kept: keptOf(agentGhost) }))
+
 // T03/T05: the default changes again; conversations that already answered keep theirs.
 const agentC = makeAgent(undefined, { id: 'session-c' })
 await ctxV2.registered.get('kit_set_default').execute({ name: 'chat' }, exec(agentB))