dsh-connect-trae 3.6.0 → 3.7.0

package/CHANGELOG.md

@@ -1,5 +1,74 @@
 # Changelog
 
+## 3.7.0 (2026-10-17)
+
+> **对齐 DSH 0.2.1-rc.1。** 宿主把 `@earendil-works/pi-ai` 从 `^0.85.1` 抬到 `^1.1.0`，
+> 这是 0.2 线里唯一有行为影响的变更。本插件的请求体**没有**回归——但那是靠 3.4.2 的双向适配
+> 兜住的，本版把这条结论从「推理」变成「被测住的对照」。
+
+### 变更
+
+- **开发树对齐宿主实际随包版本**：13 个 `@deepseek-ai/dsh-*` devDependency 固定为 `0.2.1-rc.1`，
+  `cordis` → `^4.0.5`，`schemastery` → `3.18.5`（`pnpm-workspace.yaml` 的 override 同步抬升），
+  `@earendil-works/pi-ai` → **`1.1.0`（精确固定，不用 `^`）**，使本地 typecheck 与测试
+  跑在与用户**字节一致**的契约上。
+- **`@earendil-works/pi-ai` peer 上界收窄为 `<2.0.0`**：原先 `>=0.85.1` 无上界，会默默放行
+  未审阅的 2.x。两端均已实测（0.85.1 ✅、1.1.0 ✅、1.3.0 ✅、2.0.0 ❌）。
+
+### 修复
+
+- **pi-ai 1.1.0 的类型契约**：1.1.0 把 `ProviderStreams` 的第二参改成带 `unique symbol`
+  品牌标记的 `TranscriptContext`，只有 `normalizeContext()` 能产出，于是 `withContextAdaptation`
+  在两处调用点报 `TS2345`（升级后才暴露，0.85.1 下类型可通）。适配层本来就在归一化器
+  **下方**、且旧代分支**必须**产出无品牌形状，所以在这唯一一条边界上做显式转型，
+  并在 `src/adapter.ts` 与测试侧 `send()` helper 处写明理由。
+
+### 测试
+
+- 新增 **线上请求体矩阵**（`tests/pi-ai-context.spec.ts`）：起一个真实 SSE 端点，走
+  `createProvider` + 真实 `openAICompletionsApi()`，断言线上 body 里 `roles[0] === 'system'`、
+  system 文本等于原提示、`tools` 长度为 1；并覆盖「已归一化输入不二次包裹」的幂等性。
+- 新增 **反向对照**：**不**套适配器时，现代副本会把提示与工具全部丢光（`roles: ["user"]`、
+  `system: null`、`tools: 0`，且**不报错**）——这条钉住适配器为什么是承重的。
+- 全仓 **663** 例测试通过（原 660 + 3），双 tsconfig 类型检查通过，构建通过。
+
+### 已核对、无需改动
+
+- **peer 范围**：DSH 用 `satisfies(runtime, range, { includePrerelease: true })` 求值且只校验
+  `@deepseek-ai/dsh*`，`0.2.1-rc.1` 对 `>=0.1.7-rc.1 <0.3.0-0` 已判通过（实测）。预发布悬崖
+  只在**默认选项**下成立，不适用于本插件的门禁。
+- **宿主 API**：`dsh-llm` / `dsh-settings` / `dsh-host-webserver` / `dsh-llm-pi-ai` 消费点签名未变。
+- **客户端外壳**：产物仍只 `require` react / react-dom / react/jsx-runtime，槽位与主题令牌未变。
+
+## 3.6.1 (2026-10-16)
+
+> **「自动续期」不再是一句没有期限的承诺。** 卡片现在会告诉你**刷新令牌**何时到期 ——
+> 在那之前访问令牌会自动续期，在那之后自动续期就彻底停了，必须重新登录一次 Trae。
+
+### 修复
+
+- **刷新令牌的到期时间对用户完全不可见（issue #37 追问引出）**：
+  - **问题**：卡片一直只写「访问令牌 {时间} 过期（自动续期）」。这句话是对的，
+    而且一直对 —— 直到**刷新令牌**到期的那个瞬间，自动续期就永久停止了。
+    一个读了几个月「自动续期」的用户，没有任何理由预期这件事。
+  - **根因**：刷新令牌的到期时间**被解析了、也被存下来了，但从来没送到浏览器** ——
+    状态接口里根本没有这个字段，所以卡片无从显示。
+  - **现在**：状态接口暴露刷新令牌到期时间，卡片**按账号**在临近到期时给出一行提示：
+    - 剩余 **30 天**以内 → 提醒（警告色），写明**到期时间**与**还剩几天**；
+    - **已到期** → 明确说明「自动续期已停止」，并给出恢复方式（重新登录一次 Trae）；
+    - **还很久 / 没有该字段**（CLI 凭据本身不带）→ **不显示任何东西**。
+      健康的令牌不该在每一行都占一行文字，伪造的期限比不显示更糟。
+
+  > 这条不是理论问题：我们在排查 `#38` 时**亲身遇到过** —— 某区域插件自存的凭据访问令牌已过期，
+  刷新也返回 401，而卡片上一直写着「自动续期」。当时只能靠人肉发现。
+
+### 测试
+
+- 新增 5 例覆盖三种状态与两个边界（健康不显示、临近显示截止日与剩余天数、已过期显示错误态、
+  无该字段不伪造、最后一天仍算「未过期」）。
+- **变异验证**：去掉 30 天提醒窗口 → 2 例变红；在缺少字段时伪造一个期限 → 1 例变红。
+- 全仓 **660** 例测试通过，类型检查通过。
+
 ## 3.6.0 (2026-10-16)
 
 > **多个账号可以并存了。** 本版新增**账号导入 / 导出**：不再需要每次把某台机器的登录凭据

package/README.en.md

@@ -138,7 +138,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.**
+**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.1, verified).**
 
 ### Both pi-ai context generations are supported (since 3.4.2)
 
@@ -161,6 +161,17 @@ The boundary is **0.86**: `dist/utils/transcript.js`, `normalizeContext`, the es
 
 The 0.2.0 line breaks **no** contract this plugin consumes — a symbol-by-symbol check confirmed every API it imports is unchanged ([full 0.2.0-rc.1 impact check](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.0_RC1_IMPACT_CHECK.md)). But since 0.1.7 DSH enforces a **bundle-level peer gate**: a bundle whose peers are unsatisfied is skipped **whole**, with one line on stderr and nothing in the UI — the plugin simply disappears.
 
+### DSH 0.2.1-rc.1 (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`** — 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 `0.2.1-rc.1` (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.1` declares `~3.18.5`).
+
+
 ### Why the upper bound is not `<0.2.0`
 
 2.3.1 wrote `<0.2.0-0`, meaning "not the 0.2.0 release yet". That spelling is **wrong**: in SemVer `0.2.0-rc.1 < 0.2.0-0`, so it excluded the entire 0.2.0 **prerelease** line, and the plugin went dead the moment a user installed the first 0.2.0 prerelease.

package/README.md

@@ -150,7 +150,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 两条线均受支持。**
+**peer 上界为 `<0.3.0-0`：0.1.7 与 0.2 两条线均受支持（含 0.2.1-rc.1，已实测）。**
 
 ### 同时支持 pi-ai 的两代上下文（3.4.2 起）
 
@@ -182,6 +182,30 @@ DSH 自己横跨 `@earendil-works/pi-ai` 的两代，而**本插件解析到哪
 0.2.0 线对本插件**没有契约破坏**——逐符号核对确认插件消费的 API 全部未变（[完整的 0.2.0-rc.1 影响面核对](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.0_RC1_IMPACT_CHECK.md)）。但 0.1.7 起 DSH 有一道**bundle 级 peer 门禁**：
 peer 范围不满足的 bundle 会被**整体跳过**，只往 stderr 写一行，界面上表现为「插件凭空消失」。
 
+### DSH 0.2.1-rc.1（pi-ai 1.1.0）同步结论
+
+宿主 `0.2.1-rc.1` 把 `@earendil-works/pi-ai` 从 `^0.85.1` 抬到了 **`^1.1.0`**，这是 0.2 线里
+唯一有实际行为影响的变化。三项结论：
+
+1. **请求体没有丢东西（已实测）**。1.1.0 的 api **只**读 transcript 里的 system 消息，
+   顶层 `systemPrompt` / `tools` 完全不再读取；而 `dsh-llm-pi-ai` 的 `piContext()` 仍然产出
+   旧版信封。本插件 3.4.2 起就有的双向适配正好覆盖这一点——把真实宿主信封喂进真实
+   `1.1.0` + 本地 SSE 捕获线上请求体，得到 `roles: ["system","user"]`、system 文本完好、
+   `tools: 1`；**去掉适配则变成 `roles: ["user"]`、system `null`、`tools: 0`**（不报错）。
+   这条对照已固化为 `tests/pi-ai-context.spec.ts` 的线上请求体矩阵。
+2. **类型面补齐**。1.1.0 把 `ProviderStreams` 的第二参改成带 `unique symbol` 品牌标记的
+   `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` 已判通过
+   （已实测）。**注意**：预发布悬崖只在**默认选项**下成立——那是 `dsh-connect-workbuddy` 侧
+   调研文档所描述的困境，本插件不适用。
+
+开发树的 `@earendil-works/pi-ai` 钉在 **1.1.0**（宿主实际随包的版本）而非 `^1.1.0`，
+使本地 typecheck 与测试跑在与用户完全一致的契约上；`schemastery` 的 override 同步抬到
+`3.18.5`（`dsh-llm-pi-ai@0.2.1-rc.1` 声明 `~3.18.5`）。
+
+
 ### peer 上界为什么不写 `<0.2.0`
 
 2.3.1 曾写 `<0.2.0-0`，意图是「先不支持 0.2.0 正式版」。这个写法**是错的**：

package/lib/client.js

@@ -335,6 +335,13 @@ window.__ModuleLoader__.load({
 .dsm-trae-usage-account{display:flex;align-items:center;justify-content:space-between;gap:12px;padding:12px 14px;border:1px solid var(--dsw-alias-border-l2,#3a3d45);border-radius:14px;background:var(--dsw-alias-bg-layer-2,#24262c)}
 .dsm-trae-usage-account-copy{display:flex;flex-direction:column;gap:3px;min-width:0}
 .dsm-trae-usage-expiry{padding-left:19px;color:var(--dsw-alias-label-tertiary,#9aa0a8);font-size:12px;line-height:18px}
+/* Refresh-token countdown (issue #37 follow-up). Sits under the access-token
+   line and aligns with it, so the two read as one stack: "token renews" then
+   "but this is when renewal itself ends". Only rendered when it is close or
+   already past, so a healthy account is unchanged. */
+.dsm-trae-refresh-warn{padding-left:19px;font-size:12px;line-height:18px}
+.dsm-trae-refresh-warn-soon{color:var(--dsw-alias-state-warn-primary,#b45309)}
+.dsm-trae-refresh-warn-lapsed{color:var(--dsw-alias-state-error-primary,#dc2626)}
 .dsm-trae-account-picker{display:block}
 /* The 璁剧疆 block: label + hint on the left, control on the right, one save for
    the whole block. It replaces the bare checkbox rows that used to write on
@@ -1306,6 +1313,40 @@ window.__ModuleLoader__.load({
 				minute: "2-digit"
 			}).format(new Date(value));
 		}
+		/** How close a refresh token must be to lapsing before the card warns, in days. */
+		const REFRESH_WARN_DAYS = 30;
+		/**
+		* The refresh-token warning for one account, or undefined when there is nothing
+		* worth saying.
+		*
+		* The access token renews itself every few minutes, so its own expiry answers
+		* "when does this need attention" with "never, until the refresh token lapses".
+		* The refresh token is therefore the only honest countdown on this card, and it
+		* has to be shown BEFORE it runs out: once it lapses the plugin cannot renew at
+		* all and the only recovery is signing in to Trae again, which a user who has
+		* been reading "auto-renewal" for months has no reason to expect.
+		*
+		* Three tones, matching the credit-expiry notice: `lapsed` (renewal already
+		* dead), `soon` (inside the warning window), and nothing otherwise — a healthy
+		* token must not add a line to every account row forever.
+		*/
+		function refreshTokenWarning(expiresAtMs, nowMs, t, formatTime) {
+			if (expiresAtMs === void 0) return void 0;
+			const text = formatTime(expiresAtMs);
+			if (expiresAtMs <= nowMs) return {
+				tone: "lapsed",
+				text: t("row.refreshTokenLapsed", { expiresAt: text })
+			};
+			const days = Math.ceil((expiresAtMs - nowMs) / 864e5);
+			if (days > REFRESH_WARN_DAYS) return void 0;
+			return {
+				tone: "soon",
+				text: t("row.refreshTokenExpiring", {
+					expiresAt: text,
+					days
+				})
+			};
+		}
 		function formatCapacity(value, unknown) {
 			if (value === void 0) return unknown;
 			if (value >= 1e6 && value % 1e6 === 0) return `${value / 1e6}M`;
@@ -2575,6 +2616,14 @@ window.__ModuleLoader__.load({
 																			sourceLabel(account.source)
 																		]
 																	}),
+																	(() => {
+																		const warning = refreshTokenWarning(account.refreshExpiresAtMs, Date.now(), t, formatDateTime);
+																		return warning === void 0 ? null : /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
+																			className: `dsm-trae-refresh-warn dsm-trae-refresh-warn-${warning.tone}`,
+																			role: "status",
+																			children: warning.text
+																		});
+																	})(),
 																	error === void 0 ? null : /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
 																		className: "dsm-trae-account-note",
 																		role: "alert",
@@ -3617,6 +3666,8 @@ window.__ModuleLoader__.load({
 			"row.sourceCli": "Trae CLI",
 			"row.signedIn": "Signed in: {accountName}",
 			"row.tokenExpiry": "Access token expires {expiresAt} (auto-renewal)",
+			"row.refreshTokenExpiring": "Sign in to Trae again by {expiresAt} ({days} day(s) left) — automatic renewal stops after that.",
+			"row.refreshTokenLapsed": "Automatic renewal has stopped: the Trae sign-in expired {expiresAt}. Sign in to Trae again to restore it.",
 			"row.requestFailed": "Request failed",
 			"row.creditsAvailableLabel": "Available",
 			"row.workCreditsLabel": "Work credits",
@@ -3783,6 +3834,8 @@ window.__ModuleLoader__.load({
 			"row.sourceCli": "Trae CLI",
 			"row.signedIn": "已登录：{accountName}",
 			"row.tokenExpiry": "访问令牌 {expiresAt} 过期（自动续期）",
+			"row.refreshTokenExpiring": "请在 {expiresAt} 前重新登录一次 Trae（还剩 {days} 天），此后将无法自动续期。",
+			"row.refreshTokenLapsed": "自动续期已停止：Trae 登录凭据已于 {expiresAt} 过期。请重新登录一次 Trae 以恢复。",
 			"row.requestFailed": "请求失败",
 			"row.creditsAvailableLabel": "可用",
 			"row.workCreditsLabel": "Work 积分",

package/lib/index.d.ts

@@ -319,9 +319,10 @@ declare class TraeCatalog {
  *
  * The mismatch is reachable in BOTH directions, because DSH itself spans both
  * generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 declares `^0.85.1`; 0.2.0-rc.2 and
- * later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`), while this plugin
- * accepts the whole range (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer,
- * the other one is wrong:
+ * later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`, and 0.2.1-rc.1 —
+ * the current desktop host — declares **`^1.1.0`**, which also stopped reading
+ * the top-level fields entirely), while this plugin accepts the whole range
+ * (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer, the other one is wrong:
  *
  * | host | resolved api | outcome |
  * |---|---|---|
@@ -494,13 +495,17 @@ declare function adaptLegacyPiAiContext(context: Context): Context;
  * transcript a MODERN (0.86+) api consumes — the reverse mismatch, and just as
  * silent.
  *
- * WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`)
+ * WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`,
+ * while the 0.2.1-rc.1 desktop host pins `^1.1.0` and still emits the legacy
+ * envelope from its own `piContext()`)
  * while this plugin may resolve a newer copy than its host. A LEGACY host never
  * normalizes, so it hands the api the legacy shape; a modern api reads the
  * prompt from a leading system message and the tools from its `toolsAdded`, and
  * never looks at the top-level fields — so both are dropped without a sound.
  * Verified against the published tarballs: the request that reaches the wire
- * carries no system turn and `tools: []`.
+ * carries no system turn and `tools: []`. This is exactly the shape that
+ * `dsh-llm-pi-ai@0.2.1-rc.1` + `pi-ai@1.1.0` would hit unaided, which is why
+ * the wire-level matrix in `tests/pi-ai-context.spec.ts` pins both directions.
  *
  * Identity for anything already in transcript shape, and for a context with
  * neither a prompt nor tools (pi-ai's own `createInitialSystemMessage` returns
@@ -518,6 +523,27 @@ declare function adaptModernPiAiContext(context: Context): Context;
  * no context and are passed through untouched, and each adapter function is an
  * identity unless the context is actually the other generation's shape. So a
  * healthy install does one `Array.some` per request.
+ *
+ * THE CAST IS THE CONTRACT (pi-ai 1.1.0). From 1.1.0 `ProviderStreams` takes
+ * `TranscriptContext`, a BRANDED type whose `unique symbol` member only
+ * `normalizeContext()` can produce — so a `Context` is no longer assignable and
+ * `tsc` reports `TS2345` at both call sites below. The brand cannot be acquired
+ * honestly here, for two reasons that are both deliberate:
+ *
+ * 1. This wrapper sits BELOW the normalizer. `Models.stream()`/`streamSimple()`
+ *    call `normalizeContext()` and hand a real transcript to the provider;
+ *    `createProvider()` passes it straight through to `api.stream`. So on the
+ *    modern path `adapt()` is an identity and the value already IS a branded
+ *    transcript at runtime — the type just cannot see it across that boundary.
+ * 2. The legacy path REQUIRES an unbranded shape. pi-ai ≤0.85 has no
+ *    `normalizeContext` and no transcript type at all, so its api expects
+ *    exactly the `{ systemPrompt, tools, messages }` object `adapt()` returns.
+ *
+ * So the value handed to `api` is "a context of the generation that api
+ * speaks", which no single edition's declared type names. Casting at this one
+ * boundary is what makes both generations expressible; deriving the type from
+ * the resolved copy instead would make the wrapper uncompilable against the
+ * other generation, which is the whole point of having it.
  */
 declare function withContextAdaptation(api: ProviderStreams, generation: PiAiGeneration): ProviderStreams;
 interface TraeAdapterOptions {
@@ -590,6 +616,13 @@ interface TraeAccountChoice {
   region: TraeRegion;
   source: 'desktop' | 'dsh' | 'cli';
   tokenExpiresAtMs: number;
+  /**
+   * When this account's refresh token lapses, when the credential carries one.
+   * The access token above renews itself automatically until this expires; see
+   * the mirror field on `TraeWebAccount` in status-paths.ts for why the card
+   * needs it.
+   */
+  refreshExpiresAtMs?: number;
   selected: boolean;
 }
 /**
@@ -2002,6 +2035,18 @@ interface TraeWebAccount {
   region: TraeRegion;
   source: 'desktop' | 'dsh' | 'cli';
   tokenExpiresAtMs: number;
+  /**
+   * When this account's REFRESH token expires, when the credential carries one.
+   *
+   * The access token above is renewed automatically — the plugin refreshes it
+   * five minutes before it lapses — so by itself it answers "when does this
+   * need attention", which is "never, while the refresh token lives". The
+   * refresh token is the real horizon: once IT expires the automatic renewal
+   * stops working and the user must sign in to Trae again. Before this field the
+   * card could only say "auto-renewal", which stays true right up to the moment
+   * it silently stops being true.
+   */
+  refreshExpiresAtMs?: number;
   selected: boolean;
 }
 /**
@@ -2228,6 +2273,13 @@ type TraeWebUsage = {
   accountId: string;
   accountName: string;
   tokenExpiresAtMs: number;
+  /**
+   * When the BOUND account's refresh token expires (absent when the credential
+   * carries none). See {@link TraeWebAccount.refreshExpiresAtMs} — this is the
+   * horizon that actually matters, because the access token above renews
+   * itself until this one lapses.
+   */
+  refreshExpiresAtMs?: number;
   /** Which per-region model directory and selection this account owns. */
   region: TraeRegion;
   /** Whether this region's provider is currently offered to DSH. */

package/lib/index.js

@@ -344,9 +344,10 @@ var TraeCatalog = class {
 *
 * The mismatch is reachable in BOTH directions, because DSH itself spans both
 * generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 declares `^0.85.1`; 0.2.0-rc.2 and
-* later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`), while this plugin
-* accepts the whole range (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer,
-* the other one is wrong:
+* later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`, and 0.2.1-rc.1 —
+* the current desktop host — declares **`^1.1.0`**, which also stopped reading
+* the top-level fields entirely), while this plugin accepts the whole range
+* (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer, the other one is wrong:
 *
 * | host | resolved api | outcome |
 * |---|---|---|
@@ -689,13 +690,17 @@ function adaptLegacyPiAiContext(context) {
 * transcript a MODERN (0.86+) api consumes — the reverse mismatch, and just as
 * silent.
 *
-* WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`)
+* WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`,
+* while the 0.2.1-rc.1 desktop host pins `^1.1.0` and still emits the legacy
+* envelope from its own `piContext()`)
 * while this plugin may resolve a newer copy than its host. A LEGACY host never
 * normalizes, so it hands the api the legacy shape; a modern api reads the
 * prompt from a leading system message and the tools from its `toolsAdded`, and
 * never looks at the top-level fields — so both are dropped without a sound.
 * Verified against the published tarballs: the request that reaches the wire
-* carries no system turn and `tools: []`.
+* carries no system turn and `tools: []`. This is exactly the shape that
+* `dsh-llm-pi-ai@0.2.1-rc.1` + `pi-ai@1.1.0` would hit unaided, which is why
+* the wire-level matrix in `tests/pi-ai-context.spec.ts` pins both directions.
 *
 * Identity for anything already in transcript shape, and for a context with
 * neither a prompt nor tools (pi-ai's own `createInitialSystemMessage` returns
@@ -730,13 +735,35 @@ function adaptModernPiAiContext(context) {
 * no context and are passed through untouched, and each adapter function is an
 * identity unless the context is actually the other generation's shape. So a
 * healthy install does one `Array.some` per request.
+*
+* THE CAST IS THE CONTRACT (pi-ai 1.1.0). From 1.1.0 `ProviderStreams` takes
+* `TranscriptContext`, a BRANDED type whose `unique symbol` member only
+* `normalizeContext()` can produce — so a `Context` is no longer assignable and
+* `tsc` reports `TS2345` at both call sites below. The brand cannot be acquired
+* honestly here, for two reasons that are both deliberate:
+*
+* 1. This wrapper sits BELOW the normalizer. `Models.stream()`/`streamSimple()`
+*    call `normalizeContext()` and hand a real transcript to the provider;
+*    `createProvider()` passes it straight through to `api.stream`. So on the
+*    modern path `adapt()` is an identity and the value already IS a branded
+*    transcript at runtime — the type just cannot see it across that boundary.
+* 2. The legacy path REQUIRES an unbranded shape. pi-ai ≤0.85 has no
+*    `normalizeContext` and no transcript type at all, so its api expects
+*    exactly the `{ systemPrompt, tools, messages }` object `adapt()` returns.
+*
+* So the value handed to `api` is "a context of the generation that api
+* speaks", which no single edition's declared type names. Casting at this one
+* boundary is what makes both generations expressible; deriving the type from
+* the resolved copy instead would make the wrapper uncompilable against the
+* other generation, which is the whole point of having it.
 */
 function withContextAdaptation(api, generation) {
 	const adapt = generation === "modern" ? adaptModernPiAiContext : adaptLegacyPiAiContext;
+	const forApi = (context) => adapt(context);
 	return {
 		...api,
-		stream: (model, context, options) => api.stream(model, adapt(context), options),
-		streamSimple: (model, context, options) => api.streamSimple(model, adapt(context), options)
+		stream: (model, context, options) => api.stream(model, forApi(context), options),
+		streamSimple: (model, context, options) => api.streamSimple(model, forApi(context), options)
 	};
 }
 function createTraeAdapter(options) {
@@ -1867,6 +1894,7 @@ var TraeCredentialStore = class {
 			region: regionOfCredential(live),
 			source: live.source,
 			tokenExpiresAtMs: live.expiresAtMs,
+			...live.refreshExpiresAtMs === void 0 ? {} : { refreshExpiresAtMs: live.refreshExpiresAtMs },
 			selected: false
 		};
 	}
@@ -1881,6 +1909,7 @@ var TraeCredentialStore = class {
 			region: regionOfCredential(credential),
 			source: credential.source,
 			tokenExpiresAtMs: credential.expiresAtMs,
+			...credential.refreshExpiresAtMs === void 0 ? {} : { refreshExpiresAtMs: credential.refreshExpiresAtMs },
 			selected: selectedExists ? traeAccountId(credential) === this.accountId : credential === defaultSelected
 		}));
 	}
@@ -5484,6 +5513,7 @@ async function traeWebUsage(deps, region) {
 		accountId: accounts.find((item) => item.selected)?.id ?? "",
 		accountName: credential.accountName ?? credential.userId,
 		tokenExpiresAtMs: credential.expiresAtMs,
+		...credential.refreshExpiresAtMs === void 0 ? {} : { refreshExpiresAtMs: credential.refreshExpiresAtMs },
 		region,
 		enabled,
 		accounts,

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "3.6.0",
+  "version": "3.7.0",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",
@@ -85,26 +85,26 @@
     "@deepseek-ai/dsh-llm-pi-ai": ">=0.1.7-rc.1 <0.3.0-0",
     "@deepseek-ai/dsh-settings": ">=0.1.7-rc.1 <0.3.0-0",
     "@deepseek-ai/schemastery": ">=3.18.4 <4.0.0",
-    "@earendil-works/pi-ai": ">=0.85.1",
+    "@earendil-works/pi-ai": ">=0.85.1 <2.0.0",
     "react": "^18.2.0"
   },
   "devDependencies": {
-    "@deepseek-ai/cordis": "^4.0.4",
-    "@deepseek-ai/dsh-atomic-write": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-attachment": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-locale": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-ui-primitives": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-ui-renderer": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-client-ui-slots": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-home-paths": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-host-webserver": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-llm": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-llm-pi-ai": "0.2.0-rc.1",
-    "@deepseek-ai/dsh-settings": "0.2.0-rc.1",
-    "@deepseek-ai/schemastery": "3.18.4",
-    "@earendil-works/pi-ai": "^0.85.1",
+    "@deepseek-ai/cordis": "^4.0.5",
+    "@deepseek-ai/dsh-atomic-write": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-attachment": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-locale": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-ui-renderer": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-home-paths": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-host-webserver": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-llm": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-llm-pi-ai": "0.2.1-rc.1",
+    "@deepseek-ai/dsh-settings": "0.2.1-rc.1",
+    "@deepseek-ai/schemastery": "3.18.5",
+    "@earendil-works/pi-ai": "1.1.0",
     "@testing-library/dom": "^10.4.2",
     "@testing-library/react": "^16.3.3",
     "@types/node": "^22.20.0",