dsh-workbuddy-bridge 0.3.0 → 0.4.0

package/README.md

@@ -2,9 +2,7 @@
   <img src="icon.svg" alt="dsh-workbuddy-bridge" width="80" height="80">
 </p>
 
-<p align="center">
-  <h1 align="center">dsh-workbuddy-bridge</h1>
-</p>
+<h1 align="center">dsh-workbuddy-bridge</h1>
 
 <div align="center">
   <p><strong>把 WorkBuddy 桌面 App 的模型接进 DSH 对话窗口</strong></p>
@@ -46,16 +44,18 @@
 - **开箱即用** —— 装完启用，模型分组自己出现。
 - **两版隔离** —— 国内版与国际版各自分组，模型、账号、积分互不混用，只跟随各自 App 的登录状态。
 - **推理档位** —— 上游声明了档位的模型直接可选；没声明的可在插件页**手动检测**。
-  灯泡表示「这个模型能切档位」，不是「检测过」——已声明的模型也显示灯泡，只是不需要检测。
-- **积分可见** —— 每条回复下方显示本次消耗，模型选择器旁常驻剩余积分。观测不到就不显示。
+- **推理档位** —— 上游声明了档位的模型直接可选；没声明的可在插件页**手动检测**。
+  灯泡表示能切档位；上游已声明的模型也亮着，只是不需要检测。
+  能切档位的模型会带一个**默认档位**（上游声明了就按声明，否则取 `high`），因此选择器里不再出现「Default」这一项。
+- **积分可见** —— 每条回复下方显示本次消耗，模型选择器旁常驻剩余积分。拿不到数字时不显示。
 - **模型显隐** —— 卡片「模型」标签里勾选哪些模型出现在选择器里，按登录账号分别保存。
 - **图片输入** —— 多数模型可直接粘贴或拖入图片；纯文字模型会明确说明。
 - **三种界面** —— Web / Desktop / TUI；仅 TUI 无手动检测。
 
 <p align="center">
-  <img src="assets/composer-row.png" alt="输入区那一行：剩余积分与推理档位灯泡并排" width="560">
+  <img src="assets/composer-row.png" alt="输入区那一行：币图标与余额、推理档位灯泡、模型名，从左到右一行" width="560">
   <br>
-  <em>对话窗口里每天看到的样子：左边是剩余积分，右边是推理档位灯泡——都在模型选择器旁。</em>
+  <em>对话窗口里每天看到的样子：币图标与余额、推理档位灯泡，再往右是模型名——都排在同一行。</em>
 </p>
 
 <p align="center">
@@ -73,8 +73,8 @@ dsh plugin --profile web add dsh-workbuddy-bridge
 dsh web
 ```
 
-Desktop 与 TUI 把 `--profile web` 换成 `desktop` / `dsh-tui`（TUI 需终端插件
-`@deepseek-harness-tui/dsh-tui` ≥ `0.10.0-beta.5`，详见其文档）。
+Desktop 与 TUI 把 `--profile web` 换成 `desktop` / `dsh-tui`（TUI 需较新版本的终端插件
+`@deepseek-harness-tui/dsh-tui`，版本要求见其文档）。
 
 也可以从源码安装：
 
@@ -85,6 +85,9 @@ pnpm install && pnpm build
 dsh plugin --profile web add "$PWD"
 ```
 
+⚠️ 上面那步 `pnpm install` 不能省：按路径挂载时依赖要由仓库自己装好（见[本地开发装法](docs/PUBLISHING.md)），
+漏装则插件显示「未运行」（`ERR_MODULE_NOT_FOUND`）。
+
 ## 插件页
 
 侧边栏 **插件（Plugins）** → 已安装 → 点 **DSH WorkBuddy Bridge**。配置区在描述下面，保存即生效：
@@ -100,14 +103,14 @@ dsh plugin --profile web add "$PWD"
 
 <p align="center">
   <img src="assets/detection-tab.png" alt="检测标签：每个推理模型一行" width="300">
-  <img src="assets/credits-tab.png" alt="积分标签：合计与套餐余量" width="300">
+  <img src="assets/credits-tab.png" alt="积分标签：总余额与各套餐余量条" width="300">
   <br>
-  <em>左「检测」：每个推理模型一行，点按钮确认它接受哪些推理档位；右「积分」：合计一行，下面是各套餐余量条。</em>
+  <em>左「检测」：每个推理模型一行，点按钮确认它接受哪些推理档位；右「积分」：总余额，下面是各套餐的余量条。</em>
 </p>
 
 ## 为什么是手动检测
 
-上游不保证档位信息可靠——实测有的模型**接受** `reasoning_effort` 却忽略未知值。
+WorkBuddy 接口不保证档位信息可靠——有的模型**接受** `reasoning_effort` 却忽略未知值。
 所以插件不猜：按需对单个模型发少量真实请求确认；结果只表示**上游当前接受该档位**，
 不承诺它改变推理行为。已声明档位的模型跳过这一步，直接用声明值。
 机制与取舍见 [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)。
@@ -120,7 +123,7 @@ dsh plugin --profile web add "$PWD"
 
 ## 兼容与限制
 
-无凭据的分组不显示。宿主版本下限、平台支持、目录来源与已知缺口
+无凭据的分组不显示。宿主版本下限、平台支持、模型清单从哪来与已知缺口
 → [docs/COMPATIBILITY.md](docs/COMPATIBILITY.md)。
 
 设计取舍 → [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md)；发版流程 → [docs/PUBLISHING.md](docs/PUBLISHING.md)；
@@ -128,7 +131,7 @@ dsh plugin --profile web add "$PWD"
 
 ## 免责声明
 
-- 本项目**仅供个人学习和研究使用**，仅驱动使用者自己的 WorkBuddy 账号在本机调用，请勿用于商业用途或超出个人合理使用的场景。
+- 本项目**仅供个人学习和研究使用**，仅驱动使用者自己的 WorkBuddy 账号在本机调用，请勿用于商业用途。
 - 使用者需遵守 WorkBuddy 的服务条款；因使用本项目产生的任何后果，由使用者自行承担。
 - 本项目与腾讯、WorkBuddy、DeepSeek 均无关联，未获其授权或认可；文中出现的名称仅用于描述兼容关系，其商标权利归各自所有。
 

package/README_en.md

@@ -2,12 +2,11 @@
   <img src="icon.svg" alt="dsh-workbuddy-bridge" width="80" height="80">
 </p>
 
-<p align="center">
-  <h1 align="center">dsh-workbuddy-bridge</h1>
-</p>
+<h1 align="center">dsh-workbuddy-bridge</h1>
 
 <div align="center">
   <p><strong>WorkBuddy desktop models in DeepSeek Harness</strong></p>
+  <p><em>把 WorkBuddy 桌面 App 的模型接进 DSH 对话窗口</em></p>
 
   <p>
     <a href="https://www.npmjs.com/package/dsh-workbuddy-bridge"><img src="https://img.shields.io/npm/v/dsh-workbuddy-bridge?style=flat" alt="npm"></a>
@@ -29,8 +28,7 @@
 
 > [!NOTE]
 > **Credentials never leave this machine**: sign-in state is read from the WorkBuddy desktop app's own
-> credential file and kept as one encrypted local copy; the browser half never sees a token, and none
-> ever appears in the UI.
+> credential file and kept as one encrypted local copy; the browser half never sees a token, and none ever appears in the UI.
 
 The CN **WorkBuddy** and the international **WorkBuddy AI** coexist: install one app and its model group
 appears; install both and the two groups sit side by side, each with its own account and credit. The
@@ -49,20 +47,21 @@ models appear directly in the DSH model picker — no separate provider to confi
 - **Two isolated versions** — "WorkBuddy" (CN) and "WorkBuddy AI" (international) each form their own group;
   models, accounts and credit never mix, and each follows only its own app's sign-in.
 - **Reasoning levels** — models that declare levels expose them directly; the rest can be **checked manually**
-  on the plugin page. The bulb means "this model can switch levels", not "it has been detected" — a declared
-  model shows the bulb too, it just has nothing to detect.
+  on the plugin page. The bulb means "this model can switch levels"; a declared model shows it too, it just
+  has nothing to detect. A switchable model also carries a **default level** (the upstream's own declaration
+  when it has one, otherwise `high`), so the picker no longer offers "Default".
 - **Credit in view** — each reply shows what it consumed, and remaining credit sits beside the model picker.
-  Nothing renders when a figure cannot be observed.
+  Nothing renders when a figure is unavailable.
 - **Model visibility** — tick which models appear in the picker on the card's "Models" tab, saved per
   signed-in account.
 - **Image input** — most models accept pasted or dropped images; text-only models say so explicitly.
 - **Three surfaces** — Web, Desktop and TUI; only the TUI lacks manual detection.
 
 <p align="center">
-  <img src="assets/composer-row.png" alt="The composer row: remaining credit beside the reasoning-level bulb" width="560">
+  <img src="assets/composer-row.png" alt="The composer row: the coin and balance, the reasoning-level bulb and the model name in one line" width="560">
   <br>
-  <em>The everyday view in the conversation window: remaining credit on the left, the reasoning-level bulb on
-  the right — both beside the model picker.</em>
+  <em>The everyday view in the conversation window: the coin and its balance, the reasoning-level bulb, then the
+  model name — one row, left to right.</em>
 </p>
 
 <p align="center">
@@ -81,8 +80,8 @@ dsh plugin --profile web add dsh-workbuddy-bridge
 dsh web
 ```
 
-For Desktop and TUI swap `--profile web` for `desktop` / `dsh-tui` (the TUI needs the terminal plugin
-`@deepseek-harness-tui/dsh-tui` ≥ `0.10.0-beta.5` — see its docs).
+For Desktop and TUI swap `--profile web` for `desktop` / `dsh-tui` (the TUI needs a recent version of
+the terminal plugin `@deepseek-harness-tui/dsh-tui` — see its docs).
 
 Or from source:
 
@@ -93,6 +92,10 @@ pnpm install && pnpm build
 dsh plugin --profile web add "$PWD"
 ```
 
+⚠️ The `pnpm install` above is not optional: under a path install the repository has to supply
+its own dependencies (see [local development setup](docs/PUBLISHING.md)) — skip it and the
+plugin shows as "not running" (`ERR_MODULE_NOT_FOUND`).
+
 ## The plugin page
 
 Sidebar **Plugins** → installed → click **DSH WorkBuddy Bridge**. The configuration area sits right under
@@ -109,15 +112,15 @@ the description and takes effect on save:
 
 <p align="center">
   <img src="assets/detection-tab.png" alt="Detection tab: one row per reasoning model" width="300">
-  <img src="assets/credits-tab.png" alt="Credits tab: total and per-package allowances" width="300">
+  <img src="assets/credits-tab.png" alt="Credits tab: the total balance and per-package allowances" width="300">
   <br>
   <em>Left, "Detection": one row per reasoning model — press the button to confirm which reasoning levels it
-  accepts. Right, "Credits": the total on one line, each package's allowance as a bar below.</em>
+  accepts. Right, "Credits": the total balance, each package's allowance as a row below.</em>
 </p>
 
 ## Why detection is manual
 
-The upstream does not guarantee that level information is reliable — some models were observed to
+The WorkBuddy API does not guarantee that level information is reliable — some models were observed to
 **accept** `reasoning_effort` while silently ignoring unknown values. So the plugin does not guess: it
 confirms one model at a time with a few real requests on demand, and a result only means **the upstream
 currently accepts that level** — it does not promise any change in behaviour. Models that declare their
@@ -132,8 +135,8 @@ Mechanism and trade-offs in [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md).
 
 ## Compatibility and limits
 
-A group without credentials does not appear. The host version floor, platform support, catalog sources and
-known gaps
+A group without credentials does not appear. The host version floor, platform support, where the model
+catalog comes from and known gaps
 → [docs/COMPATIBILITY.md](docs/COMPATIBILITY.md).
 
 Design notes → [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md); release process → [docs/PUBLISHING.md](docs/PUBLISHING.md);
@@ -142,7 +145,7 @@ maintainer map → [AGENTS.md](AGENTS.md).
 ## Disclaimer
 
 - This project is **for personal study and research only**; it drives your own WorkBuddy account on your own
-  machine. Do not use it commercially or beyond reasonable personal use.
+  machine. Do not use it commercially.
 - You must comply with WorkBuddy's terms of service; any consequences are your own responsibility.
 - Not affiliated with, nor endorsed by, Tencent, WorkBuddy, or DeepSeek; names appear only to describe
   compatibility, and trademarks belong to their owners.

package/lib/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import { D as WorkBuddyAtRestKeyProvider, O as cnAppDiscovery, Z as resolveAppVersion, _ as FALLBACK_WORKBUDDY_MODELS, f as WORKBUDDY_BRIDGE_VERSION, g as FALLBACK_WORKBUDDY_AI_MODELS, i as variantFor, k as WorkBuddyUpstreamClient, l as readHostHeartbeat, n as CN_VARIANT, r as WORKBUDDY_VARIANTS, s as isHeartbeatProcessAlive, u as workbuddyHostHeartbeatPath, x as WorkBuddyCredentialStore } from "./variants-3SmUZ0e_.js";
+import { C as variantFor, D as WorkBuddyUpstreamClient, S as WORKBUDDY_VARIANTS, Y as resolveAppVersion, a as readHostHeartbeat, c as WORKBUDDY_BRIDGE_VERSION, l as FALLBACK_WORKBUDDY_AI_MODELS, m as WorkBuddyCredentialStore, o as workbuddyHostHeartbeatPath, r as isHeartbeatProcessAlive, u as FALLBACK_WORKBUDDY_MODELS, x as CN_VARIANT } from "./heartbeat-CP6YM98x.js";
 import { realpathSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 //#region src/cli/bin.ts
@@ -29,17 +29,18 @@ function printJson(value) {
 /**
 * One variant's store plus the client that performs its refreshes.
 *
-* The key provider is injected explicitly, and per variant, for the same
-* reason the plugin host does it: the provider must not be left to its no-arg
-* default — that default is deliberately `discovery: 'none'`, and relying on it
-* here would quietly strip the CN CLI of the decryption it has always had.
+* No key provider is injected, and that is now correct rather than a trap: the
+* store's own default runs the discovery its variant may use
+* (`atRestDiscoveryFor`, see `src/credential/store.ts`). This file used to spell
+* that choice out per call site because the provider's no-arg default is
+* `discovery: 'none'` — which left every caller that forgot it, including
+* `scripts/live-e2e.mjs`, unable to open an encrypted credential at all.
 */
 function makeStore(variant) {
 	const client = new WorkBuddyUpstreamClient();
 	return new WorkBuddyCredentialStore({
 		variant,
-		refresh: (credential) => client.refreshToken(credential),
-		keyProvider: new WorkBuddyAtRestKeyProvider({ discovery: variant.id === CN_VARIANT.id ? cnAppDiscovery() : "none" })
+		refresh: (credential) => client.refreshToken(credential)
 	});
 }
 /** The plugin-owned credential copy for one variant, for display. */