dsh-waifu-agents 0.1.1 → 0.1.2

package/MAINTAINER.md

@@ -66,7 +66,20 @@ updateCheck  updateApply  updateProgress  purge
 - **原子写**：`writeAtomic()` = 临时文件 + `rename`，覆盖前留 `<name>.bak`。
 - **缓存**：`(mtimeMs, size)` 键；`chars` 是「去掉 front matter 并 trim 之后的 JS 字符串长度」，和字节数没有稳定换算。
 - **`list` 不带绝对路径**：它给 `id / idOk / name / order / description / group / template / chars / charsFull / problems / owned / mtimeMs / size`。
-- **`roster` 多带一个 `defaultResolves`（三态）**：`null` = 没有任何面报出默认值，**不知道**；否则 = `presets.some(r => r.id === defaultId)`。平台的新任务页 chip 是 `presets.find(p => p.isDefault)?.id ?? presets[0].id`（`ui-agent-preset`），所以默认指不到人时它会**静默**起在第一行——那个旗标是唯一能把这件事说出口的地方。`null` 不能压成 `false`：那会冤枉一个单纯什么都没设的 profile。客户端的 `defaultResolves` state 同样是三态，设置页只在 `=== false` 时报警。
+- **`roster` 多带一个 `defaultResolves`（三态）**：`null` = 没有任何面报出默认值，**不知道**；否则 = `presets.some(r => r.id === defaultId)`。`null` 不能压成 `false`：那会冤枉一个单纯什么都没设的 profile。客户端的 `defaultResolves` state 同样是三态，设置页只在 `=== false` 时报警。
+  ⚠️ **这条旗标曾经把后果写反过，别照着旧注释改回去。** 旧文案（注释和 `defaultUnresolved` 都是）说「默认指不到人 → 新会话悄悄落到列表第一项」，依据是 composer 的 `fallback = presets.find(p => p.isDefault)?.id ?? presets[0]?.id`（`ui-agent-preset.js:1263`）。那是**渲染层**的兜底，永远轮不到它跑：服务层先解析，`retain(id)` 直接抛
+  ```js
+  // registry.js:494 —— 默认就是 selectedDefault ?? config.default
+  get defaultId() { return this.config.selectedDefault.get() ?? this.config.default; }
+  // registry.js:643（resolve / readDocument 同样）
+  throw new RemoteError("agent-preset/not-found", `Unknown agent preset: ${wanted}`, { agentPreset: wanted, available: [...] });
+  ```
+  所以真实后果是**每一个新会话都被拒绝**（用户看到的那条 `新建会话失败：agent-preset/not-found: Unknown agent preset: 照桥心美`），不是静默回落到第一行。写这条断言时别用「回落」这个词——它会把一个 `P0` 级故障描述成显示问题。
+- **悬空的默认是自愈的，不是只报告。** `reconcileDefault()` 在三个地方跑：`status()`（op `list`，也就是**打开面板就修**）、`remove()`（退掉的人设正好是默认那位）、以及启动时 `scan()` 之后的 `.then()`。判定是「`selectedDefault` 有值，但 `agentPresets.list()` 里没有这个 id」；动作只有**清掉**（`moveDefaultOff`），**绝不替用户改指到另一个妻子**——清空会回落到 profile 的 `default`，替用户选人则是另一件更响的事。两个必须保留的细节：
+  - **名册为空时不动**（`rows.length === 0` → 「名册还是空的，先不动」）。别的插件在**它自己的** `apply` 里注册 preset，本行完全可能先被激活；此时读名册会把自己还没注册的 id 判成悬空。这正是启动那一跳要 `.then()` 挂在 `scan()` **之后**的原因——先让本插件自己的人设进名册。空名册守卫是同一件事的兜底。
+  - **`moveDefaultOff` 是两步，和 `setDefault` 一样**：`writeDefault`/`verifyDefault` 走 `settings` 服务并**重读确认**，然后 `resettleUnstarted` 把还挂在那个死 id 上、没开口的会话挪走。只清字段的话，屏上那个空会话的 header 还钉着死 id，chip 照样是坏的，建会话照样失败。
+  - 修复失败**必须出声**：`status()` 回传 `defaultHeal: { ok: false, from, reason }`，面板用 `defaultHealFailed` 显示（此时新会话仍然起不来，是唯一不能静默的一条）。成功回传 `{ ok: true, from, nowDefault, moved }`。`remove()` 回传 `defaultFollowed: 'cleared' | 'unchanged' | 'failed'`。
+- **`remove()` 现在是第二个会改默认的写路径**（第一个是 `rename()` 的 `repointDefault`）。退掉的正好是默认那位时，不清默认就留下一个悬空 id，等于「删人设 = 下次新会话失败」。爆炸半径同样压住：退的不是默认那位时**一个字节都不写**（断言 `defaultFollowed === 'unchanged'`）。
 - **非法 id 不进选择器**：`choosableRows()` 只收 `problems` 为空且 `idOk` 为真的行。
 - **条件样式必须把键写进基础样式，不能让 React 去"移除"。** 这一条看着像代码风格，其实是面板高亮的生死线。React 丢弃一个不再收到的样式属性时写的是 `style[name] = ''`；对普通属性这没问题（开关的 `transform` 就是这么被清掉的，实测正常），但对**简写里的属性不行**：清掉 `borderColor` 之后，`border: 1px solid …` 会把颜色重新应用一遍，而"颜色被清掉"的边框会回落到 `currentColor`。本主题下 `currentColor`（`--dsw-alias-label-primary`）和品牌色（`--dsw-alias-brand-primary` = `neutral-bluish-50`）是同一个近白，于是**一个已经不是默认的行看起来仍然选中**，只有重挂载才会好。这正是用户报的「多次切换默认人设后，选中过的 border 样式存在残留，再次进入就消失了」——而且只发生在**点过的**那些行上（点过才有机会被设过品牌色），没点过的行用的是显式的 `border-l1`。所以 `L.item` 里同时写明 `border` 和 `borderColor`/`borderStyle`，`L.switch` 写明 `borderColor`，`L.thumb` 写明 `transform: 'translateX(0)'`。自测里有一条按**键集合**遍历所有 `条件变体/基础` 配对的断言，加新的条件样式时它会替你拦住。
 - **会话顶部那个 chip 不是我们的，是 `projectionValues.agentPreset`。** 它由**唯一一种事件**推进：`agent-preset/selected`（`registry.js` 的 `apply` 只认这个），而写它的只有平台的 `select()`。`select()` 对**已开过轮**的会话会抛 `agent-preset/locked` —— 因为"真的换"意味着重挂载整套 preset、连工具一起换。所以 `/waifu-change` 追加**事件本身**：只动标签，不动正在跑的树；人设本来就有 override 在供，标签和模型听到的因此终于一致。两条硬约束：① 只能写**已注册**的 preset id（值会被持久化，恢复会话时按它挂载，写一个没人提供的 id 会让下次恢复失败）；② 插件配置的 `syncSessionChip: false` 可以整条关掉（关的理由是这条通道同时决定恢复时挂载谁）。`/waifu-reset` 对应地把标签挪回"会话挂载的那一位，没有就回落到全局默认"。
@@ -89,7 +102,7 @@ updateCheck  updateApply  updateProgress  purge
 ## 测试与 CI
 
 ```bash
-pnpm test          # = node selftest.mjs，296 条断言，离线、不碰 profile、不联网
+pnpm test          # = node selftest.mjs，313 条断言，离线、不碰 profile、不联网
 pnpm pack          # 先看产物清单
 pnpm publish --no-git-checks 
 ```
@@ -125,7 +138,8 @@ CI 在 `.github/workflows/test.yml`：push 到 `main`、开 PR、或手动触发
 18. `/waifu-reset` → 回落到这个会话原本挂载的那一篇。
 19. **开一个新任务（别发消息）→ 看顶部 preset 下拉**：四个内置模式（standard / ptc / minimal / cordis）必须在**最上面四行**，自定义人设全在下面。这是 `PERSONA_ORDER_BASE` 唯一的验收点。
 20. **默认开关连点**：把默认从 A 换到 B，再换到 C，**每换一次都留在面板里看**——高亮边框必须**当次**就落到新行上，不能还挂在旧行上等下次进来才自愈。然后开新任务，顶部下拉默认选中的必须是 C。
-21. 把默认指向一个**正在被编辑、暂时组装不出来**的人设 → 设置页「新会话默认用谁」下面必须出现「这个默认指不到任何可用的人设」，而不是安安静静地回落。
+21. 把默认指向一个**正在被编辑、暂时组装不出来**的人设 → 设置页「新会话默认用谁」下面必须出现「这个默认指不到任何可用的人设」。
 22. **改默认不该需要重启**：在插件面板把默认从 A 换成 B → **立刻**开一个新任务（别发消息）→ 顶部选择器默认选中的必须是 B。这是「写入有没有通知平台」唯一的验收点（`settings/document-updated`）；走 `configEditor.edit()` 的旧路径这里会显示 A。
 23. **切完看会话顶上那个标签**：在同一个会话里 `/waifu-change` 到另一位 → 会话标题旁边的标签必须**跟着变**。它不动就是 `agent-preset/selected` 没追加成功；把它写成 `syncSessionChip: false` 时标签**应该**保持不动。
 24. **改默认要连"当前这个空会话"一起换**：让新任务页停在屏幕上别动 → 在插件面板把默认从 A 换成 B → **不要新建会话**，回来看新任务页顶上的选择器，必须已经变成 B。这一条和第 22 条**不是同一件事**：第 22 条考的是"之后新建的会话拿谁"（`selectedDefault`），这条考的是"已经摆在屏幕上的那个空会话"（`projectionValues.agentPreset`）。只修了第 22 条的版本，这里会停在 A——而且 Agent 预设页的「新任务默认」徽章**已经是 B**，两处对不上就是它。
+25. **删掉人设文件 / 退掉默认那位，然后重启** —— 这是「悬空默认」的现场复现，也是这一版修复的验收点：① 把默认指向 A，**关掉 DSH**，把 `~/.dsh/personas/A.md` 从磁盘删掉（不走面板），重开 DSH → 新任务必须能正常建起来，**不能**出现 `agent-preset/not-found`；② 日志里应有一条 `WARN dsh-waifu-agents: 默认人设「A」已经不在名册里了…已清掉这条默认`；③ 打开插件面板 → 「新会话默认用谁」那行下面出现一条「已自动清掉」的说明（`defaultHealed*`），刷新一次面板后它消失；④ 面板里把默认设成 B → 在**面板里**退掉 B（归档）→ 默认必须跟着清掉，`~/.dsh/personas` 里出现 `B.md.off`，且下一次新任务不再失败。只有清了字段、没把屏上那个空会话一起挪走的版本，会在 ① 那里照样失败。

package/client.js

@@ -174,7 +174,11 @@ window.__ModuleLoader__.load({
         defaultUnchecked: '写进去了，但这个 profile 读不回来确认（既没有 settings，名册里也没有 isDefault）。这一行没报错，可也没人能担保平台认它。',
         defaultReseated: '也把当前这个还没开口的会话换过去了——新任务页顶上现在就是她。',
         defaultViaEditor: '警告：这次没走 settings 服务，退回配置编辑器写的。磁盘上是对的，但平台收不到通知，新任务页可能不跟——看日志里那条 warn。',
-        defaultUnresolved: '这个默认指不到任何可用的人设——新会话会悄悄落到列表第一项。重新点一次开关，或者换一个。',
+        defaultUnresolved: '这个默认指不到任何可用的人设——新建会话会直接失败（agent-preset/not-found），不是悄悄回落。插件会把它清掉，让新会话回落到 profile 默认。',
+        defaultHealed: '默认「{from}」已经不在名册里了——留着它新建会话会被 agent-preset/not-found 直接挡掉。已自动清掉，新会话现在用「{to}」。',
+        defaultHealedNobody: '默认「{from}」已经不在名册里了——留着它新建会话会被 agent-preset/not-found 直接挡掉。已自动清掉，新会话回落到 profile 默认。',
+        defaultHealedMoved: ' 还没开口的会话也一起换过去了。',
+        defaultHealFailed: '默认「{from}」已经不在名册里了，新建会话会被 agent-preset/not-found 直接挡掉——但这次没能自动清掉：{reason}。去「设置 → Agent Presets」重新选一个。',
         diagnostics: '诊断',
         defaultReadFrom: '默认值读自',
         srcRemoteExportList: '会话预置清单',
@@ -338,7 +342,11 @@ window.__ModuleLoader__.load({
         defaultUnchecked: 'The write went through, but this profile cannot read the field back to confirm it (no `settings`, and the roster carries no `isDefault`). Nothing errored — and nothing can vouch that the platform agrees.',
         defaultReseated: 'The session already open on the new-task screen was moved too — its chip names her now.',
         defaultViaEditor: 'Warning: this went through the config editor instead of the settings service. The disk is right, but the platform was not told, so the new-task screen may not follow — see the warning in the log.',
-        defaultUnresolved: 'This default points at no usable persona, so a new session silently falls back to the first row. Toggle it again, or pick another.',
+        defaultUnresolved: 'This default points at no usable persona, so a new session fails outright with agent-preset/not-found — it does NOT fall back to the first row. The plugin clears it, and new sessions go back to the profile default.',
+        defaultHealed: 'The default "{from}" is no longer in the roster, so new sessions would be refused with agent-preset/not-found. It has been cleared; new sessions now use "{to}".',
+        defaultHealedNobody: 'The default "{from}" is no longer in the roster, so new sessions would be refused with agent-preset/not-found. It has been cleared, and new sessions fall back to the profile default.',
+        defaultHealedMoved: ' The sessions that had not opened a turn were moved with it.',
+        defaultHealFailed: 'The default "{from}" is no longer in the roster, so new sessions are refused with agent-preset/not-found — and clearing it did not work: {reason}. Pick another one under Settings → Agent Presets.',
         diagnostics: 'Diagnostics',
         defaultReadFrom: 'default read from',
         srcRemoteExportList: 'session preset list',
@@ -1489,6 +1497,32 @@ window.__ModuleLoader__.load({
       return h('span', { style: L.meta }, key === undefined ? String(source ?? '—') : t(key));
     }
 
+    /**
+     * The one-line report for a default the Host had to repair.
+     *
+     * A default that names a preset nothing registers is not cosmetic: the
+     * registry refuses EVERY new session with `agent-preset/not-found`
+     * (`registry.js:643`), so this has to be said even though the user did not ask
+     * — and it has to distinguish 「修好了」 from 「没修掉」, because only the second
+     * one leaves new sessions still refusing to open.
+     * @param {{ ok: boolean, from?: string, nowDefault?: string | null, moved?: string[], reason?: string } | null | undefined} heal
+     * @param {(key: string) => string} t
+     */
+    function healNote(heal, t) {
+      if (heal === null || heal === undefined) return null;
+      const from = heal.from ?? '';
+      if (heal.ok !== true)
+        return t('defaultHealFailed')
+          .replace('{from}', from)
+          .replace('{reason}', heal.reason ?? '');
+      const to = typeof heal.nowDefault === 'string' ? heal.nowDefault : '';
+      const base =
+        to === ''
+          ? t('defaultHealedNobody').replace('{from}', from)
+          : t('defaultHealed').replace('{from}', from).replace('{to}', to);
+      return (heal.moved ?? []).length > 0 ? base + t('defaultHealedMoved') : base;
+    }
+
     function SettingsTab({
       data,
       t,
@@ -1598,13 +1632,27 @@ window.__ModuleLoader__.load({
           h('span', { style: L.meta }, data?.defaultId ?? '—'),
           h(Btn, { variant: 'toolbar', disabled: busy || data?.defaultId == null, onClick: onClearDefault }, t('clearDefault')),
         ),
-        // A default that resolves to no live row is the one failure the platform
-        // never reports: the registry quietly falls back to the profile default,
-        // and the new-task chip stages the first row instead. The setting page is
-        // the only place this can be said out loud, so say it here.
+        /*
+         * A default that resolves to no live row is the failure the platform never
+         * reports: the service throws `agent-preset/not-found` at session creation
+         * (`registry.js:643`) — the composer's 「落到第一项」 fallback is never
+         * reached — so every new task is refused with nothing on screen to explain
+         * it. The Host clears it on open; these two lines are the report.
+         */
         defaultResolves === false
           ? h('div', { style: L.card }, h('span', { style: L.error }, t('defaultUnresolved')))
           : null,
+        data?.defaultHeal != null
+          ? h(
+              'div',
+              { style: L.card },
+              h(
+                'span',
+                { style: data.defaultHeal.ok === true ? L.ok : L.error },
+                healNote(data.defaultHeal, t),
+              ),
+            )
+          : null,
         h(
           SettingRow,
           { title: t('paging'), hint: t('pagingHint') },

package/index.js

@@ -1940,8 +1940,14 @@ export function apply(ctx, config = {}) {
    * Panel state. `defaultId` comes from the LIVE roster rather than from the
    * config file: `selectedDefault` can be stale, or point at a preset that no
    * longer resolves, and the roster is what actually decides the next session.
+   *
+   * Opening the panel is also a repair point — see `reconcileDefault`, which runs
+   * first here. A default that names nothing does not merely read wrong: the
+   * registry refuses every new session with `agent-preset/not-found`, so leaving
+   * the panel to only REPORT it would mean reporting a broken app.
    */
   async function status() {
+    const healed = await reconcileDefault();
     // Live, not straight from the cache: `selectedDefault` can be stale or point
     // at a preset that no longer resolves, and the roster is what actually decides
     // the next session. Reporting the cached id is how the default's active border
@@ -1959,6 +1965,24 @@ export function apply(ctx, config = {}) {
       defaultId: cachedDefault.id,
       defaultSource: cachedDefault.source,
       defaultError: cachedDefault.error,
+      /*
+       * What the repair did, in the one case where the user has to know: the
+       * default they set is gone. `null` when there was nothing to repair.
+       * `ok: false` is the degrade path and it has to be visible — a default that
+       * names nothing still blocks every new session, so a silent failure here
+       * would look exactly like the bug it is supposed to fix.
+       */
+      defaultHeal:
+        healed.healed !== null
+          ? {
+              ok: true,
+              from: healed.healed,
+              nowDefault: healed.nowDefault ?? null,
+              moved: healed.moved ?? [],
+            }
+          : healed.from === undefined
+            ? null
+            : { ok: false, from: healed.from, reason: healed.reason },
       skeleton: {
         present: skeleton !== null,
         file: skeleton === null ? path.join(dir, SKELETON_FILE) : skeleton.file,
@@ -2333,7 +2357,26 @@ export function apply(ctx, config = {}) {
     const archived = nextArchiveName(id);
     const wasRegistered = await unregister(id);
     fs.renameSync(full, archived);
-    return { ok: true, id, file: full, archived, wasRegistered };
+    /*
+     * Retiring the wife the default names used to leave `selectedDefault` pointing
+     * at nothing, and the registry then refuses EVERY new session with
+     * `agent-preset/not-found` (`registry.js:643`) — so the one operation that
+     * deliberately removes a persona was also the one that could break the next
+     * new task, with the archived file sitting right there as if all were well.
+     * `rename()` has followed its id for a while (`repointDefault`); removing had
+     * no such step.
+     *
+     * Best effort by design: the file is already archived and that must not be
+     * undone because the config write failed, so the outcome is reported instead.
+     */
+    const dropped = await moveDefaultOff(id);
+    const follow =
+      dropped.ok === true
+        ? { defaultFollowed: "cleared", defaultCleared: true }
+        : dropped.skipped === true
+          ? { defaultFollowed: "unchanged" }
+          : { defaultFollowed: "failed", defaultError: dropped.reason };
+    return { ok: true, id, file: full, archived, wasRegistered, ...follow };
   }
 
   /**
@@ -2977,6 +3020,155 @@ export function apply(ctx, config = {}) {
     }
   }
 
+  /**
+   * Move the default off one id, and take the unstarted sessions with it.
+   *
+   * The counterpart of `setDefault` for the case where the id being named can no
+   * longer be used. The registry resolves the default at session creation —
+   * `get defaultId() { return this.config.selectedDefault.get() ?? this.config.default }`
+   * (`registry.js:494`) — and `retain()` throws
+   *
+   *     agent-preset/not-found: Unknown agent preset: <id>
+   *
+   * (`registry.js:643`, same in `resolve()` and `readDocument()`) when nothing
+   * holds it. So a dangling default is not a display problem that sorts itself
+   * out: it blocks EVERY new session, and the refusal comes from the service, so
+   * the composer's own `presets.find(p => p.isDefault)?.id ?? presets[0]?.id`
+   * fallback (`ui-agent-preset.js:1263`) never gets a chance to run.
+   *
+   * Same two steps as `setDefault`, for the same reasons: write through the
+   * settings service so the app re-reads the roster, confirm it by REREADING
+   * rather than by believing the write, and re-seat the blank sessions that were
+   * still following the id being dropped.
+   *
+   * @param {string} from the id the default is expected to hold right now
+   * @param {{ before?: object }} [context] a `refreshDefault({force:true})` the
+   *   caller already did, so this does not have to repeat the read
+   * @returns {Promise<{ ok: boolean, reason: string | null, skipped?: boolean,
+   *   nowDefault?: string | null, via?: string, moved?: string[], refused?: number }>}
+   */
+  async function moveDefaultOff(from, context = {}) {
+    const wanted = oneLine(from);
+    if (wanted === "")
+      return { ok: false, skipped: true, reason: "没有指定默认" };
+    const before = context.before ?? (await refreshDefault({ force: true }));
+    if (oneLine(before.id) !== wanted)
+      return { ok: false, skipped: true, reason: "默认已经不是它了" };
+    const configEditor = ctx.get("configEditor");
+    if (configEditor === undefined || configEditor === null)
+      return {
+        ok: false,
+        reason: "这个环境没有 configEditor 服务，改不了配置。",
+      };
+    let entry;
+    try {
+      entry = findRegistryEntry(configEditor);
+    } catch (error) {
+      return { ok: false, reason: `读不到配置项：${error.message ?? error}` };
+    }
+    if (entry === undefined)
+      return { ok: false, reason: `找不到 ${REGISTRY_PACKAGE} 这条配置项` };
+    const written = await writeDefault({ configEditor, entry, id: null });
+    if (!written.ok) return { ok: false, reason: `清不掉：${written.error}` };
+    const settled = await verifyDefault(null, {
+      previous: before.field,
+      checkable: before.field !== undefined,
+    });
+    if (!settled.verified && settled.checkable)
+      return {
+        ok: false,
+        reason: `写进去了，但读回来还是「${settled.id ?? "（没指定）"}」`,
+      };
+    /*
+     * The field decides what a session created LATER gets; this decides what the
+     * session already sitting on the new-task screen gets. Without it the blank
+     * session keeps the dead id its header was stamped with — a chip naming a
+     * wife that no longer exists, and a creation path that fails for the same
+     * reason the default did.
+     */
+    const resettled = await resettleUnstarted({
+      to: oneLine(cachedDefault.id),
+      from: wanted,
+    });
+    return {
+      ok: true,
+      reason: null,
+      nowDefault: cachedDefault.id,
+      via: written.via,
+      moved: resettled.moved,
+      refused: resettled.refused,
+    };
+  }
+
+  /**
+   * Clear a `selectedDefault` that names a preset nothing registers.
+   *
+   * Run from `status()` (so opening the panel heals), from the boot scan, and
+   * from `remove()`. Each of those is a moment where the default can be seen to
+   * be dead, and the failure it causes is the worst this plugin can produce:
+   * every new session refused with `agent-preset/not-found`, with nothing in the
+   * UI to explain it and nothing to click to get out.
+   *
+   * It only ever clears — never re-points at another wife. Choosing a persona on
+   * the user's behalf would be a different, louder decision than undoing a broken
+   * one, and the profile default is what the field falls back to.
+   *
+   * @returns {Promise<{ healed: string | null, from?: string, reason: string | null,
+   *   nowDefault?: string | null, moved?: string[], refused?: number, via?: string }>}
+   */
+  async function reconcileDefault() {
+    const before = await refreshDefault({ force: true });
+    const picked = oneLine(before.id);
+    if (picked === "")
+      return { healed: null, reason: "没指定默认" };
+    let rows;
+    try {
+      rows = await ctx.agentPresets.list();
+    } catch (error) {
+      return { healed: null, reason: `读不到名册：${error?.message ?? error}` };
+    }
+    if (!Array.isArray(rows)) return { healed: null, reason: "名册没回数组" };
+    /*
+     * An empty roster is 「还没人注册」, not 「谁都指不到」. A plugin that registers
+     * its presets after this row was applied would otherwise have its default
+     * cleared out from under it for no reason — and the cost of waiting is nil,
+     * because `status()` runs this again every time the panel opens.
+     */
+    if (rows.length === 0)
+      return { healed: null, reason: "名册还是空的，先不动" };
+    if (rows.some((row) => oneLine(row?.id) === picked))
+      return { healed: null, reason: "默认指的这个人设还在" };
+    const dropped = await moveDefaultOff(picked, { before });
+    if (!dropped.ok) {
+      // Say it out loud: a default that names nothing blocks every new session,
+      // and failing to repair it silently is exactly how this looked before —
+      // like nothing was wrong until the next new task refused to open.
+      ctx.logger?.warn?.(
+        `dsh-waifu-agents: 默认人设「${picked}」已经不在名册里了（新会话会被 ` +
+          `agent-preset/not-found 直接挡掉），可是清不掉它：${dropped.reason}`,
+      );
+      return { healed: null, from: picked, reason: dropped.reason };
+    }
+    const now = oneLine(dropped.nowDefault);
+    ctx.logger?.warn?.(
+      `dsh-waifu-agents: 默认人设「${picked}」已经不在名册里了（新会话会被 ` +
+        `agent-preset/not-found 直接挡掉），已清掉这条默认，新会话回落到` +
+        `${now === "" ? " profile 默认" : `「${now}」`}` +
+        (dropped.moved.length > 0
+          ? `，顺手把 ${dropped.moved.length} 个还没开口的会话也挪过去了。`
+          : "。"),
+    );
+    return {
+      healed: picked,
+      from: picked,
+      nowDefault: dropped.nowDefault,
+      moved: dropped.moved,
+      refused: dropped.refused,
+      via: dropped.via,
+      reason: null,
+    };
+  }
+
   /** Point the registry's `selectedDefault` at one wife, or at nobody. */
   async function setDefault(request) {
     const id = String(request.id ?? "").trim();
@@ -3485,11 +3677,17 @@ export function apply(ctx, config = {}) {
         defaultSource: cachedDefault.source,
         defaultError: cachedDefault.error,
         // Does the persisted default name a preset this registry actually holds?
-        // The new-task chip stages `presets.find(p => p.isDefault)?.id ??
-        // presets[0].id` (`ui-agent-preset`), so a default that resolves to
-        // nothing silently comes up on the FIRST row — 「我在面板设了默认，新对话
-        // 却不是她」 with no error anywhere. This flag is what lets the panel say
-        // so instead of leaving the user to guess.
+        //
+        // This used to be written down as 「悄悄落到列表第一项」, quoting the
+        // composer's own `fallback = presets.find(p => p.isDefault)?.id ??
+        // presets[0]?.id ?? ""` (`ui-agent-preset.js:1263`). That is the
+        // RENDERER's fallback and it is never reached: the service resolves the
+        // default first, and `retain()` throws
+        // `agent-preset/not-found: Unknown agent preset: <id>` (`registry.js:643`).
+        // So a dangling default does not degrade to the first row — it blocks
+        // EVERY new session outright, with the panel nowhere in the picture and no
+        // row to click. The flag stays; what it means is 「新会话会直接失败」, and
+        // `reconcileDefault()` now clears it instead of only reporting it.
         //
         // `null` when no face named a default at all: that means 「不知道」, not
         // 「指不到人」. Reporting `false` there would accuse a profile that simply
@@ -4145,5 +4343,22 @@ export function apply(ctx, config = {}) {
       ctx.logger?.warn?.(
         `dsh-waifu-agents: 首次扫描失败：${error?.message ?? error}`,
       );
+    })
+    /*
+     * Then the default. `scan()` only ADOPTS files — it never looks at what
+     * `selectedDefault` names — so a persona deleted off disk while the app was
+     * closed leaves the registry pointing at a preset nothing holds, and every
+     * new session is then refused with `agent-preset/not-found`
+     * (`registry.js:643`) with nothing on screen to explain why.
+     *
+     * Chained AFTER the scan rather than run beside it, so the roster already
+     * carries this plugin's own rows: otherwise a `selectedDefault` naming one of
+     * OUR personas would look dangling and be cleared for nothing.
+     */
+    .then(() => reconcileDefault())
+    .catch((error) => {
+      ctx.logger?.warn?.(
+        `dsh-waifu-agents: 默认人设自检失败：${error?.message ?? error}`,
+      );
     });
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-waifu-agents",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "type": "module",
   "description": "Registers every *.md in a persona directory as an agent preset, and manages them from the Plugins settings page.",
   "license": "MIT",
@@ -11,6 +11,9 @@
     "persona",
     "agent-preset"
   ],
+  "scripts": {
+    "test": "node selftest.mjs"
+  },
   "exports": {
     ".": "./index.js",
     "./client": "./client.js",
@@ -44,8 +47,5 @@
         "@deepseek-ai/dsh-client-ui-settings-plugins"
       ]
     }
-  },
-  "scripts": {
-    "test": "node selftest.mjs"
   }
-}
+}

package/selftest.mjs

@@ -869,6 +869,193 @@ check(
 services = {};
 defaultId = null;
 
+console.log('--- a default that names a persona nothing registers ---');
+/*
+ * `selectedDefault` is resolved at session creation, and the SERVICE is the one
+ * that refuses:
+ *
+ *     get defaultId() { return this.config.selectedDefault.get() ?? this.config.default }
+ *     // registry.js:494, feeding retain(id)
+ *     throw new RemoteError("agent-preset/not-found", `Unknown agent preset: ${wanted}`, …)
+ *     // registry.js:643
+ *
+ * so a persona deleted off disk while she was the default does not degrade to the
+ * first row: it blocks EVERY new session, and the panel is not where the user
+ * would think to look. That is 「删掉人设后新开对话直接失败：agent-preset/not-found」.
+ *
+ * Note the sequence — `roster` is read FIRST because it only reports, while
+ * `status` (op: list) is the repair point. Asserting the report after the repair
+ * would assert nothing.
+ */
+const writesBeforeHeal = writes.length;
+const healServices = {
+  settings: {
+    describe: () => [
+      {
+        ns: 'agent-preset-registry',
+        value: { selectedDefault: defaultId ?? '' },
+        revision: writes.length + 1,
+      },
+    ],
+    update: async (ns, patch) => {
+      writes.push({ op: 'update', ns, patch });
+      defaultId = patch.selectedDefault;
+    },
+    mutate: async (ns, ops) => {
+      writes.push({ op: 'mutate', ns, ops });
+      defaultId = null;
+    },
+  },
+  configEditor: {
+    entries: () => [
+      {
+        options: {
+          id: 'agent-preset-registry',
+          name: '@deepseek-ai/dsh-agent-preset-registry',
+        },
+      },
+    ],
+    edit: async () => {
+      throw new Error('configEditor.edit must not be the first choice any more');
+    },
+  },
+};
+services = healServices;
+defaultId = 'ghost-wife';
+check('the ghost really is not registered', !presets.has('ghost-wife'));
+const ghostRoster = await call({ op: 'roster' });
+check(
+  'the roster reports a default that names nothing as not resolving',
+  ghostRoster.defaultResolves === false,
+  JSON.stringify(ghostRoster.defaultResolves),
+);
+check(
+  'and no row is wearing the default badge',
+  ghostRoster.presets.every((row) => row.isDefault !== true),
+  JSON.stringify(ghostRoster.presets.filter((row) => row.isDefault === true)),
+);
+const healedPanel = await call({ op: 'list' });
+check(
+  'opening the panel clears it through settings.mutate',
+  writes.length === writesBeforeHeal + 1 &&
+    writes.at(-1)?.op === 'mutate' &&
+    writes.at(-1)?.ops?.[0]?.op === 'unset' &&
+    writes.at(-1)?.ops?.[0]?.path?.[0] === 'selectedDefault',
+  JSON.stringify(writes.slice(writesBeforeHeal)),
+);
+check(
+  'the repaired default is gone from the registry',
+  defaultId === null,
+  JSON.stringify(defaultId),
+);
+check(
+  'the panel is told what was repaired, and why',
+  healedPanel.defaultHeal?.ok === true &&
+    healedPanel.defaultHeal.from === 'ghost-wife',
+  JSON.stringify(healedPanel.defaultHeal),
+);
+/*
+ * `nowDefault` is the id a new session will actually be stamped with. On this
+ * stub the roster has no `config.default` to fall back on, so it is `null` and
+ * the report says 「回落到 profile 默认」; a real profile resolves `cordis` through
+ * the roster faces and names it instead. Both are the same field.
+ */
+check(
+  'and it names what new sessions will use instead',
+  healedPanel.defaultHeal.nowDefault === null ||
+    typeof healedPanel.defaultHeal.nowDefault === 'string',
+  JSON.stringify(healedPanel.defaultHeal.nowDefault),
+);
+const healedTwice = await call({ op: 'list' });
+check(
+  'a second open writes nothing more',
+  writes.length === writesBeforeHeal + 1,
+  String(writes.length),
+);
+check(
+  'and there is no repair left to report',
+  healedTwice.defaultHeal === null,
+  JSON.stringify(healedTwice.defaultHeal),
+);
+/*
+ * The other half of the contract: a default that DOES resolve must be left
+ * exactly where the user put it. A healer that clears a live default is worse
+ * than the bug it fixes.
+ */
+defaultId = 'alpha';
+const keptDefault = await call({ op: 'list' });
+check(
+  'a default that resolves is never touched',
+  writes.length === writesBeforeHeal + 1 && keptDefault.defaultId === 'alpha',
+  JSON.stringify({ writes: writes.length, id: keptDefault.defaultId }),
+);
+check('and nothing claims to have been repaired', keptDefault.defaultHeal === null);
+/*
+ * The degrade path has to be loud. Without a `configEditor` there is nothing to
+ * write through, and the panel has to say the default is still broken — staying
+ * quiet here is how the next new session fails with no explanation again.
+ */
+services = { settings: healServices.settings };
+defaultId = 'ghost-wife';
+const cannotHeal = await call({ op: 'list' });
+check(
+  'a profile that cannot write keeps the broken default and says so',
+  cannotHeal.defaultHeal?.ok === false &&
+    String(cannotHeal.defaultHeal.reason).includes('configEditor'),
+  JSON.stringify(cannotHeal.defaultHeal),
+);
+check(
+  'and it did not pretend to have written anything',
+  writes.length === writesBeforeHeal + 1 && defaultId === 'ghost-wife',
+  JSON.stringify({ writes: writes.length, defaultId }),
+);
+/*
+ * The other way this default goes dead: retiring her from the panel. `remove()`
+ * archives the file, so the preset leaves the roster — and if she was the
+ * default, the field is left naming nothing.
+ */
+services = healServices;
+const victim = await call({
+  op: 'create',
+  id: 'victim',
+  name: 'Victim',
+  body: 'Victim body.',
+});
+defaultId = 'victim';
+const removedDefault = await call({ op: 'remove', id: 'victim' });
+check(
+  'retiring the default persona clears the default with it',
+  removedDefault.defaultFollowed === 'cleared' &&
+    removedDefault.defaultCleared === true &&
+    defaultId === null,
+  JSON.stringify({ removedDefault, defaultId }),
+);
+check(
+  'and she is archived rather than deleted, as always',
+  fs.existsSync(path.join(tmp, 'victim.md.off')),
+);
+/*
+ * Blast radius: removing somebody else must not move the user's default. This is
+ * the assertion that keeps `remove()` from becoming a general-purpose healer.
+ */
+const bystander = await call({
+  op: 'create',
+  id: 'bystander',
+  name: 'Bystander',
+  body: 'Bystander body.',
+});
+defaultId = 'alpha';
+const removedBystander = await call({ op: 'remove', id: 'bystander' });
+check(
+  'retiring anyone else leaves the default where it is',
+  removedBystander.defaultFollowed === 'unchanged' &&
+    removedBystander.defaultCleared === undefined &&
+    defaultId === 'alpha',
+  JSON.stringify({ removedBystander, defaultId }),
+);
+services = {};
+defaultId = null;
+
 console.log('--- the session already on screen is re-seated, not just future ones ---');
 /*
  * Writing `selectedDefault` decides what a session created LATER is stamped
@@ -1945,6 +2132,21 @@ check(
   'the persona picker and the @ source are both wired',
   clientSource.includes('commandUi.decorate') && clientSource.includes('registerSource'),
 );
+/*
+ * The repair report has three outcomes and the panel has to be able to draw all
+ * three: cleared and falling back to the profile default, cleared onto a named
+ * persona, and NOT cleared (which leaves new sessions still refusing to open, so
+ * it is the one that must never be silent).
+ */
+check(
+  'the repair report can draw every outcome it can be handed',
+  clientSource.includes("t('defaultHealed')") &&
+    clientSource.includes("t('defaultHealedNobody')") &&
+    clientSource.includes("t('defaultHealedMoved')") &&
+    clientSource.includes("t('defaultHealFailed')") &&
+    clientSource.includes('data?.defaultHeal != null'),
+  'the default-repair notice is not wired',
+);
 check(
   'every icon the panel asks for is in the bridge table',
   (() => {