dsh-connect-trae 3.3.0 → 3.4.1

package/CHANGELOG.md

@@ -1,5 +1,69 @@
 # Changelog
 
+## 3.4.1 (2026-10-12)
+
+> **`4011` 的含义改正了：它是 Trae 对 SOLO 通道的限流，不是「该 function 不提供此模型」。**
+> 起因是 [issue #33](https://github.com/dingminhua/dsh-connect-trae/issues/33)：报告人用 `GLM-5.3` 拿到
+> `Trae code 4011`，报文原文写着 `your requests have exceeded the rate limit`，而他额度充足、
+> Trae 客户端的 SOLO 里同一模型正常。**两边都没错**——Trae 把「额度」和「限流」分成两个码，
+> 插件此前把限流读成了「function 归属错误」，于是用一个与上游原文矛盾的结论来解释，用户只能来问。
+> 取证过程见 `docs/ISSUE33_DIAGNOSIS.md`。
+
+### 修复
+
+- **`4011` 的文案不再断言一个与上游原文矛盾的原因**（issue #33）：
+  - **原行为**：`TRAE_ERROR_HINTS[4011]` 写死为「Trae refused this model under the SOLO function the request used」，并把 Trae 自己的原文降级成 `· upstream:` 后缀。用户看到的主句是「模型/function 错了」，于是按那个方向去查。
+  - **为什么那个断言站不住**：本机 CN 实时凭据上跑 **22 个 function × 6 个模型**的最小请求矩阵，
+    「模型不在该 function 名单里」**无一例外回 `4001`**（`the param is invalid`）——22 个 function 全部如此，**没有一次回 4011**；而报告人用的 `glm-5.3` 归属的正是 `solo_work_remote`（插件本来就发这个 function），同一份请求体**正常出字**。也就是说「function 选错」这个条件已经被 `4001` 占用了，4011 不可能是它。
+  - **改后**：`4011` 如实描述为「Trae 限流了这条 SOLO 通道（是限流，不是余额）」，Trae 原文照旧附在后面。
+- **`4011` 的 HTTP 状态改为 `429`（`soft_rate`），让状态码、文案与内核判定三者一致**：
+  - **原行为**：4011 被归类为 `400 / client`（按本插件 `fallback-upstream.ts` 的语义，`client` 属于「可换通道重放」的一类，绝不是「等一下再来」的一类）。但内核 `@deepseek-ai/dsh-llm-pi-ai` 是**按消息文本**分类的（`/\b429\b|rate.?limit/i` → `RATE_LIMIT`），而 `RATE_LIMIT` 在 `DEFAULT_RETRYABLE_CODES` 里、`maxRetries = 5`。
+  - **后果（issue #33 截图逐项吻合）**：失败的 4011 被内核当限流重试——`已重试模型请求 (5/5)`、重试延迟 7328 毫秒、右侧 `RATE_LIMIT` 徽标；而同一行正文却说「该 function 不提供此模型」。**被限流的通道 8 秒内又挨了 5 发请求。**
+  - **改后**：4011 → `429 / soft_rate`，三处判定不再打架；`soft_rate` 也正是 `fallback-upstream` 拒绝换通道重放的类别（限流不是通道兼容性问题，是对的）。
+- **一键测试不再把「被限流」判成「上游不提供」**（issue #33）：
+  - `UNSUPPORTED_CODES` 此前是 `{4001, 4011}`，于是 4011 会得到 `unsupported`——卡片文案「上游不提供」，是一个**永久性的负面结论**。这与该模块自己写在文件头的原则直接冲突（「the verdict must never turn an inconclusive answer into "unavailable"」）。报告人用一键测试时会被告知一个能用的模型已经死了。
+  - **改后**：4011 归入 `rate_limited`（卡片「被限流」），`unsupported` 只由 `4001` 产生。
+  - **顺带把「一个码只能有一个 verdict」变成结构性约束**：原来每个 verdict 一个 `Set`，一个码同时出现在两个集合里时，结果取决于分支书写顺序——实测把 4011 加回「unsupported」集合**所有测试都过**。现在改成单一 `CODE_VERDICTS` 映射表 + 加载期唯一性断言，并补了交叉断言用例钉住它。
+- **登记两个此前不认识的错误码**：
+  - **`4008` = 额度/配额耗尽**（原文 `Your requests have exceeded the quota.`）。它与 `4011` **是两个不同的码**：Trae 把「额度用完」和「被限流」分开报，所以 issue #33 里「我额度还有很多」与「我被 4011 拦住」可以同时成立。只登记文案与分类，**不改它的既有语义**（仍 `400 / client`）。本机只在国际版账号上观察到（该账号当前对多数模型都回 4008），CN 未触发——属**未验证项**。
+  - **`4023` = 模型名不存在**（原文 `the model is unknown`）。
+  - 一键测试里 `4008` 归入 `unknown`：它是**账号级**状态，不能变成对某个**模型**的判决。
+
+### 测试
+
+- **全仓 541 → 549（+8）**：
+  - `tests/solo-bridge.spec.ts`：4011 文案改为「限流」并保留 Trae 原文、`4008` 与 `4011` 文案分开、`4023` 命名、未登记码回退；`bridgeTraeSoloStreamOrFail` 的 4011 用例改为断言 `429 / soft_rate`；`4008` 的既有用例改为断言新文案。
+  - `tests/model-probe.spec.ts`：4011 → `rate_limited`（含「消息里只有码、没有 429 状态」的路径与「流中拒绝」路径）、`4008` → `unknown`、`4001` → `unsupported`，以及一条**表级交叉断言**（每个已知码都只映射到一个 verdict）——它正是为上面那个「顺序依赖」缺陷加的。
+  - **变异验证 6 次，6 次全部被抓**：① 去掉 4011 的 429 映射 → 1 例失败；② 恢复旧 4011 文案 → 2 例失败；③ 把 4011 在映射表里改回 `unsupported` → 4 例失败（**这条在改造前是抓不到的**）；④ 去掉 4008 的 `unknown` 映射 → 2 例失败；⑤ 删除「表内唯一性」的交叉断言依赖的行为 → 2 例失败；⑥ 其余组合。恢复后 55 文件 549 例全绿。
+- 确认新增用例真的在跑：改动前基线 **541**、改动后 **549**，净增 8，与新增用例数一致。
+
+### 文档
+
+- `docs/ISSUE33_DIAGNOSIS.md`：完整取证——`4008`/`4011`/`4001`/`4023`/`1001`/`1005` 的码→语义对照、
+  22 function × 6 模型的调用矩阵、`glm-5.3` 的归属验证、本机 30 并发未触发限流的对照，以及内核
+  `dsh-llm-pi-ai` 按文本分类 + `DEFAULT_RETRYABLE_CODES` 的证据链（为什么截图里是 5/5 与 7328 毫秒）。
+  同时明确列出**未证实项**（4011 的粒度是「通道」还是「账号」、`4008` 的边界与恢复时间、CN 是否也用 4008）。
+
+## 3.4.0 (2026-10-12)
+
+### 新增
+
+- **积分即将过期时给出提醒**（贡献者 [JeffTsuiCUG](https://github.com/JeffTsuiCUG)，PR [#32](https://github.com/dingminhua/dsh-connect-trae/pull/32)）。剩余额度只回答「还有多少」，回答不了「**哪一笔先到期**」，而后者才是「该先用哪个」的依据。此前一个 1 小时后过期的包和一个下个月才过期的包在界面上看起来完全一样，只盯总额的用户会毫无察觉地丢掉最先到期的那个。
+  - **数据在上一版（3.3.0，PR #31）已就绪**：`credits.accounts[].expiresAtMs` 已逐包携带到期时刻；本版在其之上加提醒 UI，**不新增任何上游读、卡片也不因此多一次请求**。原始起因见 [issue #26](https://github.com/dingminhua/dsh-connect-trae/issues/26)（DSH 主界面侧边栏显示积分状态的长期目标；`credits.expiry` 这份数据将来做 #26 可直接复用，同一个计费请求的结果）。
+  - **`toCredits` 按到期时刻把有余额的积分包分桶汇总为 `credits.expiry`**：`within24h` / `within3d` / `within7d` / `expired` 四桶，每桶带金额合计、套餐数量与最早到期时间。
+    - 只统计**正余额**的包：已用尽的包即使今天到期也不计入，否则长命账号会看起来永远「迫在眉睫」。
+    - 已过期的包**单独计桶**，不进入前瞻窗口——剩余毫秒数为负时会满足所有前瞻条件（`end - now < 24h`），混在一起会让一个早就死掉的包看起来永远临近。
+    - 抽出 `usableExpiry()` 谓词（`> 0` 且有限），与每包投影共用同一判断，两者不可能对同一批数据得出矛盾结论。`0` 与 `NaN`/`Infinity` 均被排除。
+  - **`TraeWebCreditExpiry` / `TraeWebExpiringCredits` 仅当有包携带可用到期时间时才存在**——「没拿到数据」不得渲染成「没有要过期的」，这与 #31 里 `expiresAtMs` 缺省即省略的设计一致。
+  - **两处 UI 不再一视同仁**：使用量标签页新增到期提示条，按 **7 天 → 24 小时 → 已过期**逐级加重，写明金额、套餐数和最早到期时间；输入框下面的积分面板（真正常驻看额度的地方）同样渲染提示条。仅国内版：国际版是订阅制（`payStatus`），没有逐包到期数据。
+  - 中英双语文案（`row.expiryWarningSoon` / `row.expiryWarningWeek` / `row.expiryWarningLapsed` / `row.expiryEarliest`）。
+  - 新增测试覆盖分桶边界、正余额排除、已过期/未到期分离、最早到期选取、非有限值与 `0` 的处理，以及「无数据」与「没有要过期的」这两个必须区分的状态。
+
+### 测试
+
+- `tests/composer-styles.spec.tsx` 的 fixture 补上带 `expiry` 的数据，让输入框面板的到期提示条真正被渲染并接受「每个渲染出的 class 在样式表里有规则」的守卫检查；并做了负向验证——临时删掉一条样式规则，测试精确报出缺失的 class（`dsm-trae-expiry-detail`），确认守卫是真的在覆盖而不是假通过。
+- `tests/web-status.spec.ts` 新增 `expiry summary` 一组，钉住分桶与两种状态的区分。
+
 ## 3.3.0 (2026-10-11)
 
 ### 新增

package/README.en.md

@@ -42,7 +42,9 @@ A [DeepSeek Harness (DSH)](https://github.com/deepseek-ai/deepseek-harness) bund
 - **Vision follows Trae's own declaration** — when Trae marks a model `multimodal`, the plugin advertises it as such with no manual tick per model (issue #16). The rule is "**models you tick ∪ models Trae marks multimodal**": models Trae marks `false`, or does not mark at all, stay text-only and can still be turned on by hand. A row enabled automatically is shown ticked and read-only, with the reason. See "Image input" below.
 - **Account switching** — refreshes the token list and lets users select an account without storing tokens in DSH settings. **Your choice is remembered and stays in effect**: the plugin will never switch accounts on its own just because the bound one ran out of credit or another usable one was found (switching bills a different person). So when the bound account is exhausted the card **says so explicitly** and lists the other accounts on this machine that still have credit, with their balances, for you to switch to in one click — instead of showing an empty panel or quietly rebinding you. "Refresh accounts & tokens" now always reports what happened (how many accounts were found, who is still bound) instead of appearing to do nothing. The dropdown names the product (`Trae` / `TRAE SOLO` / international) so a credential left behind by an uninstalled app is recognisable.
 - **Read-only usage and model management** — Work/general credits on CN accounts, subscription/trial status on international ones; enable Trae models freely. Read-only queries consume nothing.
-- **One-click test of the enabled models** — sends each **enabled** model one minimal message (a single `ping`, no tools) and reports whether it actually answers: **works** / **needs a higher plan** (Trae `1005`; your plan does not cover it) / **not served** (`4001`/`4011`; no SOLO function serves it) / **throttled** / **sign-in rejected** / **not determined**. The last one is a first-class outcome: a timeout, a dropped connection, a proxy or a 5xx is **never** reported as unusable — only an explicit upstream refusal is a negative verdict. This is the plugin's **only** operation that spends quota (check-in changes account state but spends nothing), it runs only when you click, and its results live in the current session rather than in your settings.
+- **Credit-near-expiry notices** — the remaining balance only says "how much is left", not "**which pack lapses first**". The notice escalates by urgency (7 days → 24 hours → already lapsed) and names the amount, the pack count and the soonest expiry, so a user watching only the total never silently loses the pack that expires first. Shown in both the usage card and the composer credits panel on the CN side (the international side is subscription-based and has no per-pack expiry).
+- **One-click test of the enabled models** — sends each **enabled** model one minimal message (a single `ping`, no tools) and reports whether it actually answers: **works** / **needs a higher plan** (Trae `1005`; your plan does not cover it) / **not served** (`4001`; no SOLO function serves it) / **throttled** (`4011`; Trae rate-limited that route) / **sign-in rejected** / **not determined**. The last one is a first-class outcome: a timeout, a dropped connection, a proxy or a 5xx is **never** reported as unusable — only an explicit upstream refusal is a negative verdict. This is the plugin's **only** operation that spends quota (check-in changes account state but spends nothing), it runs only when you click, and its results live in the current session rather than in your settings.
+  > `4011` is a **rate limit**, not "this model is unavailable" (measured for issue #33): an exhausted balance reports a different code, `4008`, so "I still have plenty of credits" and "I got a 4011" are both true at once. A throttled model answers again after a short wait — do not delete it.
 - **One-click test of all models** — the same probe applied to **every visible model** of the current region, not just the enabled ones. Use it when you want to know whether the models you have switched off could still answer — after a plan change, or after Trae reshuffles its lineup.
 - **Daily check-in claiming (per account)** — on the CN card **every account row carries its own check-in button**, with the day's reward written on it (`Check in +150`). A row reads **Claimed** and disables itself once *that account* has been paid, and reads **Device used** and disables itself when *this machine* has already spent today's slot through some other account — the two are reported honestly, and the second is never dressed up as "claimed". This is the plugin's **only** operation that changes account state, and it runs only when you click; one click targets that one row's account and sends exactly one request. There is deliberately **no "claim for every account"**: Trae allows **one check-in per device per day** (switching accounts does not reset the slot), so a sweep could only manufacture a row of false failures. The international side has no check-in activity, so no button is shown there.
 - **Composer readout** — the composer tool row (between "Expert" and the model selector) shows a clickable readout, refreshing every 5 minutes. **Both regions show it, but they do not show the same quantity, and that is the data's doing**: the CN side is credit-based, so it reads "Trae CN · <general credits>"; the international side is subscription-based and its usage document carries no credit field at all, so it reads "Trae Global · <plan>" (e.g. `Pro` / `Free`). The whole readout is clickable and opens a panel showing a TABLE: one row per account in the region — general credits on CN, plan on international — where clicking a row SWITCHES accounts (through the same merged `accounts` write the card uses, so the other region's selection survives), with the manual refresh button in the panel. It appears **only while the session's selected model belongs to this plugin**, and renders nothing for any other provider — which is what keeps two connector plugins from competing for one shared row (the sidebar foot is a shared root row; the composer row is per-session and provider-scoped).

package/README.md

@@ -43,7 +43,9 @@
 - **多账号切换** —— 支持重新读取 Token 列表并选择账号；Token 不写入 DSH 设置。**你的选择会被记住并长期生效**：插件不会因为某个账号额度用尽、或检测到另一个可用账号就自作主张替你切换（换账号意味着换人计费）。所以当绑定的账号额度耗尽时，卡片会**明确告诉你**，并把本机其他还有额度的账号连同其可用积分数列出来，由你一键切换——而不是让面板一直空着、也不自动把你切走。「刷新账号与 Token」每次都会回报结果（找到几个账号、当前仍绑定谁），不会再「点了没反应」。下拉里显示的是产品名（`Trae` / `TRAE SOLO` / 国际版），便于分辨凭据来自哪个安装。
 - **跟随 Trae 当前登录的账号** —— 你在 Trae 桌面端**退出并换登录**后，卡片会检测到「插件绑定的账号」与「Trae 现在登录的账号」不一致，并给出一行提示与**一键切换**（复用账号下拉的同一次写入，不引入第二条切换路径）。想让插件**自动跟随**，可打开设置卡片里的「跟随 Trae 当前登录的账号」开关：此后每次配置生效都会把 `accounts.<region>` 重绑到 App 当前登录的账号。**该开关默认关闭**——已有配置保持原来的严格绑定，自动换绑意味着换人计费，必须由你主动勾选；未勾选时上面那行提示就是你的手动通道。（issue #29）
 - **只读用量与模型管理** —— 国内版查看 Work 积分与通用积分，国际版查看订阅/试用状态；刷新/启用 Trae 模型；只读查询不消耗额度。
-- **一键测试启用模型** —— 给**已启用**的每个模型发一条最小消息（一句 `ping`、不带工具），逐个告诉你能不能真的应答：**可用** / **需要更高档位**（Trae `1005`，你的套餐不覆盖）/ **上游不提供**（`4001`/`4011`，SOLO 通道没有这个模型）/ **被限流** / **登录凭据被拒** / **本次未测出**。最后一项是一等公民：超时、断连、代理、5xx **一律不算「不可用」**——只有上游明确的拒绝才算负面结论。**这是插件里唯一消耗额度的操作**（签到改变的是账号状态，不消耗），只在你点击时运行，结果只留在当前会话里不写入设置。
+- **积分临近到期会提醒** —— 剩余额度只回答「还有多少」，回答不了「**哪一笔先到期**」；提醒条按到期紧迫程度逐级加重（**7 天 → 24 小时 → 已过期**），写明金额、套餐数和最早到期时间，避免只盯总额时悄悄丢掉最先到期的额度。国内版在用量页与输入框积分面板两处都显示（国际版是订阅制，没有逐包到期数据）。
+- **一键测试启用模型** —— 给**已启用**的每个模型发一条最小消息（一句 `ping`、不带工具），逐个告诉你能不能真的应答：**可用** / **需要更高档位**（Trae `1005`，你的套餐不覆盖）/ **上游不提供**（`4001`，SOLO 通道没有这个模型）/ **被限流**（`4011`，Trae 限了这条通道）/ **登录凭据被拒** / **本次未测出**。最后一项是一等公民：超时、断连、代理、5xx **一律不算「不可用」**——只有上游明确的拒绝才算负面结论。**这是插件里唯一消耗额度的操作**（签到改变的是账号状态，不消耗），只在你点击时运行，结果只留在当前会话里不写入设置。
+  > `4011` 是**限流**不是「模型不可用」（issue #33 实测）：它额度耗尽走的是另一个码 `4008`，所以「额度还有很多却报 4011」两句话可以同时成立。被限流的模型**等你一会儿再试**即可，不要删。
 - **一键测试所有模型** —— 同一套探测，作用于当前 region 的**全部可见模型**（不限于已启用的）。想知道「没启用的那些到底还能不能用」时用它——比如套餐降级后，或 Trae 调整了模型阵容之后。
 - **每日签到领取（逐账号）** —— 国内版**每个账号行各有一个签到按钮**，当日奖励直接写在按钮上（`签到 +150`）；该账号当天已领显示「已领取」并禁用，**本机今日名额已被别的账号用掉**时显示「本机已签」并禁用——如实区分「这个账号领了」和「这台设备领过了」，绝不把后者说成「已领取」。这是插件里**唯一会改变账号状态**的操作，由你主动点击触发；一次点击只针对该行账号、只发一次请求，**刻意没有「一键全签」**——Trae 的签到按「**每台设备每天一次**」计（换账号不会重置当天名额），批量只会酿成一排假失败。国际版没有签到活动，因此不显示该按钮。
 - **输入框读数** —— 在输入框工具栏（「专家」与模型选择器之间）显示一块可点击读数，5 分钟自动刷新。**两个区域都显示，但显示的东西不同，这是数据决定的**：国内版是积分制，显示「Trae CN · <通用积分>」；国际版是订阅制，它的用量文档里根本没有积分字段，所以显示「Trae 国际版 · <套餐>」（如 `Pro` / `Free`）。**整块可点击**，弹出浮层显示一张**表格**：本区域**每个账号一行**，国内版列**通用积分**、国际版列**套餐**，**点行即可切换账号**（写入与卡片相同的 `accounts` 字段、合并时不丢掉另一个区域的选择），并把手动刷新按钮放在浮层里。**只在当前会话选中的模型属于本插件时出现**——选其它供应商的模型时整块不渲染。这样两个连接器插件不会争同一个位置（侧边栏底部是共享的根级行，输入框工具栏是按会话、按供应商的）。

package/lib/client.js

@@ -243,7 +243,7 @@ window.__ModuleLoader__.load({
 .dsm-plugin-card-title{color:var(--dsw-alias-label-primary,#e6e6e6);font-size:15px;font-weight:600;line-height:1.4}
 .dsm-plugin-card-description{color:var(--dsw-alias-label-tertiary,#999);font-size:13px;line-height:1.5}
 /* Pure-CSS caret: the host primitives' chevron icon names are not part of any
-   stable contract across DSH releases, so no static import is used — a border
+   stable contract across DSH releases, so no static import is used 鈥?a border
    caret in the plugin's own CSS is version-proof. */
 .dsm-plugin-card-chevron{color:var(--dsw-alias-label-tertiary,#999);flex:none;width:16px;height:16px;position:relative;transition:transform .16s}
 .dsm-plugin-card-chevron::before{content:"";display:block;position:absolute;left:4px;top:5px;width:7px;height:7px;border-right:1.6px solid currentColor;border-bottom:1.6px solid currentColor;transform:rotate(45deg)}
@@ -280,15 +280,15 @@ window.__ModuleLoader__.load({
 .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}
 .dsm-trae-account-picker{display:block}
-/* The 设置 block: label + hint on the left, control on the right, one save for
+/* 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
-   every click — a draft needs a visible way back out, so each row carries its
+   every click 鈥?a draft needs a visible way back out, so each row carries its
    own explanation and the footer carries the buttons. */
 /* The preference switches: BARE LINES, one per switch, each with its label
    wrapped around the box so the whole line is a click target.
  *
- * The 设置 block used to be a bordered box with a heading, two rows and a
- * 「保存」/「放弃」 footer. That is gone with the draft it existed to serve — this
+ * The 璁剧疆 block used to be a bordered box with a heading, two rows and a
+ * 銆屼繚瀛樸€?銆屾斁寮冦€?footer. That is gone with the draft it existed to serve 鈥?this
  * is the sibling dsh-connect-workbuddy card's shape, where a preference is a
  * checkbox on a line that commits on the click. */
 .dsm-trae-prefs{display:flex;flex-direction:column;gap:8px}
@@ -300,14 +300,14 @@ window.__ModuleLoader__.load({
 .dsm-trae-pref-hint{color:var(--dsw-alias-label-tertiary,#9aa0a8)}
 .dsm-trae-pref span{min-width:0}
 /* The card's checkboxes are the platform's own, styled only with
-   accent-color — the SAME idiom .dsm-trae-mainui-switch-label above already
+   accent-color 鈥?the SAME idiom .dsm-trae-mainui-switch-label above already
    uses for the composer-line switch, and the one the sibling
    dsh-connect-workbuddy card uses for its tab and credits boxes.
  *
  * These were drawn by hand for one release: a 34x20 track with a 14px knob,
  * --dsw-alias-brand-primary when checked. That token is DSH's CONTRAST colour
  * (#0f1115 light / #f9fafb dark), not an accent, so a checked box came out as a
- * solid black pill — heavier than anything else in the card, and unrelated to
+ * solid black pill 鈥?heavier than anything else in the card, and unrelated to
  * the native box sitting two centimetres away in the composer toolbar. The
  * platform checkbox tracks the host's own accent and dark mode for free. */
 .dsm-trae-switch{display:inline-flex;align-items:center;cursor:pointer}
@@ -315,7 +315,7 @@ window.__ModuleLoader__.load({
 .dsm-trae-switch input:disabled{cursor:default}
 .dsm-trae-switch:has(input:disabled){opacity:.6;cursor:default}
 /* The account block is a real table: the question it answers is "which of these
-   accounts, and what is the action on each one" — a dropdown can only ever show
+   accounts, and what is the action on each one" 鈥?a dropdown can only ever show
    the one already chosen. */
 .dsm-trae-accounts{display:flex;flex-direction:column;gap:10px;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-accounts-head{display:flex;align-items:flex-start;justify-content:space-between;gap:12px}
@@ -323,15 +323,15 @@ window.__ModuleLoader__.load({
 .dsm-trae-accounts-head>button{flex:none;white-space:nowrap}
 .dsm-trae-accounts-title{margin:0;font-size:13px;font-weight:600;line-height:18px;color:var(--dsw-alias-label-primary,#e6e6e6)}
 .dsm-trae-accounts-hint{margin:3px 0 0;font-size:12px;line-height:18px;color:var(--dsw-alias-label-tertiary,#9aa0a8)}
-/* The account rows: two lines each — who the account is, then what it is worth
-   — with the one action that applies to THAT row on the right. A four-column
+/* The account rows: two lines each 鈥?who the account is, then what it is worth
+   鈥?with the one action that applies to THAT row on the right. A four-column
    table was the wrong instrument here: every field demanded its own header, the
    columns drifted with the content ("LaoDing" vs a full expiry stamp), and the
    bound row repeated its "in use" badge in two different columns. */
 /* The account table, shaped like the sibling WorkBuddy card's pool table: a
    bordered container, a tinted header row, and one grid row per account whose
    tracks are FRACTIONS of the container rather than sizes derived from the
-   content. That is the whole point — the previous four-column table let each
+   content. That is the whole point 鈥?the previous four-column table let each
    column grow with its own text, so the columns did not line up from row to row
    and the table read as noise in a narrow panel. */
 .dsm-trae-account-table{display:flex;flex-direction:column;border:1px solid var(--dsw-alias-border-l2,#3a3d45);border-radius:12px;overflow:hidden;background:var(--dsw-alias-bg-layer-2,#24262c)}
@@ -375,7 +375,7 @@ window.__ModuleLoader__.load({
 .dsm-trae-account-checkin:hover:not(:disabled){background:rgba(86,134,254,.16)}
 .dsm-trae-account-checkin:focus-visible{outline:2px solid var(--dsw-alias-brand-primary,#5686fe);outline-offset:1px}
 /* A disabled check-in still STATES something ("claimed", "device used"), so it
-   stays readable — clearly inactive, not invisible. */
+   stays readable 鈥?clearly inactive, not invisible. */
 .dsm-trae-account-checkin:disabled{opacity:.55;cursor:default;border-color:transparent;color:var(--dsw-alias-label-tertiary,#9aa0a8);background:transparent}
 /* The switch is the row's LIVE control, so it is brighter than the inert
    check-in labels beside it: same shape, different weight. */
@@ -422,7 +422,7 @@ window.__ModuleLoader__.load({
    the hint tooltip rather than looking like its read-only sibling. */
 /* The sidebar-credit switch. Two instances share this style: the card's own
    row at the top and the copy beside the model actions (2.9.3). Without it the
-   checkbox rendered unstyled and read as absent — the whole reason the switch
+   checkbox rendered unstyled and read as absent 鈥?the whole reason the switch
    looked missing. */
 .dsm-trae-models-actions{display:flex;align-items:center;gap:8px;flex:none}
 .dsm-trae-usage-alternative{display:flex;align-items:flex-start;gap:10px;margin-top:10px;padding:10px 12px;border:1px solid var(--dsw-alias-state-warn-secondary,#fbbf24);border-radius:10px;background:var(--dsw-alias-state-warn-tertiary,#fef3c7)}
@@ -431,6 +431,14 @@ window.__ModuleLoader__.load({
 .dsm-trae-usage-switch-button:hover:not(:disabled){background:var(--dsw-alias-interactive-bg-hover,rgba(127,127,127,.14))}
 .dsm-trae-usage-switch-button:disabled{opacity:.5;cursor:not-allowed}
 .dsm-trae-usage-note{margin:8px 0 0;color:var(--dsw-alias-label-tertiary,#999);font-size:11px;line-height:16px}
+/* Credit-expiry notice, card copy. Three tones by urgency, so the 24-hour case
+   cannot be mistaken for the 7-day one at a glance. Reads as an advisory, not
+   an error: the account works fine, the credit is simply about to lapse. */
+.dsm-trae-expiry{display:flex;flex-direction:column;gap:2px;margin-top:10px;padding:10px 12px;border:1px solid;border-radius:10px;font-size:12px;line-height:18px}
+.dsm-trae-expiry-soon{border-color:var(--dsw-alias-state-warn-secondary,#fbbf24);background:var(--dsw-alias-state-warn-tertiary,#fef3c7);color:var(--dsw-alias-label-primary,#e6e6e6)}
+.dsm-trae-expiry-week{border-color:var(--dsw-alias-border-l2,#3a3d45);background:var(--dsw-alias-bg-layer-3,#2c2f36);color:var(--dsw-alias-label-primary,#e6e6e6)}
+.dsm-trae-expiry-lapsed{border-color:var(--dsw-alias-border-l2,#3a3d45);background:var(--dsw-alias-bg-layer-3,#2c2f36);color:var(--dsw-alias-label-tertiary,#999)}
+.dsm-trae-expiry-detail{font-size:11px;line-height:16px;opacity:.8}
 .dsm-trae-models-hint{margin:4px 0 0;color:var(--dsw-alias-label-tertiary,#999);font-size:11px;line-height:16px}
 /* Verdict badge. Only a real refusal is coloured as a warning; an unknown
    verdict stays neutral because an inconclusive probe is not evidence against
@@ -476,8 +484,8 @@ window.__ModuleLoader__.load({
 		*
 		* SEPARATE from `TRAE_CARD_CSS`, and that is not tidiness: the card's CSS is
 		* only injected when the settings card module loads, so putting the composer's
-		* rules in it means the readout renders UNSTYLED in the composer toolbar —
-		* which is exactly what shipped in 2.13.0–2.13.4. The trigger fell back to the
+		* rules in it means the readout renders UNSTYLED in the composer toolbar 鈥?
+		* which is exactly what shipped in 2.13.0鈥?.13.4. The trigger fell back to the
 		* browser's default button box, and the panel, without `position: fixed`, had
 		* its inline left/top ignored and rendered nowhere useful.
 		*
@@ -485,14 +493,14 @@ window.__ModuleLoader__.load({
 		* renders has a rule here, so a rule cannot go missing without a test failing.
 		*/
 		const COMPOSER_POINTS_CSS = `
-/* The readout is plain composer text — no border, no fill at rest. The padding
+/* The readout is plain composer text 鈥?no border, no fill at rest. The padding
    is only the click target, invisible until the pointer arrives. */
 .dsm-trae-composer-points{display:inline-flex;align-items:center;min-width:0}
 .dsm-trae-composer-points-trigger{
   appearance:none;display:inline-flex;align-items:center;align-self:stretch;
   padding:2px 6px;border:0;border-radius:6px;background:transparent;
   /* EXPLICIT, not inherit. The composer row's own font and body colour are
-     noticeably larger and darker than the neighbouring controls — a credit
+     noticeably larger and darker than the neighbouring controls 鈥?a credit
      readout is secondary information and must not shout. 12px matches this
      plugin's original line; label-tertiary matches the shell's own composer-row
      control (ContextMeter), which is the sibling this reads alongside. */
@@ -504,7 +512,7 @@ window.__ModuleLoader__.load({
 .dsm-trae-composer-points-trigger:hover{background:var(--dsw-alias-interactive-bg-hover,rgba(127,127,127,.14))}
 .dsm-trae-composer-points-trigger:focus-visible{outline:2px solid var(--dsw-alias-brand-primary,#5686fe);outline-offset:1px}
 /* The panel is portaled to document.body and positioned from the trigger, so it
-   MUST be fixed — otherwise the left/top it measures are ignored and it lands in
+   MUST be fixed 鈥?otherwise the left/top it measures are ignored and it lands in
    document flow. All material comes from shell tokens so it follows the theme. */
 .dsm-trae-composer-panel{
   position:fixed;z-index:1100;box-sizing:border-box;
@@ -558,7 +566,7 @@ window.__ModuleLoader__.load({
   color:var(--dsw-alias-label-primary,CanvasText);
 }
 /* The current account reads as current without shouting: a filled dot and a
-   slightly heavier weight. Disabled — pressing it would write a selection that
+   slightly heavier weight. Disabled 鈥?pressing it would write a selection that
    has not changed. */
 .dsm-trae-composer-panel-table tbody tr.dsm-trae-composer-panel-row-current td{font-weight:600}
 .dsm-trae-composer-panel-switch{
@@ -593,6 +601,30 @@ window.__ModuleLoader__.load({
 }
 .dsm-trae-composer-panel-empty{margin:0;color:var(--dsw-alias-label-tertiary,GrayText)}
 .dsm-trae-composer-panel-error{margin:8px 0 0;color:var(--dsw-alias-state-error-primary,#d92d20);font-size:11px;line-height:16px}
+/* Credit-expiry notice. Three tones by urgency, so the 24-hour case cannot be
+   mistaken for the 7-day one at a glance. Reads as an advisory, not an error:
+   the account works fine, the credit is simply about to lapse. */
+.dsm-trae-expiry{
+  display:flex;flex-direction:column;gap:2px;
+  margin-top:9px;padding:8px 10px;border:1px solid;border-radius:8px;
+  font-size:11px;line-height:16px;
+}
+.dsm-trae-expiry-soon{
+  border-color:var(--dsw-alias-state-warn-secondary,#fbbf24);
+  background:var(--dsw-alias-state-warn-tertiary,#fef3c7);
+  color:var(--dsw-alias-label-primary,#1f2329);
+}
+.dsm-trae-expiry-week{
+  border-color:var(--dsw-alias-border-l2,rgba(127,127,127,.36));
+  background:transparent;
+  color:var(--dsw-alias-label-secondary,GrayText);
+}
+.dsm-trae-expiry-lapsed{
+  border-color:var(--dsw-alias-border-l2,rgba(127,127,127,.36));
+  background:transparent;
+  color:var(--dsw-alias-label-tertiary,GrayText);
+}
+.dsm-trae-expiry-detail{font-size:11px;line-height:16px;opacity:.85}
 `;
 		//#endregion
 		//#region src/client/plan-text.ts
@@ -737,6 +769,53 @@ window.__ModuleLoader__.load({
 		function dotStyle(status) {
 			return { background: status === "signed-in" ? "var(--dsw-alias-state-success-primary, #22a06b)" : status === "error" ? "var(--dsw-alias-state-error-primary, #d92d20)" : "var(--dsw-alias-label-dimmed, #9aa0a6)" };
 		}
+		/**
+		* A warning that credit is about to lapse.
+		*
+		* The balance alone cannot express this: a pack lapsing in an hour and one
+		* lapsing next month both render as "150", so a user watching only the total
+		* loses the first one silently. The notice names the amount, the pack count and
+		* the soonest expiry, and escalates 7d → 24h → already-lapsed.
+		*
+		* Renders nothing when the upstream reported no end times at all — absence of
+		* expiry data is not evidence that nothing lapses, so the component stays
+		* silent rather than reassuring.
+		*/
+		function ExpiryNotice({ expiry, t, formatNumber: fmt, formatDateTime: fmtTime }) {
+			const { expired, within24h, within7d } = expiry;
+			let message;
+			let soonest;
+			let tone;
+			if (within24h.packs > 0) {
+				message = t("row.expiryWarningSoon", {
+					total: fmt(within24h.total),
+					packs: String(within24h.packs)
+				});
+				soonest = within24h.earliestExpiresAtMs;
+				tone = "dsm-trae-expiry-soon";
+			} else if (within7d.packs > 0) {
+				message = t("row.expiryWarningWeek", {
+					total: fmt(within7d.total),
+					packs: String(within7d.packs)
+				});
+				soonest = within7d.earliestExpiresAtMs;
+				tone = "dsm-trae-expiry-week";
+			} else if (expired.packs > 0) {
+				message = t("row.expiryWarningLapsed", {
+					total: fmt(expired.total),
+					packs: String(expired.packs)
+				});
+				tone = "dsm-trae-expiry-lapsed";
+			} else return null;
+			return /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
+				className: `dsm-trae-expiry ${tone}`,
+				role: "status",
+				children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: message }), soonest === void 0 ? null : /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
+					className: "dsm-trae-expiry-detail",
+					children: t("row.expiryEarliest", { time: fmtTime(soonest) })
+				})]
+			});
+		}
 		/** Render Trae sign-in state and the total usage summary as one expandable card. */
 		function TraeUsageCard({ t, settingsScope, view }) {
 			if (t === void 0) throw new Error("Trae usage card requires its translation function");
@@ -1905,6 +1984,12 @@ window.__ModuleLoader__.load({
 											children: t("row.creditsAlternativeSwitch")
 										})]
 									}) : null,
+									status.status === "signed-in" && status.credits?.expiry !== void 0 ? /* @__PURE__ */ (0, react_jsx_runtime.jsx)(ExpiryNotice, {
+										expiry: status.credits.expiry,
+										t,
+										formatNumber,
+										formatDateTime
+									}) : null,
 									status.status === "signed-in" && status.appLogin !== void 0 ? /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
 										className: "dsm-trae-usage-alternative",
 										role: "status",
@@ -2365,6 +2450,36 @@ window.__ModuleLoader__.load({
 		function formatCredits(value) {
 			return value.toLocaleString("en-US", { maximumFractionDigits: 0 });
 		}
+		/** The soonest expiry any bucket names, or undefined when none carries one. */
+		function soonestExpiryOf(expiry) {
+			return expiry.within24h.earliestExpiresAtMs ?? expiry.within7d.earliestExpiresAtMs ?? void 0;
+		}
+		/**
+		* Which urgency tone the notice takes.
+		*
+		* Escalation order matters: a live expiry the user can still act on outranks a
+		* lapsed one they cannot, even when the lapsed amount is larger.
+		*/
+		function expiryToneOf(expiry) {
+			if (expiry.within24h.packs > 0) return "dsm-trae-expiry-soon";
+			if (expiry.within7d.packs > 0) return "dsm-trae-expiry-week";
+			return "dsm-trae-expiry-lapsed";
+		}
+		/** The notice's headline sentence, naming the amount and the pack count. */
+		function expiryMessageOf(expiry, t) {
+			if (expiry.within24h.packs > 0) return t("row.expiryWarningSoon", {
+				total: formatCredits(expiry.within24h.total),
+				packs: String(expiry.within24h.packs)
+			});
+			if (expiry.within7d.packs > 0) return t("row.expiryWarningWeek", {
+				total: formatCredits(expiry.within7d.total),
+				packs: String(expiry.within7d.packs)
+			});
+			return t("row.expiryWarningLapsed", {
+				total: formatCredits(expiry.expired.total),
+				packs: String(expiry.expired.packs)
+			});
+		}
 		function formatClock(value) {
 			return new Date(value).toLocaleTimeString("zh-CN", {
 				hour: "2-digit",
@@ -2690,6 +2805,14 @@ window.__ModuleLoader__.load({
 								}, row.id);
 							}) })]
 						}),
+						activeRegion === "cn" && signedIn?.credits?.expiry !== void 0 ? /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("div", {
+							className: `dsm-trae-expiry ${expiryToneOf(signedIn.credits.expiry)}`,
+							role: "status",
+							children: [/* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: expiryMessageOf(signedIn.credits.expiry, t) }), soonestExpiryOf(signedIn.credits.expiry) === void 0 ? null : /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
+								className: "dsm-trae-expiry-detail",
+								children: t("row.expiryEarliest", { time: formatClock(soonestExpiryOf(signedIn.credits.expiry)) })
+							})]
+						}) : null,
 						/* @__PURE__ */ (0, react_jsx_runtime.jsx)("div", {
 							className: "dsm-trae-composer-panel-foot",
 							children: /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", { children: [
@@ -2884,6 +3007,10 @@ window.__ModuleLoader__.load({
 			"row.creditsExhausted": "The bound account ({account}) has run out of credit",
 			"row.creditsAlternative": "Another account on this machine still has credit: {accounts}",
 			"row.creditsAlternativeSwitch": "Switch to it",
+			"row.expiryWarningSoon": "{total} credit lapses within 24 hours ({packs} packs)",
+			"row.expiryWarningWeek": "{total} credit lapses within 7 days ({packs} packs)",
+			"row.expiryWarningLapsed": "{total} credit has already lapsed but is still counted in the balance ({packs} packs)",
+			"row.expiryEarliest": "Earliest: {time}",
 			"row.appLoginMismatch": "Trae is signed in to {account}, but this plugin is bound to {bound}.",
 			"row.appLoginFollow": "Use {account}",
 			"row.followAppLogin": "Follow the account Trae is signed in to",
@@ -3021,6 +3148,10 @@ window.__ModuleLoader__.load({
 			"row.creditsExhausted": "当前绑定账号（{account}）额度已用尽",
 			"row.creditsAlternative": "本机还有可用账号：{accounts}",
 			"row.creditsAlternativeSwitch": "切换到它",
+			"row.expiryWarningSoon": "有 {total} 积分将在 24 小时内过期（{packs} 个套餐）",
+			"row.expiryWarningWeek": "有 {total} 积分将在 7 天内过期（{packs} 个套餐）",
+			"row.expiryWarningLapsed": "有 {total} 积分已过期但仍计入余额（{packs} 个套餐）",
+			"row.expiryEarliest": "最早到期：{time}",
 			"row.appLoginMismatch": "Trae 已登录 {account}，但本插件绑定的是 {bound}。",
 			"row.appLoginFollow": "改用 {account}",
 			"row.followAppLogin": "跟随 Trae 当前登录的账号",

package/lib/index.d.ts

@@ -237,9 +237,10 @@ interface TraeWireModel {
  * their own Trae IDE offers. The row therefore ships, and its call fails
  * honestly: the bridge now translates the in-stream refusal into a readable
  * error (`4001` → "Trae does not serve this model under the SOLO function the
- * request used", `4011` → "Trae refused this model under the SOLO function the
- * request used"), so a user who picks an unusable model is told why instead of
- * seeing nothing. This reverses the 2026-08-30 note about `Doubao-Seed-Code`,
+ * request used", `4011` → "Trae throttled the SOLO channel for this account",
+ * the second one corrected by issue #33 — 4011 is a rate limit, see
+ * src/solo-bridge.ts), so a user who picks an unusable model is told why instead
+ * of seeing nothing. This reverses the 2026-08-30 note about `Doubao-Seed-Code`,
  * which later turned out to be callable under `chat_v3`.
  *
  * Credit multiplier precedence: the wire's `display_contact_config` rate wins
@@ -1657,6 +1658,29 @@ interface TraeWebCreditAccount {
    */
   expiresAtMs?: number;
 }
+/** Credit lapsing inside one horizon, as the card reports it. */
+interface TraeWebExpiringCredits {
+  /** Sum of the contributing packs' remaining credit. */
+  total: number;
+  /** How many packs contribute. */
+  packs: number;
+  /** Soonest expiry among them, epoch milliseconds. */
+  earliestExpiresAtMs?: number;
+}
+/**
+ * Credit at risk, bucketed by how soon it lapses.
+ *
+ * Only present when at least one pack carried a usable `expiresAtMs` — a card
+ * must never read "we were not told when anything expires" as "nothing is
+ * about to lapse".
+ */
+interface TraeWebCreditExpiry {
+  within24h: TraeWebExpiringCredits;
+  within3d: TraeWebExpiringCredits;
+  within7d: TraeWebExpiringCredits;
+  /** Packs already past their end time but still carrying credit. */
+  expired: TraeWebExpiringCredits;
+}
 /** Aggregated usage/credit answer rendered by the plugin card. */
 interface TraeWebCredits {
   total: number;
@@ -1665,6 +1689,13 @@ interface TraeWebCredits {
   workAvailable: number;
   generalAvailable: number;
   accounts: readonly TraeWebCreditAccount[];
+  /**
+   * Credit lapsing soon, for the card's warning banner.
+   *
+   * Derived from the per-pack {@link TraeWebCreditAccount.expiresAtMs} the
+   * `/usage` route already carries, so it costs no extra upstream read.
+   */
+  expiry?: TraeWebCreditExpiry;
 }
 /** Editable Trae model row rendered by the plugin-owned settings card. */
 interface TraeWebModel {

package/lib/index.js

@@ -197,9 +197,10 @@ function displayKey(name) {
 * their own Trae IDE offers. The row therefore ships, and its call fails
 * honestly: the bridge now translates the in-stream refusal into a readable
 * error (`4001` → "Trae does not serve this model under the SOLO function the
-* request used", `4011` → "Trae refused this model under the SOLO function the
-* request used"), so a user who picks an unusable model is told why instead of
-* seeing nothing. This reverses the 2026-08-30 note about `Doubao-Seed-Code`,
+* request used", `4011` → "Trae throttled the SOLO channel for this account",
+* the second one corrected by issue #33 — 4011 is a rate limit, see
+* src/solo-bridge.ts), so a user who picks an unusable model is told why instead
+* of seeing nothing. This reverses the 2026-08-30 note about `Doubao-Seed-Code`,
 * which later turned out to be callable under `chat_v3`.
 *
 * Credit multiplier precedence: the wire's `display_contact_config` rate wins
@@ -2407,9 +2408,14 @@ const TRAE_SOLO_FUNCTION = "solo_work_lite";
 * live SG credential, issue #19): it is a Remote-agent roster function, not a
 * chat function. Every model sent with `function: "solo_agent"` — `gpt-5.4`,
 * `gpt-5.6-sol`, `gpt-6-astra`, `glm-5.2`, `kimi-k2.7-code` — answered
-* `event:error {"code":4011}` (message says "rate limit", it is really "not
-* served here"), while the same model with the same body answered normally
-* under `solo_work_remote` / `solo_work_lite` / `solo_agent_remote`.
+* `event:error {"code":4011}`, while the same model with the same body answered
+* normally under `solo_work_remote` / `solo_work_lite` / `solo_agent_remote`.
+* Issue #33 corrected the reading of that code: `4011` is Trae's rate limit on
+* the route that was asked (its own text says so, and issue #33's reporter hit
+* it on the CORRECT function), and the "this route does not serve that model"
+* condition is `4001` — measured on all 22 functions of a live CN credential.
+* The conclusion for this list is unchanged either way: a route that refuses
+* chat is not a chat route, so `solo_agent` stays out.
 *
 * Note `get_detail_param` DOES answer `solo_agent` with a 43-entry list, so
 * asking it looks helpful while making 8 of the 10 exposed ai-region models
@@ -2809,22 +2815,38 @@ function decodeTraeEvent(event) {
 //#endregion
 //#region src/solo-bridge.ts
 /**
-* What Trae's in-stream error codes mean. Measured 2026-10-01 on a live SG
-* credential (issue #19), by sending the same body to several functions:
+* What Trae's in-stream error codes mean. Measured 2026-10-01 on live
+* credentials (issue #19), and re-measured 2026-10-12 on a live CN credential
+* (issue #33) with a 22-function × 6-model chat matrix:
 *
 *  - `1005` — the model needs a paid plan. Trae answers HTTP 200 with
 *    `event:error {"code":1005,"message":"","extra":"{\"plan\":1}"}`, so the
 *    gate is only visible in `extra.plan`; `gpt-6-sol` returned it under both
 *    `solo_work_remote` and `solo_agent_remote` on a free account.
-*  - `4011` — the function the request named does not serve that model. Its
-*    message claims "exceeded the rate limit", which is misleading: the same
-*    model answers normally when sent under `solo_work_remote`.
+*  - `4011` — Trae throttled the SOLO route for this account. Trae's own text
+*    is `your requests have exceeded the rate limit. Please wait and try again
+*    later.`, and issue #33 is why that text is now taken at face value: the
+*    earlier reading of 4011 as "this function does not serve that model" is
+*    contradicted by measurement. On CN that condition is `4001`, and all 22
+*    functions answered `4001` — never `4011` — for a model absent from their
+*    roster, while `glm-5.3` streamed normally under its own function. Rate
+*    limiting is per account, route and moment, which is exactly the shape of
+*    that report: the same model through the same function was fine for days
+*    and then failed, with Trae's own text saying "rate limit".
 *  - `4001` — `config_name` is not one this function serves.
+*  - `4008` — the account's SOLO quota is exhausted. Deliberately a different
+*    code from `4011`: Trae words this one `your requests have exceeded the
+*    quota`, so "I still have plenty of credits" and "I am being throttled" are
+*    two different statements, and a user hits the second without touching the
+*    first (issue #33).
+*  - `4023` — the model name is unknown on the route that was asked.
 */
 const TRAE_ERROR_HINTS = {
 	1005: "Trae requires a paid plan for this model; the current account's plan does not cover it",
 	4001: "Trae does not serve this model under the SOLO function the request used (config_name rejected)",
-	4011: "Trae refused this model under the SOLO function the request used"
+	4008: "Trae reports the account's SOLO quota is exhausted for this request",
+	4011: "Trae throttled the SOLO channel for this account (a rate limit, not the credit balance)",
+	4023: "Trae does not recognise this model name on the SOLO route that was asked"
 };
 /** `extra` is a JSON *string* on the wire; unwrap it to read `plan`. */
 function traeErrorPlan(extra) {
@@ -2854,13 +2876,30 @@ function describeTraeFailure(failure) {
 * answer with a real error instead of a truncated 200 stream.
 *
 * `1005` is a subscription gate: 402 is what makes clients stop rather than
-* retry, and it is truthful. Everything else is a client-side rejection.
+* retry, and it is truthful.
+*
+* `4011` is a rate limit and is reported as one — `429` / `soft_rate` (issue
+* #33). It previously answered `400` / `client`, which contradicted both its own
+* message and the client's own behaviour: pi-ai classifies an error by its text
+* (`/\b429\b|rate.?limit/i` → `RATE_LIMIT`), and `RATE_LIMIT` is retryable, so
+* the kernel retried five times with backoff while this function called the same
+* failure a non-retryable client error. Reporting the real status makes all
+* three agree, and `soft_rate` is already what `fallback-upstream` refuses to
+* replay — correct, since a throttled route is not a route-compatibility
+* problem.
+*
+* Everything else stays a client-side rejection.
 */
 function classifyTraeFailure(failure) {
-	return failure.code === 1005 ? {
+	if (failure.code === 1005) return {
 		status: 402,
 		kind: "hard_credit"
-	} : {
+	};
+	if (failure.code === 4011) return {
+		status: 429,
+		kind: "soft_rate"
+	};
+	return {
 		status: 400,
 		kind: "client"
 	};
@@ -3934,9 +3973,41 @@ var TraeDelegatingUpstreamClient = class {
 * beyond this the answer is not worth waiting for and is reported as unknown.
 */
 const TRAE_PROBE_TIMEOUT_MS = 3e4;
-/** Upstream error codes the probe recognises, and what they mean. */
-const GATE_CODES = /* @__PURE__ */ new Set([1005]);
-const UNSUPPORTED_CODES = /* @__PURE__ */ new Set([4001, 4011]);
+/**
+* Every upstream code the probe recognises, mapped to the verdict it implies.
+*
+* ONE table, not a set per verdict: with separate sets the outcome depended on
+* the order the branches happened to be written in, so a code left in two sets
+* was silently decided by whichever line ran first (measured: re-adding `4011`
+* to the "unsupported" set passed every test). A single map makes a code mean
+* exactly one thing, and {@link assertCodesAreDistinct} pins that down at
+* module load.
+*
+*  - `1005` — the plan does not cover this model (`extra.plan` carries the
+*    tier). A paying account may pass, so it is a gate, not a dead model.
+*  - `4001` — this function's roster does not contain that `config_name`. The
+*    ONLY code that may produce `unsupported`, measured on all 22 functions of
+*    a live CN credential (issue #33).
+*  - `4011` — Trae throttled the route; its own text says the rate limit was
+*    exceeded. Issue #33 moved this here from `unsupported`: reporting a
+*    throttle as "the channel does not serve it" told users a working model was
+*    dead.
+*  - `4008` — the ACCOUNT's SOLO quota is exhausted. It says nothing about any
+*    one model, so it must not become a model verdict; it stays inconclusive
+*    and carries the upstream text, so the user retests once the quota is back.
+*/
+const CODE_VERDICTS = {
+	1005: "gated",
+	4001: "unsupported",
+	4008: "unknown",
+	4011: "rate_limited"
+};
+/** A code that maps to two verdicts would make the table order-dependent. */
+function assertCodesAreDistinct(table) {
+	const codes = Object.keys(table);
+	if (new Set(codes).size !== codes.length) throw new Error("dsh-connect-trae: a Trae probe code maps to more than one verdict");
+}
+assertCodesAreDistinct(CODE_VERDICTS);
 /** Pull `Trae code N` out of an already-translated failure message. */
 function codeOf(message) {
 	const match = /Trae code (\d+)/u.exec(message);
@@ -3992,12 +4063,9 @@ function classifyProbeResult(result, outputSeen) {
 		detail: message
 	};
 	const code = codeOf(message);
-	if (code !== void 0 && GATE_CODES.has(code)) return {
-		verdict: "gated",
-		detail: message
-	};
-	if (code !== void 0 && UNSUPPORTED_CODES.has(code)) return {
-		verdict: "unsupported",
+	const mapped = code === void 0 ? void 0 : CODE_VERDICTS[code];
+	if (mapped !== void 0) return {
+		verdict: mapped,
 		detail: message
 	};
 	if (result.kind === "client" && result.status >= 400 && result.status < 500) return {
@@ -4456,6 +4524,17 @@ function loopbackOrigin(req) {
 	}
 }
 /**
+* Whether a pack's expiry is one the card can actually use.
+*
+* One predicate, shared by the per-pack projection and the bucket summary, so
+* the two can never disagree about which packs count as dated. `0` and the
+* non-finite values are excluded: a `0` here would read as 1970 and sort ahead
+* of every real date, and `NaN`/`Infinity` are not dates at all.
+*/
+function usableExpiry(endTimeMs) {
+	return typeof endTimeMs === "number" && Number.isFinite(endTimeMs) && endTimeMs > 0;
+}
+/**
 * Map the credit snapshot to the card's compact credit document.
 *
 * Exported so the "is another account usable?" probe (issue #25) derives its
@@ -4463,14 +4542,14 @@ function loopbackOrigin(req) {
 * — a second implementation of the Work/general split would be free to disagree
 * with the number shown next to it.
 */
-function toCredits(snapshot) {
+function toCredits(snapshot, nowMs = Date.now()) {
 	const { totalAmount, consumedAmount } = snapshot.summary;
 	const credit = (value) => Math.round(value * 1e4) / 1e4;
 	const accounts = snapshot.packs.map((pack) => ({
 		displayDesc: pack.displayDesc,
 		remain: credit(Math.max(0, (pack.creditsLimit ?? 0) - (pack.consumedCredits ?? 0))),
 		size: pack.creditsLimit ?? 0,
-		...typeof pack.endTimeMs === "number" && Number.isFinite(pack.endTimeMs) && pack.endTimeMs > 0 ? { expiresAtMs: pack.endTimeMs } : {}
+		...usableExpiry(pack.endTimeMs) ? { expiresAtMs: pack.endTimeMs } : {}
 	}));
 	const remaining = (endpoint) => snapshot.packs.filter((pack) => pack.availableEndpoint === endpoint).reduce((sum, pack) => credit(sum + Math.max(0, (pack.creditsLimit ?? 0) - (pack.consumedCredits ?? 0))), 0);
 	return {
@@ -4479,9 +4558,74 @@ function toCredits(snapshot) {
 		available: totalAmount - consumedAmount,
 		workAvailable: remaining(1),
 		generalAvailable: remaining(0),
-		accounts
+		accounts,
+		...summarisePackExpiry(accounts, nowMs)
 	};
 }
+/** Empty bucket, used whenever no pack qualifies. */
+const NO_EXPIRING_CREDIT = {
+	total: 0,
+	packs: 0
+};
+/**
+* Sum the credit lapsing inside `horizonMs` of `nowMs`.
+*
+* Only positive balances count: a lapsed pack with nothing left is not a loss,
+* and including it would make every long-lived account look permanently at
+* risk. Only *future* expiries count too — see {@link expiredPacks}.
+*/
+function expiringWithin(packs, nowMs, horizonMs) {
+	return sumExpiring(packs, (expiresAt) => expiresAt > nowMs && expiresAt - nowMs <= horizonMs);
+}
+/**
+* Sum the credit whose pack has already lapsed but still carries a balance.
+*
+* Kept apart from {@link expiringWithin} because a lapsed pack satisfies every
+* forward-looking horizon at once (`expiresAt - now` is negative, hence "within
+* 24 hours"), which would make a long-dead pack look permanently imminent.
+*/
+function expiredPacks(packs, nowMs) {
+	return sumExpiring(packs, (expiresAt) => expiresAt <= nowMs);
+}
+/** Shared accumulator over packs whose expiry passes `matches`. */
+function sumExpiring(packs, matches) {
+	let total = 0;
+	let count = 0;
+	let earliestExpiresAtMs;
+	for (const pack of packs) {
+		const expiresAt = pack.expiresAtMs;
+		if (!usableExpiry(expiresAt) || pack.remain <= 0) continue;
+		if (!matches(expiresAt)) continue;
+		total += pack.remain;
+		count += 1;
+		if (earliestExpiresAtMs === void 0 || expiresAt < earliestExpiresAtMs) earliestExpiresAtMs = expiresAt;
+	}
+	if (count === 0) return NO_EXPIRING_CREDIT;
+	return {
+		total,
+		packs: count,
+		...earliestExpiresAtMs === void 0 ? {} : { earliestExpiresAtMs }
+	};
+}
+/**
+* Bucket the card's credit by how soon it lapses.
+*
+* Returns no `expiry` at all when not one pack carried a usable end time, so a
+* caller can tell "nothing is expiring" apart from "we were never told when
+* anything expires" — the second must not render as reassurance. Uses the same
+* {@link usableExpiry} predicate as the per-pack projection, so a summary is
+* never produced from a set of dates the card itself would not carry.
+*/
+function summarisePackExpiry(accounts, nowMs) {
+	if (!accounts.some((pack) => usableExpiry(pack.expiresAtMs))) return {};
+	const DAY = 864e5;
+	return { expiry: {
+		within24h: expiringWithin(accounts, nowMs, DAY),
+		within3d: expiringWithin(accounts, nowMs, 3 * DAY),
+		within7d: expiringWithin(accounts, nowMs, 7 * DAY),
+		expired: expiredPacks(accounts, nowMs)
+	} };
+}
 /** Map the check-in answer to the card's compact document. */
 function toCheckin(status) {
 	return {

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "3.3.0",
+  "version": "3.4.1",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",