dsh-connect-trae 4.4.5 → 4.4.6

package/CHANGELOG.md

@@ -1,5 +1,76 @@
 # Changelog
 
+## 4.4.6 (2026-10-24)
+
+> **对齐宿主 DSH 0.2.1-rc.3（纯版本推进，插件代码零改动），并修掉账号链路上三处
+> 会静默丢数据的问题——其中一处可能正是 #56「被顶掉的账号若干时间后消失」的成因。**
+>
+> 宿主这一版只落地 5 个提交：三个是「导航项自定义」（面板固定/取消固定、More 菜单、埋点），
+> 一个是 DeepSeek API-key 通道改走官方 `/models` 目录，一个是版本号——**均与本插件不相干**。
+> 插件消费的 13 个宿主包里只有 `dsh-client-ui-primitives` 有代码变化，且全是新增，
+> 而本插件对它只有类型层引用，因此**不需要任何适配**。
+>
+> 真正的风险在插件自己身上：一份读不懂的副本文件会被当成「一个账号都没有」，
+> 而三条合并写路径又以它为基底——一次损坏读 + 一次刷新 = 其余账号的副本被无声抹掉。
+
+### 修复
+
+- **副本文件损坏不再清掉全部账号**（`fix(auth)`，PR #58）。
+  `parseOwn` 此前对「无法解析的文件」（半截写入、手改损坏、未知版本）一律返回空数组，而镜像 /
+  刷新 / 导入三条合并写路径都以它的结果为合并基底——一次损坏读 + 下一次刷新 = **其余全部账号的
+  副本被无声抹掉**，账号行随下一个轮询消失，且因为异常全被吞掉，日志里什么都看不到。
+  - `parseOwn` 改为三态（合法 / 合法空 / **无法解析返回 `undefined`**），新增 `readOwnForMerge`
+    收口三条写路径：遇到无法解析的文件先隔离为 `.corrupt-<时间戳>`（字节保留、可找回），
+    再从干净文件开始；**隔离失败则放弃本次写入，绝不覆盖读不懂的字节**。
+  - `deleteAccount` 对不可解析文件**拒绝**而非当空。
+  - 这可能是 #56（被顶掉的账号若干时间后消失）的一种成因——值得让报告者检查
+    `$DSH_HOME/.trae-auth.cn.json` 及其同目录的 `.corrupt-*` 隔离文件。
+- **墓碑读-改-写收进一把锁**（`fix(auth)`，PR #58）。墓碑文件被两个并发流读改写：镜像
+  （清失效墓碑）与删除（加墓碑），此前都是锁外读、锁内写，丢更新的两个方向都疼——丢一个墓碑＝
+  已删账号在下一轮镜像复活；丢一次清理＝墓碑永久残留，该账号之后永远无法再被镜像。
+  收口为锁内 `updateTombstones(mutator)`。
+- **池测量的删除不再丢并发写入**（`fix(pool)`，PR #58）。`dropTraePoolProbe` 的读取挪进锁内
+  （对齐同文件 `writeTraePoolProbes` 的范式）：此前锁外读的快照会把并发批次刚写入的测量覆盖掉。
+
+### 变更
+
+- **对齐宿主 DSH 0.2.1-rc.3**：13 个 `@deepseek-ai/dsh-*` devDependency 从 `0.2.1-rc.2`
+  推进到 `0.2.1-rc.3`。`cordis`（`4.0.5`）/ `schemastery`（`3.18.5`）/ `pi-ai`（仍 `1.1.0`）
+  均未变——宿主 `app.asar` 实测随包的 pi-ai 仍是 1.1.0，3.4.2 起的双向适配结论原样成立。
+- **peer 范围无需改动**：`0.2.1-rc.3` 对 `>=0.1.7-rc.1 <0.3.0-0` 已判通过（实测）。
+- **插件代码零改动**：rc.3 对本插件消费的 13 个宿主包里，只有 `dsh-client-ui-primitives`
+  存在代码变化，且全部是**新增**（`TooltipSide` 增加 `'left'` 并改用实测边框盒换边放置、
+  `MenuItemButton` 增加 `current`、`Menu` 增加 `minWidthFromAnchor`、新增 `IconAppsAddOutline*`）。
+  本插件对 `dsh-client-ui-primitives` 只有**类型层引用**（`import type {} from ...`），
+  运行时不消费这些组件，故无需适配。
+
+### 已核对确认无变化
+
+- 逐字节比对 npm 上 `0.2.1-rc.2` 与 `0.2.1-rc.3` 两版的全量文件树：
+  `dsh-llm`、`dsh-llm-pi-ai`、`dsh-settings`、`dsh-host-webserver`、`dsh-atomic-write`、
+  `dsh-home-paths`、`dsh-attachment`、`dsh-client-ui-renderer`、`dsh-client-ui-settings`、
+  `dsh-client-ui-settings-plugins`、`dsh-client-ui-slots`、`dsh-client-locale`
+  ——**除 package.json 的版本号与内部依赖号外逐字节相同**。
+- 本插件注册的 5 个槽位（`plugins.bundle.config`、`plugins.row.config`、`conversation.input.left`、
+  `conversation.composer.dock`、`conversation.input.model.label`）在 rc.3 中**仍然存在且契约未变**；
+  宿主新增的 `conversation.session.header.views.actions` 等槽位与本插件无交集。
+- rc.3 宿主上实测：宿主侧 Config 条目 `include:dsh-connect-trae` 在册，客户端
+  `plugins.bundle.config` / `plugins.row.config` / `conversation.input.left` 三处注册均 active。
+
+### 测试
+
+- PR #58 新增回归用例：损坏副本文件被隔离且字节保留、合法文件中坏一行只丢该行、
+  隔离失败时放弃写入且原字节不动、墓碑并发删除/写入序列化冒烟、池测量的 drop 与 write 不互相覆盖。
+- `tests/dsh-peer-range.spec.ts` 的 `MUST_ADMIT` 补入 `0.2.1-rc.3`——此前这份「必须放行的版本」
+  清单里没有当前正在使用的版本，范围若被误收窄到当前宿主之外，测试仍会全绿。
+- 全仓 **1084** 例通过（84 个测试文件），双 tsconfig 类型检查通过。
+
+### 文档
+
+- 新增 `docs/DSH_0.2.1_RC1_SYNC.md` 第十节：`0.2.1-rc.3` 复核记录（取证、依赖面、契约面、
+  槽位核对、peer 门禁）。
+- `README.md` / `README.en.md` 的宿主版本结论推进到 `0.2.1-rc.3`，并新增
+  「`0.2.1-rc.3` 同步结论」小节。
 ## 4.4.5 (2026-10-23)
 
 > **模型列表不再倒出官方已下架的历史配置：按 Trae IDE 名册退役 12 行、改钉 6 行，

package/README.en.md

@@ -153,7 +153,7 @@ Restart the DSH process after install/update/uninstall.
 ## DSH version compatibility
 
 **Requires DSH 0.1.7-rc.1 and up** (since 2.3.0 the plugin no longer targets hosts older than 0.1.7; the peer dependency ranges are narrowed accordingly).
-**The peer upper bound is `<0.3.0-0`, so both the 0.1.7 and the 0.2 line are supported (including 0.2.1-rc.2, verified).**
+**The peer upper bound is `<0.3.0-0`, so both the 0.1.7 and the 0.2 line are supported (including 0.2.1-rc.3, verified).**
 
 ### Both pi-ai context generations are supported (since 3.4.2)
 
@@ -178,13 +178,26 @@ The 0.2.0 line breaks **no** contract this plugin consumes — a symbol-by-symbo
 
 ### DSH 0.2.1 line (pi-ai 1.1.0) sync
 
-The `0.2.1-rc.1` host moved `@earendil-works/pi-ai` from `^0.85.1` to **`^1.1.0`** (unchanged through `0.2.1-rc.2`) — the only change on the 0.2 line with real behavioural impact. Three conclusions:
+The `0.2.1-rc.1` host moved `@earendil-works/pi-ai` from `^0.85.1` to **`^1.1.0`** (unchanged through `0.2.1-rc.2` and `0.2.1-rc.3`) — the only change on the 0.2 line with real behavioural impact. Three conclusions:
 
 1. **The request body did not regress (measured, not inferred).** The 1.1.0 api reads the prompt **only** from a transcript system message and never touches top-level `systemPrompt` / `tools`, while `dsh-llm-pi-ai`'s `piContext()` still emits the legacy envelope. The bidirectional adapter this plugin has shipped since 3.4.2 covers exactly that: feeding the real host envelope through real `1.1.0` with a local SSE capture yields `roles: ["system","user"]`, an intact system text and `tools: 1`; **without the adapter it degenerates to `roles: ["user"]`, system `null`, `tools: 0`** — with no error. That contrast is pinned as a wire-level matrix in `tests/pi-ai-context.spec.ts`.
 2. **Types were fixed.** 1.1.0 changed `ProviderStreams`' second parameter to a **branded** `TranscriptContext` (a `unique symbol` only `normalizeContext()` can produce). The adapter casts once at that single boundary (`withContextAdaptation` in `src/adapter.ts`) and documents why the brand cannot be obtained honestly there.
-3. **The peer range needed no change.** DSH evaluates with `semver.satisfies(runtime, range, { includePrerelease: true })` and checks only the `@deepseek-ai/dsh*` namespace, so `>=0.1.7-rc.1 <0.3.0-0` already admits both `0.2.1-rc.1` and `0.2.1-rc.2` (verified). Note the prerelease cliff only exists under **default** options — it is not this plugin's situation.
+3. **The peer range needed no change.** DSH evaluates with `semver.satisfies(runtime, range, { includePrerelease: true })` and checks only the `@deepseek-ai/dsh*` namespace, so `>=0.1.7-rc.1 <0.3.0-0` already admits `0.2.1-rc.1`, `0.2.1-rc.2` and `0.2.1-rc.3` (verified). Note the prerelease cliff only exists under **default** options — it is not this plugin's situation.
 
-The dev tree pins `@earendil-works/pi-ai` at exactly **1.1.0** (the version the host actually bundles) rather than `^1.1.0`, so local typecheck and tests run against the same contract users do; the `schemastery` override moved to `3.18.5` (`dsh-llm-pi-ai@0.2.1-rc.2` declares `~3.18.5`).
+The dev tree pins `@earendil-works/pi-ai` at exactly **1.1.0** (the version the host actually bundles — still 1.1.0 on `0.2.1-rc.3`) rather than `^1.1.0`, so local typecheck and tests run against the same contract users do; the `schemastery` override moved to `3.18.5` (`dsh-llm-pi-ai@0.2.1-rc.3` declares `~3.18.5`).
+
+### `0.2.1-rc.3` sync (since 4.4.6)
+
+The host moved to `0.2.1-rc.3` (the desktop app's `CFBundleVersion` and the bundled `dsh-desktop-runtime` both report `0.2.1-rc.3`). Upstream shipped five commits: three of them are the new "navigation entry customization" UI (pin/unpin plugin launchers, a More menu, analytics), one switches the DeepSeek API-key route to the official `/models` listing, one is the version bump.
+
+For **this plugin**:
+
+- Of the 13 host packages the plugin consumes, **only `dsh-client-ui-primitives` changed code**, and every change is **additive**: `Tooltip`'s `TooltipSide` gains `'left'` and now places the bubble from measured border boxes (preferred → opposite → perpendicular side), `MenuItemButton` gains `current`, `Menu` gains `minWidthFromAnchor`, and the icon set gains `IconAppsAddOutline*`. This plugin references `dsh-client-ui-primitives` **at the type level only** (`import type {} from ...`) and never touches those components at runtime, so **no adaptation is needed**.
+- The other 12 packages (`dsh-llm`, `dsh-llm-pi-ai`, `dsh-settings`, `dsh-host-webserver`, `dsh-atomic-write`, `dsh-home-paths`, `dsh-attachment`, `dsh-client-ui-renderer`, `dsh-client-ui-settings`, `dsh-client-ui-settings-plugins`, `dsh-client-ui-slots`, `dsh-client-locale`) are **byte-for-byte unchanged**.
+- Every slot this plugin registers (`plugins.bundle.config`, `plugins.row.config`, `conversation.input.left`, `conversation.composer.dock`, `conversation.input.model.label`) **still exists with an unchanged contract** on rc.3; the host's new slots (e.g. `conversation.session.header.views.actions`) do not overlap with them.
+- The peer range **needs no change**: `0.2.1-rc.3` is admitted by `>=0.1.7-rc.1 <0.3.0-0` (verified).
+
+Details: [section 10 of `docs/DSH_0.2.1_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.1_RC1_SYNC.md).
 
 
 ### Why the upper bound is not `<0.2.0`

package/README.md

@@ -172,7 +172,7 @@ npm install dsh-connect-trae
 ## DSH 版本兼容
 
 **要求 DSH 0.1.7-rc.1 及以上**（2.3.0 起不再支持 0.1.7 之前的宿主；peer 依赖范围已按此收窄）。
-**peer 上界为 `<0.3.0-0`：0.1.7 与 0.2 两条线均受支持（含 0.2.1-rc.2，已实测）。**
+**peer 上界为 `<0.3.0-0`：0.1.7 与 0.2 两条线均受支持（含 0.2.1-rc.3，已实测）。**
 
 ### 同时支持 pi-ai 的两代上下文（3.4.2 起）
 
@@ -206,7 +206,7 @@ peer 范围不满足的 bundle 会被**整体跳过**，只往 stderr 写一行
 
 ### DSH 0.2.1 线（pi-ai 1.1.0）同步结论
 
-宿主 `0.2.1-rc.1` 把 `@earendil-works/pi-ai` 从 `^0.85.1` 抬到了 **`^1.1.0`**（`0.2.1-rc.2` 保持不变），这是 0.2 线里
+宿主 `0.2.1-rc.1` 把 `@earendil-works/pi-ai` 从 `^0.85.1` 抬到了 **`^1.1.0`**（`0.2.1-rc.2` / `0.2.1-rc.3` 均保持不变），这是 0.2 线里
 唯一有实际行为影响的变化。三项结论：
 
 1. **请求体没有丢东西（已实测）**。1.1.0 的 api **只**读 transcript 里的 system 消息，
@@ -219,13 +219,36 @@ peer 范围不满足的 bundle 会被**整体跳过**，只往 stderr 写一行
    `TranscriptContext`，只有 `normalizeContext()` 能产出。适配层在这条边界上做一次显式转型
    （`src/adapter.ts` 的 `withContextAdaptation`），并在两处调用点写明为何品牌在此处不可诚实获得。
 3. **peer 范围无需改动**。DSH 用 `semver.satisfies(runtime, range, { includePrerelease: true })`
-   求值，且只校验 `@deepseek-ai/dsh*` 命名空间，因此 `>=0.1.7-rc.1 <0.3.0-0` 对 `0.2.1-rc.1` / `0.2.1-rc.2` 均已判通过
+   求值，且只校验 `@deepseek-ai/dsh*` 命名空间，因此 `>=0.1.7-rc.1 <0.3.0-0` 对 `0.2.1-rc.1` / `0.2.1-rc.2` / `0.2.1-rc.3` 均已判通过
    （已实测）。**注意**：预发布悬崖只在**默认选项**下成立——那是 `dsh-connect-workbuddy` 侧
    调研文档所描述的困境，本插件不适用。
 
-开发树的 `@earendil-works/pi-ai` 钉在 **1.1.0**（宿主实际随包的版本）而非 `^1.1.0`，
+开发树的 `@earendil-works/pi-ai` 钉在 **1.1.0**（宿主实际随包的版本，`0.2.1-rc.3` 实测仍是 1.1.0）而非 `^1.1.0`，
 使本地 typecheck 与测试跑在与用户完全一致的契约上；`schemastery` 的 override 同步抬到
-`3.18.5`（`dsh-llm-pi-ai@0.2.1-rc.2` 声明 `~3.18.5`）。
+`3.18.5`（`dsh-llm-pi-ai@0.2.1-rc.3` 声明 `~3.18.5`）。
+
+### `0.2.1-rc.3` 同步结论（4.4.6 起）
+
+宿主推进到 `0.2.1-rc.3`（桌面版 `CFBundleVersion` 与随包 `dsh-desktop-runtime` 同为 `0.2.1-rc.3`）。
+上游这一版只落地了 5 个提交，其中 3 个是 UI 的「导航项自定义」（插件化面板的固定/取消固定、
+More 菜单、埋点），1 个是 DeepSeek API-key 通道改走官方 `/models` 目录，1 个是版本号。
+
+对**本插件**而言：
+
+- 插件消费的 13 个宿主包里，**只有 `dsh-client-ui-primitives` 有代码变化**，且**全是新增**：
+  `Tooltip` 的 `TooltipSide` 增加 `'left'` 并改用实测边框盒做「首选 → 对侧 → 垂直侧」的换边放置，
+  `MenuItemButton` 增加 `current`、`Menu` 增加 `minWidthFromAnchor`，图标新增 `IconAppsAddOutline*`。
+  本插件对 `dsh-client-ui-primitives` 只有**类型层引用**（`import type {} from ...`），
+  运行时不碰这些组件，**无需任何适配**。
+- 其余 12 个包（`dsh-llm`、`dsh-llm-pi-ai`、`dsh-settings`、`dsh-host-webserver`、`dsh-atomic-write`、
+  `dsh-home-paths`、`dsh-attachment`、`dsh-client-ui-renderer`、`dsh-client-ui-settings`、
+  `dsh-client-ui-settings-plugins`、`dsh-client-ui-slots`、`dsh-client-locale`）**逐字节未变**。
+- 插件注册的全部槽位（`plugins.bundle.config`、`plugins.row.config`、`conversation.input.left`、
+  `conversation.composer.dock`、`conversation.input.model.label`）在 rc.3 中**仍然存在且契约未变**；
+  宿主新增的 `conversation.session.header.views.actions` 等槽位与本插件无交集。
+- peer 范围**无需改动**：`0.2.1-rc.3` 对 `>=0.1.7-rc.1 <0.3.0-0` 已判通过（已实测）。
+
+细节见 [`docs/DSH_0.2.1_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.1_RC1_SYNC.md) 第十节。
 
 
 ### peer 上界为什么不写 `<0.2.0`

package/lib/index.d.ts

@@ -1889,7 +1889,40 @@ declare class TraeCredentialStore {
    * account, it never locks the user out.
    */
   private readTombstones;
-  private writeTombstones;
+  /**
+   * Read, mutate, and write the tombstone list under ONE lock.
+   *
+   * The tombstone file is read-modify-write state shared by two flows that run
+   * concurrently: `mirrorLocalLogins` (drops tombstones whose logins are gone)
+   * and `deleteAccount` (adds the id just deleted). A read OUTSIDE the write's
+   * lock loses updates in both directions — a dropped-add resurrects a deleted
+   * account on the next mirror, a dropped-drop keeps a tombstone forever and
+   * hides every future sign-in of that account. The mutator therefore runs on
+   * the freshly-read set INSIDE the lock, and what it returns is what gets
+   * written, with no window in between.
+   *
+   * Fire-and-forget safe: a failed update only delays a tombstone change until
+   * the next mirror or delete, so errors are swallowed like the readers'.
+   */
+  private updateTombstones;
+  /**
+   * Read the plugin-owned file as the merge base for a read-modify-write.
+   *
+   * This is the fail-safe that keeps one unreadable file from erasing every
+   * account: `parseOwn` now distinguishes a VALID empty file (`[]`) from one
+   * this build cannot parse (`undefined`), and only the former may serve as a
+   * merge base. For the latter the file is quarantined — renamed aside with
+   * its bytes intact — and the merge then starts from nothing, so the action
+   * the user pressed still succeeds and the lost entries are recoverable from
+   * the quarantine copy instead of being overwritten silently. A quarantine
+   * that fails (an exotic filesystem, a name collision) aborts the write
+   * instead: losing one refresh is recoverable by pressing it again, losing
+   * every account is not.
+   *
+   * Every caller must hold the {@link withFileLock} of `path` across BOTH the
+   * read and the subsequent write — this does not lock by itself.
+   */
+  private readOwnForMerge;
   /**
    * Copy every local Trae sign-in into this store's own file, once.
    *

package/lib/index.js

@@ -6,7 +6,7 @@ import { PiAiAdapter } from "@deepseek-ai/dsh-llm-pi-ai";
 import { existsSync, readFileSync } from "node:fs";
 import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
-import { copyFile, readFile, rm, stat } from "node:fs/promises";
+import { copyFile, readFile, rename, rm, stat } from "node:fs/promises";
 import { createCipheriv, createDecipheriv, createHash, randomBytes, randomUUID, sign, timingSafeEqual } from "node:crypto";
 import { withFileLock, writeFileAtomic } from "@deepseek-ai/dsh-atomic-write";
 import { resolveDshHome } from "@deepseek-ai/dsh-home-paths";
@@ -2223,21 +2223,55 @@ function credentialOfStored(stored) {
 * needed and an older install's file is never rejected. A malformed row is
 * dropped rather than failing the whole file — one bad imported account must
 * not hide the rest.
+*
+* Returns `undefined` — NOT an empty array — for a file this build cannot parse
+* at all: a torn JSON write, a hand-edited document, or a version nothing here
+* knows. The distinction is load-bearing (see {@link readOwnForMerge}): every
+* merge writer treats `[]` as the merge base but `undefined` as "do not build
+* on this", because an unparseable file may still HOLD every account, and
+* merging onto "empty" would erase them on the very next refresh.
 */
 function parseOwn(text) {
+	let document;
 	try {
-		const document = JSON.parse(text);
-		if (document.version === OWN_VERSION) {
-			if (!Array.isArray(document.credentials)) return [];
-			return document.credentials.map(credentialOfStored).filter((value) => value !== void 0);
-		}
-		if (document.version === OWN_VERSION_SINGLE) {
-			const single = credentialOfStored(document.credential);
-			return single === void 0 ? [] : [single];
-		}
-		return [];
+		const parsed = JSON.parse(text);
+		if (typeof parsed !== "object" || parsed === null || Array.isArray(parsed)) return void 0;
+		document = parsed;
+	} catch {
+		return;
+	}
+	if (document.version === OWN_VERSION) {
+		if (!Array.isArray(document.credentials)) return void 0;
+		return document.credentials.map(credentialOfStored).filter((value) => value !== void 0);
+	}
+	if (document.version === OWN_VERSION_SINGLE) {
+		const single = credentialOfStored(document.credential);
+		return single === void 0 ? void 0 : [single];
+	}
+}
+/**
+* Move a plugin-owned file this build can no longer parse out of the way, so
+* the next write starts from a clean file instead of building on — or being
+* refused by — the unreadable one.
+*
+* The rename is the data preservation: the bytes stay on disk beside the live
+* path (`.corrupt-<stamp>`), so a future build that understands the format (or
+* a user with a text editor) can still recover the accounts it carried. It is
+* best-effort on purpose: a quarantine that cannot happen must not fail the
+* user action that triggered it, and the merge writers refuse to overwrite a
+* file they could not quarantine (see {@link readOwnForMerge}).
+*
+* Must be called under the same lock the caller writes under: without the lock
+* the rename could interleave with a concurrent writer holding the pre-rename
+* content and write it right back.
+*/
+async function quarantineCorruptOwn(path) {
+	const stamp = (/* @__PURE__ */ new Date()).toISOString().replace(/[:.]/g, "-");
+	try {
+		await rename(path, `${path}.corrupt-${stamp}`);
+		return true;
 	} catch {
-		return [];
+		return false;
 	}
 }
 /**
@@ -2415,9 +2449,26 @@ var TraeCredentialStore = class {
 			return /* @__PURE__ */ new Set();
 		}
 	}
-	async writeTombstones(ids) {
+	/**
+	* Read, mutate, and write the tombstone list under ONE lock.
+	*
+	* The tombstone file is read-modify-write state shared by two flows that run
+	* concurrently: `mirrorLocalLogins` (drops tombstones whose logins are gone)
+	* and `deleteAccount` (adds the id just deleted). A read OUTSIDE the write's
+	* lock loses updates in both directions — a dropped-add resurrects a deleted
+	* account on the next mirror, a dropped-drop keeps a tombstone forever and
+	* hides every future sign-in of that account. The mutator therefore runs on
+	* the freshly-read set INSIDE the lock, and what it returns is what gets
+	* written, with no window in between.
+	*
+	* Fire-and-forget safe: a failed update only delays a tombstone change until
+	* the next mirror or delete, so errors are swallowed like the readers'.
+	*/
+	async updateTombstones(mutator) {
 		const path = this.deletedPath();
 		await withFileLock(path, async () => {
+			const ids = await this.readTombstones();
+			mutator(ids);
 			await writeFileAtomic(path, `${JSON.stringify({
 				version: 1,
 				ids: [...ids]
@@ -2425,7 +2476,31 @@ var TraeCredentialStore = class {
 				mode: 384,
 				dirMode: 448
 			});
-		});
+		}).catch(() => void 0);
+	}
+	/**
+	* Read the plugin-owned file as the merge base for a read-modify-write.
+	*
+	* This is the fail-safe that keeps one unreadable file from erasing every
+	* account: `parseOwn` now distinguishes a VALID empty file (`[]`) from one
+	* this build cannot parse (`undefined`), and only the former may serve as a
+	* merge base. For the latter the file is quarantined — renamed aside with
+	* its bytes intact — and the merge then starts from nothing, so the action
+	* the user pressed still succeeds and the lost entries are recoverable from
+	* the quarantine copy instead of being overwritten silently. A quarantine
+	* that fails (an exotic filesystem, a name collision) aborts the write
+	* instead: losing one refresh is recoverable by pressing it again, losing
+	* every account is not.
+	*
+	* Every caller must hold the {@link withFileLock} of `path` across BOTH the
+	* read and the subsequent write — this does not lock by itself.
+	*/
+	async readOwnForMerge(path) {
+		const text = await readFile(path, "utf8").catch(() => void 0);
+		if (text === void 0) return [];
+		const parsed = parseOwn(text);
+		if (parsed !== void 0) return parsed;
+		return await quarantineCorruptOwn(path) ? [] : void 0;
 	}
 	/**
 	* Copy every local Trae sign-in into this store's own file, once.
@@ -2447,20 +2522,17 @@ var TraeCredentialStore = class {
 		const { credentials: discovered } = await this.readDesktopAll();
 		const own = await this.readOwns();
 		const ownIds = new Set(own.map((credential) => traeAccountId(credential)));
-		const tombstones = await this.readTombstones();
 		const liveIds = new Set(discovered.map((credential) => traeAccountId(credential)));
-		let tombstonesChanged = false;
-		for (const id of [...tombstones]) {
-			if (liveIds.has(id)) continue;
-			tombstones.delete(id);
-			tombstonesChanged = true;
-		}
+		const tombstones = await this.readTombstones();
+		if ([...tombstones].some((id) => !liveIds.has(id))) await this.updateTombstones((ids) => {
+			for (const id of [...ids]) if (!liveIds.has(id)) ids.delete(id);
+		});
 		const missing = discovered.filter((credential) => this.matchesRegion(credential) && !ownIds.has(traeAccountId(credential)) && !tombstones.has(traeAccountId(credential)));
-		if (tombstonesChanged) await this.writeTombstones(tombstones);
 		if (missing.length === 0) return;
 		const ownPath = this.ownAuthPath();
 		await withFileLock(ownPath, async () => {
-			const existing = await readFile(ownPath, "utf8").then(parseOwn, () => []);
+			const existing = await this.readOwnForMerge(ownPath);
+			if (existing === void 0) return;
 			const byId = new Map(existing.map((credential) => [traeAccountId(credential), credential]));
 			for (const credential of missing) {
 				const id = traeAccountId(credential);
@@ -2748,7 +2820,8 @@ var TraeCredentialStore = class {
 		const ownPath = this.ownAuthPath();
 		const written = [];
 		await withFileLock(ownPath, async () => {
-			const existing = await readFile(ownPath, "utf8").then(parseOwn, () => []);
+			const existing = await this.readOwnForMerge(ownPath);
+			if (existing === void 0) return;
 			const byId = /* @__PURE__ */ new Map();
 			for (const item of existing) byId.set(traeAccountId(item), item);
 			for (const credential of credentials) {
@@ -2907,7 +2980,7 @@ var TraeCredentialStore = class {
 		let mutated = false;
 		for (const path of this.ownCandidates()) {
 			const dropped = await withFileLock(path, async () => {
-				const existing = await readFile(path, "utf8").then(parseOwn, () => null);
+				const existing = await readFile(path, "utf8").then((text) => parseOwn(text) ?? null, () => null);
 				if (existing === null || !existing.some((credential) => traeAccountId(credential) === accountId)) return false;
 				const next = existing.filter((credential) => traeAccountId(credential) !== accountId);
 				await writeOwn(path, next);
@@ -2915,11 +2988,9 @@ var TraeCredentialStore = class {
 			}).catch(() => false);
 			mutated = mutated || dropped;
 		}
-		const tombstones = await this.readTombstones();
-		if (!tombstones.has(accountId)) {
-			tombstones.add(accountId);
-			await this.writeTombstones(tombstones).catch(() => void 0);
-		}
+		await this.updateTombstones((ids) => {
+			ids.add(accountId);
+		});
 		if (this.accountId === accountId) {
 			this.accountId = void 0;
 			this.inflight = void 0;
@@ -3039,7 +3110,8 @@ var TraeCredentialStore = class {
 	async readOwns() {
 		const copies = [];
 		for (const path of this.ownCandidates()) try {
-			copies.push(...parseOwn(await readFile(path, "utf8")));
+			const parsed = parseOwn(await readFile(path, "utf8"));
+			if (parsed !== void 0) copies.push(...parsed);
 		} catch {}
 		return copies;
 	}
@@ -3061,7 +3133,8 @@ var TraeCredentialStore = class {
 			};
 			const ownPath = this.ownAuthPath();
 			await withFileLock(ownPath, async () => {
-				const existing = await readFile(ownPath, "utf8").then(parseOwn, () => []);
+				const existing = await this.readOwnForMerge(ownPath);
+				if (existing === void 0) return;
 				const refreshedId = traeAccountId(refreshed);
 				const entries = existing.filter((item) => traeAccountId(item) !== refreshedId);
 				entries.push(refreshed);
@@ -9254,24 +9327,28 @@ async function writeTraePoolProbes(panel, updates) {
 * member, and leaving it in the file would resurrect a stale `rate-limited` row if
 * the account were added back later. Written through the same lock/atomic path so a
 * removal cannot interleave with a batch.
+*
+* The READ also sits inside the lock, like {@link writeTraePoolProbes}'s: a
+* delete is a read-modify-write, and a read taken outside the lock snapshots a
+* moment that a concurrent batch's write can then be older than — the delete
+* would write that stale snapshot back and silently discard the measurements
+* the batch had just learned.
 */
 async function dropTraePoolProbe(panel, accountId) {
-	const existing = await readTraePoolProbes(panel);
-	if (existing[accountId] === void 0) return;
 	const path = traePoolStorePath(panel);
-	const probes = {};
-	for (const [id, probe] of Object.entries(existing)) if (id !== accountId) probes[id] = probe;
-	try {
-		await withFileLock(path, async () => {
-			await writeFileAtomic(path, `${JSON.stringify({
-				version: STORE_FORMAT_VERSION,
-				probes
-			}, null, 2)}\n`, {
-				mode: 384,
-				dirMode: 448
-			});
+	await withFileLock(path, async () => {
+		const existing = await readTraePoolProbes(panel);
+		if (existing[accountId] === void 0) return;
+		const probes = {};
+		for (const [id, probe] of Object.entries(existing)) if (id !== accountId) probes[id] = probe;
+		await writeFileAtomic(path, `${JSON.stringify({
+			version: STORE_FORMAT_VERSION,
+			probes
+		}, null, 2)}\n`, {
+			mode: 384,
+			dirMode: 448
 		});
-	} catch {}
+	}).catch(() => {});
 }
 //#endregion
 //#region src/model-config.ts

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "4.4.5",
+  "version": "4.4.6",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",
@@ -94,19 +94,19 @@
   },
   "devDependencies": {
     "@deepseek-ai/cordis": "^4.0.5",
-    "@deepseek-ai/dsh-atomic-write": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-attachment": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-locale": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-primitives": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-renderer": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-home-paths": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-host-webserver": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-llm": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-llm-pi-ai": "0.2.1-rc.2",
-    "@deepseek-ai/dsh-settings": "0.2.1-rc.2",
+    "@deepseek-ai/dsh-atomic-write": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-attachment": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-locale": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-ui-renderer": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-ui-settings": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-home-paths": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-host-webserver": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-llm": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-llm-pi-ai": "0.2.1-rc.3",
+    "@deepseek-ai/dsh-settings": "0.2.1-rc.3",
     "@deepseek-ai/schemastery": "3.18.5",
     "@earendil-works/pi-ai": "1.1.0",
     "@testing-library/dom": "^10.4.2",