dsh-workbuddy-bridge 0.5.0 → 0.5.2

package/README.md

@@ -47,10 +47,11 @@
 
 - **开箱即用** —— 装完启用，模型分组自己出现。
 - **两版隔离** —— 国内版与国际版各自分组，模型、账号、积分互不混用，只跟随各自 App 的登录状态。
-- **推理档位** —— 上游声明了档位的模型直接可选；没声明的可在插件页**手动检测**。
 - **推理档位** —— 上游声明了档位的模型直接可选；没声明的可在插件页**手动检测**。
   灯泡表示能切档位；上游已声明的模型也亮着，只是不需要检测。
   能切档位的模型会带一个**默认档位**（上游声明了就按声明，否则取 `high`），因此选择器里不再出现「Default」这一项。
+  档位里的 **Off 表示「不发送档位参数」**：两个接口都不接受这个字面量，所以插件不会把它发出去；
+  实际是否关闭思考由上游决定，插件不做保证。
 - **积分可见** —— 每条回复下方显示本次消耗，模型选择器旁常驻剩余积分。拿不到数字时不显示。
 - **模型显隐** —— 卡片「模型」标签里勾选哪些模型出现在选择器里，按登录账号分别保存。
 - **图片输入** —— 多数模型可直接粘贴或拖入图片；纯文字模型会明确说明。

package/README_en.md

@@ -54,6 +54,8 @@ models appear directly in the DSH model picker — no separate provider to confi
   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".
+  **Off means "send no level parameter"**: neither endpoint accepts that literal, so the plugin never puts it
+  on the wire — whether thinking is then actually disabled is up to the upstream, and the plugin makes no claim.
 - **Credit in view** — each reply shows what it consumed, and remaining credit sits beside the model picker.
   Nothing renders when a figure is unavailable.
 - **Model visibility** — tick which models appear in the picker on the card's "Models" tab, saved per

package/lib/bin.js

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-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-BpW2mSgI.js";
+import { C as variantFor, D as WorkBuddyUpstreamClient, S as WORKBUDDY_VARIANTS, X 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-6xWs7ak3.js";
 import { realpathSync } from "node:fs";
 import { fileURLToPath } from "node:url";
 //#region src/cli/bin.ts

package/lib/{heartbeat-BpW2mSgI.js → heartbeat-6xWs7ak3.js}

@@ -366,13 +366,15 @@ async function resolveGlobalIdentity(options) {
 const UPSTREAM_CODE_KINDS = {
 	"12153": "session_dead",
 	"11128": "client",
-	"11133": "client"
+	"11133": "client",
+	"11140": "client"
 };
 /** 业务码 → 失败类别：信封 code 非 0 时的第一落点。 */
 const ENVELOPE_CODE_KINDS = {
 	12153: "session_dead",
 	11128: "client",
-	11133: "client"
+	11133: "client",
+	11140: "client"
 };
 /**
 * 文案兜底标记。**只在既无机器码也无业务码可依时使用**，且命中后必须记日志：
@@ -396,8 +398,43 @@ const TEXT_MARKERS = [
 	["offline user session not found", "session_dead"],
 	["12153", "session_dead"],
 	["11128", "client"],
-	["11133", "client"]
+	["11133", "client"],
+	["11140", "client"]
 ];
+/**
+* 上游自己的、面向用户的文案：`displayMsg` 优先，其次是 `msg`。
+*
+* 上游把「真正该给人看的那句话」放在 `displayMsg` 里（分别给出 `zh` / `zh-hant` /
+* `en` 三种拼写），而 `msg` 常常是一句机器可读的英文短语（`request illegal`）。
+* 把 `displayMsg` 丢掉的代价不是"少一句说明"：`msg` 本身看不出是封号、限流还是
+* 参数错，使用者只能看到一句无从下手的英文。
+*
+* 读取顺序固定在 `zh` → `zh-hant` → `en`：国内网关的 zh 文案是原始表述，en 是
+* 它的译文；先中文，只有上游没给中文时才退回英文。
+*
+* @param body - 响应体原文。
+* @returns 干净的、可直接展示的一行文案；读不出来返回 undefined。
+*/
+function upstreamDisplayMessage(body) {
+	const parsed = parseJson(body);
+	if (!isRecord(parsed)) return void 0;
+	const display = parsed["displayMsg"];
+	if (isRecord(display)) for (const key of [
+		"zh",
+		"zh-hant",
+		"en"
+	]) {
+		const value = display[key];
+		if (typeof value === "string" && value.trim() !== "") return value.trim();
+	}
+	const msg = parsed["msg"];
+	if (typeof msg === "string" && msg.trim() !== "") return msg.trim();
+	const extError = parsed["extError"];
+	if (isRecord(extError)) {
+		const message = extError["message"];
+		if (typeof message === "string" && message.trim() !== "") return message.trim();
+	}
+}
 /** 上游错误体：只取结构化字段，其余一概不看。 */
 const ErrorBody = z.object({
 	extError: z.object({
@@ -494,6 +531,10 @@ function parseJson(body) {
 		return;
 	}
 }
+/** 是否是一个可按键读取的对象（数组与 null 都不算）。 */
+function isRecord(value) {
+	return typeof value === "object" && value !== null && !Array.isArray(value);
+}
 //#endregion
 //#region src/probe/probe.ts
 /**
@@ -538,15 +579,31 @@ function randomSentinel() {
 	return `probe_sentinel_${randomBytes(12).toString("hex")}`;
 }
 /**
-* The upstream's "this effort value is not supported" code, measured
-* 2026-09-11 (plan §4.2). It is *not* treated as a permanent protocol promise:
-* anything unrecognized degrades to `unknown` rather than to a capability
-* conclusion.
+* The upstream's "this effort value is not supported" code.
+*
+* Measured 2026-09-11 (plan §4.2) as `invalid_reasoning_effort`. It is *not* a
+* permanent protocol promise: the upstream has since respelled it to the
+* generic `invalid_parameter_value` on both endpoints, which is why that
+* spelling is recognized too. Anything unrecognized still degrades to
+* `unknown` rather than to a capability conclusion.
 */
 const INVALID_EFFORT_CODE = "invalid_reasoning_effort";
+/**
+* Generic rejection code the upstream now uses for every bad field.
+*
+* Because it names no field, a body carrying it is only attributed to the
+* effort when `extError.param` points at the effort; otherwise a rejected
+* `max_tokens` would be misread as "this level is unsupported" and shrink the
+* reported capability set.
+*/
+const GENERIC_INVALID_CODE = "invalid_parameter_value";
 /** Whether an attempt is an attributable rejection of the effort value. */
 function isEffortRejection(attempt) {
-	return attempt.status === 400 && attempt.errorCode === INVALID_EFFORT_CODE;
+	if (attempt.status !== 400) return false;
+	const code = attempt.errorCode;
+	if (code === INVALID_EFFORT_CODE) return true;
+	if (code !== GENERIC_INVALID_CODE) return false;
+	return (attempt.param ?? "").toLowerCase().includes("effort");
 }
 /** Whether an attempt shows the upstream accepted the request and streamed. */
 function isAcceptance(attempt) {
@@ -828,13 +885,22 @@ function billingHeaders(credential) {
 * Normalize an OpenAI chat-completions body for the WorkBuddy upstream:
 * force `stream: true` (the upstream rejects non-streaming), flatten
 * `tool_choice` (the upstream's field is a string; object forms return 400),
-* and rewrite `developer` messages as `system`.
+* rewrite `developer` messages as `system`, neutralize the channel signature
+* (see {@link neutralizeChannelSignature}), and drop the adapter's own `off`
+* effort spelling (see {@link dropUnsupportedEffort}).
 *
 * The `developer` rewrite is load-bearing: pi-ai emits the system prompt as
 * `role: "developer"` (the OpenAI convention it adopted), but the WorkBuddy
 * upstream rejects that role with HTTP 400 code 11128 ("Illegal API
 * invocation from an unapproved channel"). Rewriting to `system` is the
 * compatible spelling the upstream accepts.
+*
+* Every transformation here is region-agnostic on purpose. The two endpoints
+* differ in what they *add* (the international one also needs a leading system
+* prompt — see {@link prepareInternationalChatBody}), not in what they reject:
+* both refuse the picker's `off` spelling, which is why that strip lives here
+* rather than in the international layer (issue #13 reversed the earlier
+* international-only scope decision, which rested on CN accepting it).
 */
 function prepareChatBody(source) {
 	let body;
@@ -847,9 +913,87 @@ function prepareChatBody(source) {
 	const obj = body;
 	obj["stream"] = true;
 	normalizeDeveloperRole(obj);
+	neutralizeChannelSignature(obj);
 	normalizeToolChoice(obj);
+	dropUnsupportedEffort(obj);
 	return JSON.stringify(obj);
 }
+/**
+* Strip the product-identity phrase the CN gateway reads as an unofficial
+* client signature.
+*
+* Measured 2026-10-21 on `copilot.tencent.com/v2/chat/completions`: a request
+* whose **system/developer** message carries the phrase `DeepSeek Harness`
+* answers `400` / `11128` "Illegal API invocation from an unapproved channel",
+* while the same account, headers and body with the phrase rewritten answers
+* 200. DSH injects exactly that phrase as the head of its system prompt
+* ("You are an AI agent powered by DeepSeek Harness."), so every request the
+* harness sends is affected; the official desktop app never sends it.
+*
+* Two rewrites, in this order, because they solve different halves of it:
+*
+* 1. **The opener**, when a message starts with it, becomes a plain
+*    "You are an AI agent." — a readable sentence that survives upstream
+*    normalization (unlike an invisible character, which a tokenizer or a
+*    normalizer may simply drop, and which the same measurement showed the
+*    gateway still rejects once an account is restricted).
+* 2. **Any other occurrence** gets a zero-width space between the two words:
+*    lossless, the model reads the same thing, and the substring match no
+*    longer fires.
+*
+* **Path contexts are never rewritten** (`…\DeepSeek Harness\…`,
+* `…/DeepSeek Harness/…`): a real directory name carries this phrase, and a
+* zero-width space inside it would turn every tool call that quotes the path
+* into a silently wrong path. Both rewrites anchor on the surrounding slashes
+* for that reason.
+*
+* Only `system` / `developer` messages are touched: the same measurement shows
+* user messages are not inspected, and rewriting user content would corrupt
+* data the plugin has no business editing. Idempotent — a second pass finds
+* neither the opener nor a bare phrase.
+*/
+function neutralizeChannelSignature(obj) {
+	const messages = obj["messages"];
+	if (!Array.isArray(messages)) return;
+	for (const message of messages) {
+		if (!isObject(message)) continue;
+		const role = message["role"];
+		if (role !== "system" && role !== "developer") continue;
+		const content = message["content"];
+		if (typeof content === "string") {
+			message["content"] = neutralizeSignatureText(content);
+			continue;
+		}
+		if (!Array.isArray(content)) continue;
+		for (const part of content) {
+			if (!isObject(part) || part["type"] !== "text") continue;
+			const text = part["text"];
+			if (typeof text === "string") part["text"] = neutralizeSignatureText(text);
+		}
+	}
+}
+/** Apply the two signature rewrites to one string; see {@link neutralizeChannelSignature}. */
+function neutralizeSignatureText(text) {
+	return text.replace(CHANNEL_OPENER, "$1You are an AI agent.").replace(CHANNEL_SIGNATURE_PHRASE, `DeepSeek${ZERO_WIDTH_SPACE}$1Harness`);
+}
+/**
+* The opener DSH puts at the head of every system prompt.
+*
+* Leading whitespace and a BOM are tolerated (group 1 carries them through to
+* the replacement, so the rewrite never touches anything but the sentence), and
+* every gap between the words is matched as whitespace so a respelling cannot
+* walk past it. Case-insensitive for the same reason.
+*/
+const CHANNEL_OPENER = /^([\s\uFEFF]*)You\s+are\s+an\s+AI\s+agent\s+powered\s+by\s+DeepSeek[\s\u00A0]+Harness\s*\./i;
+/**
+* The bare phrase, with slash guards on both sides so a real path survives.
+*
+* The capture keeps whatever whitespace the original used, so the rewritten
+* sentence reads identically.
+*/
+const CHANNEL_SIGNATURE_PHRASE = /(?<![\\/])DeepSeek([\s\u00A0]+)Harness(?![\\/])/gi;
+/** U+200B: invisible to a reader and to the model, breaks a substring match. */
+const ZERO_WIDTH_SPACE = "​";
 /** Rewrite `role: "developer"` messages to `role: "system"` (upstream rejects developer). */
 function normalizeDeveloperRole(obj) {
 	const messages = obj["messages"];
@@ -937,7 +1081,20 @@ var WorkBuddyUpstreamClient = class {
 		this.resolveAppVersion = options.resolveAppVersion ?? (() => resolveAppVersion());
 		this.resolveChatIdentity = options.resolveChatIdentity ?? ((region) => resolveChatIdentity(region));
 	}
-	/** POST the chat endpoint; a successful answer is the raw SSE response. */
+	/**
+	* POST the chat endpoint; a successful answer is the raw SSE response.
+	*
+	* This is the one place every chat request converges on (the loopback shim,
+	* the host LLM route, and any direct caller all end up here), so it is also
+	* where the body is normalized for the upstream — in *both* regions. The
+	* region only decides which extra requirement applies on top: the
+	* international gateway additionally demands a leading system message. It
+	* used to decide whether the body was normalized at all, which left the CN
+	* path sending the picker's `off` spelling verbatim (issue #13).
+	*
+	* Normalization is idempotent, so a caller that already prepared the body
+	* (the shim does) sees no second change.
+	*/
 	async chatStream(credential, bodyJson, signal) {
 		const region = regionOf(credential.domain);
 		let userAgent;
@@ -946,6 +1103,7 @@ var WorkBuddyUpstreamClient = class {
 		} catch {
 			userAgent = chatUserAgent(fallbackChatIdentity(region), region);
 		}
+		const body = region === "global" ? prepareInternationalChatBody(bodyJson) : prepareChatBody(bodyJson);
 		let response;
 		try {
 			response = await fetch(`${chatBase(credential)}/v2/chat/completions`, {
@@ -954,7 +1112,7 @@ var WorkBuddyUpstreamClient = class {
 					...chatHeaders(credential, userAgent),
 					Authorization: `Bearer ${credential.accessToken}`
 				},
-				body: region === "global" ? prepareInternationalChatBody(bodyJson) : bodyJson,
+				body,
 				...signal === void 0 ? {} : { signal }
 			});
 		} catch (error) {
@@ -1315,7 +1473,14 @@ var WorkBuddyUpstreamClient = class {
 		};
 	}
 };
-/** Pull `extError.code` out of an upstream error body, if it is shaped that way. */
+/**
+* Pull the structured failure fields out of an upstream error body.
+*
+* `extError.param` matters as much as the code: the upstream reuses one generic
+* code (`invalid_parameter_value`) for every rejected field, so the parameter
+* name is the only thing that attributes the rejection to `reasoning.effort`
+* rather than to `max_tokens` or anything else.
+*/
 function errorCodeOf(text) {
 	try {
 		const parsed = JSON.parse(text);
@@ -1323,7 +1488,12 @@ function errorCodeOf(text) {
 			const extError = parsed["extError"];
 			if (typeof extError === "object" && extError !== null && !Array.isArray(extError)) {
 				const code = extError["code"];
-				if (typeof code === "string") return {
+				const param = extError["param"];
+				if (typeof code === "string") return typeof param === "string" ? {
+					errorCode: code,
+					detail: code,
+					param
+				} : {
 					errorCode: code,
 					detail: code
 				};
@@ -1498,6 +1668,11 @@ function modelWithCurrentPromotion(model, now = Date.now()) {
 * merged: existing messages keep their order and wording. A body that is not a
 * JSON object is returned unchanged, exactly as {@link prepareChatBody} does,
 * so this is safe to run over an already-prepared-or-not body.
+*
+* This layer now carries *only* that requirement. The `reasoning_effort` strip
+* used to live here, scoped to this region; issue #13 showed CN rejects the
+* same spelling, so it moved into the shared {@link prepareChatBody} and this
+* function no longer touches the effort field at all.
 */
 function prepareInternationalChatBody(source) {
 	const prepared = prepareChatBody(source);
@@ -1508,7 +1683,6 @@ function prepareInternationalChatBody(source) {
 		return prepared;
 	}
 	if (!isObject(body)) return prepared;
-	dropUnsupportedEffort(body);
 	const messages = body["messages"];
 	if (!Array.isArray(messages)) return JSON.stringify(body);
 	const first = messages[0];
@@ -1520,25 +1694,35 @@ function prepareInternationalChatBody(source) {
 	return JSON.stringify(body);
 }
 /**
-* Remove the adapter's own `off` effort spelling from the **international** wire.
-*
-* `thinkingLevelMap.off` is pinned to the literal `'off'` for models that
-* declare `canDisableThinking`, so that the level stays selectable. pi-ai
-* sends that value for any request carrying no explicit level, and the
-* international endpoint rejects it on the GPT family with HTTP 400 `11133` /
-* `extError.param === 'reasoning.effort'` (issue #49). Omission is the only
-* form measured good on every such model; a literal `'none'` is *not* a safe
-* substitute — accepted by the GPT-5.6 family and GLM, rejected by
-* `gpt-6-astra`.
-*
-* Consequences, stated honestly: the international picker still offers Off,
-* but selecting it now means "the field is omitted" — the model's actual
-* behaviour is decided upstream and is *not* guaranteed to disable thinking
-* or to match the catalog's `defaultEffort`. Declared spellings
-* (`low`/`medium`/`high`/`xhigh`/`max`) and an explicit `none` pass through
-* untouched. The CN variant is deliberately unaffected: its endpoint has
-* accepted this spelling in every measurement so far, and keeping its wire
-* unchanged is a scope decision, not a claim about that endpoint's future.
+* Remove the adapter's own `off` effort spelling from the wire, in both regions.
+*
+* `thinkingLevelMap.off` is pinned to the literal `'off'` so the level stays
+* selectable in the picker — pi-ai exposes a level only when its entry is a
+* string — but that same entry is also the value pi-ai puts on the wire, both
+* for an explicit Off selection and for *every* request that carries no level
+* at all. `'off'` is a picker name, not an upstream spelling, and both
+* endpoints reject it:
+*
+* - international GPT family: HTTP 400 `11133` / `extError.param ===
+*   'reasoning.effort'` (issue #49);
+* - CN: the same 400 `11133` on every `canDisableThinking` model — measured
+*   on `deepseek-v4.1-flash`, where the author also confirmed `'disabled'`
+*   is rejected and `'none'` answers 200 (issue #13). This is what made the
+*   earlier international-only scope decision obsolete.
+*
+* Omission is the only form measured good on every affected model, so it is
+* the only form this function can produce; a literal `'none'` is *not* a safe
+* substitute (accepted by the GPT-5.6 family and GLM, rejected by
+* `gpt-6-astra`, and silently ignored by `kimi-k2.8-preview`). Declared
+* spellings (`low`/`medium`/`high`/`xhigh`/`max`) and an explicit `none` pass
+* through untouched — the adapter does not decide a user's `none` for them.
+*
+* Consequences, stated honestly: the picker still offers Off in both regions,
+* but selecting it means "the field is omitted". The model's actual behaviour
+* is then decided upstream — *not* guaranteed to disable thinking and not
+* guaranteed to match the catalog's `defaultEffort`. The plugin used to claim
+* more than that on CN, where `'off'` was merely accepted (accepted never
+* meant effective); #13 is why the claim is withdrawn rather than reworded.
 */
 function dropUnsupportedEffort(obj) {
 	if (obj["reasoning_effort"] === "off") delete obj["reasoning_effort"];
@@ -3688,7 +3872,7 @@ var WorkBuddyCatalog = class {
 };
 //#endregion
 //#region src/version.ts
-const WORKBUDDY_BRIDGE_VERSION = "0.5.0";
+const WORKBUDDY_BRIDGE_VERSION = "0.5.2";
 //#endregion
 //#region src/web/heartbeat.ts
 /**
@@ -3859,4 +4043,4 @@ function isHeartbeatProcessAlive(heartbeat) {
 	return startAtMs <= heartbeat.registeredAt;
 }
 //#endregion
-export { parseModelCatalog as A, chatUserAgent as B, variantFor as C, WorkBuddyUpstreamClient as D, WORKBUDDY_STATUS_PATH as E, probeModel as F, WORKBUDDY_APP_VERSION_FILENAME as G, readCliVersion as H, randomSentinel as I, readBundleVersion as J, appUserAgent as K, classifyUpstreamError as L, prepareInternationalChatBody as M, regionOf as N, modelWithCurrentPromotion as O, PROBE_EFFORT_CANDIDATES as P, CN_APP_VERSION_FILENAME as R, WORKBUDDY_VARIANTS as S, WORKBUDDY_PROBE_PATH as T, resolveChatIdentity as U, fallbackChatIdentity as V, validCliVersion as W, validAppVersion as X, resolveAppVersion as Y, desktopAuthCandidatesFor as _, readHostHeartbeat as a, AI_VARIANT as b, WORKBUDDY_BRIDGE_VERSION as c, WorkBuddyCatalog as d, WORKBUDDY_AUTH_FILENAME as f, defaultDesktopAuthPath as g, defaultDesktopAuthCandidates as h, processStartTimeMs as i, prepareChatBody as j, normalizeCredits as k, FALLBACK_WORKBUDDY_AI_MODELS as l, WorkBuddyCredentialStore as m, clearHostHeartbeat as n, workbuddyHostHeartbeatPath as o, WORKBUDDY_AUTH_FILE_ENV as p, installedAppVersion as q, isHeartbeatProcessAlive as r, writeHostHeartbeat as s, WORKBUDDY_HOST_HEARTBEAT_FILENAME as t, FALLBACK_WORKBUDDY_MODELS as u, parseWorkBuddyAuth as v, WORKBUDDY_CREDIT_PATH as w, CN_VARIANT as x, workbuddyOwnAuthPath as y, FALLBACK_CN_APP_VERSION as z };
+export { parseModelCatalog as A, FALLBACK_CN_APP_VERSION as B, variantFor as C, WorkBuddyUpstreamClient as D, WORKBUDDY_STATUS_PATH as E, probeModel as F, validCliVersion as G, fallbackChatIdentity as H, randomSentinel as I, installedAppVersion as J, WORKBUDDY_APP_VERSION_FILENAME as K, classifyUpstreamError as L, prepareInternationalChatBody as M, regionOf as N, modelWithCurrentPromotion as O, PROBE_EFFORT_CANDIDATES as P, upstreamDisplayMessage as R, WORKBUDDY_VARIANTS as S, WORKBUDDY_PROBE_PATH as T, readCliVersion as U, chatUserAgent as V, resolveChatIdentity as W, resolveAppVersion as X, readBundleVersion as Y, validAppVersion as Z, desktopAuthCandidatesFor as _, readHostHeartbeat as a, AI_VARIANT as b, WORKBUDDY_BRIDGE_VERSION as c, WorkBuddyCatalog as d, WORKBUDDY_AUTH_FILENAME as f, defaultDesktopAuthPath as g, defaultDesktopAuthCandidates as h, processStartTimeMs as i, prepareChatBody as j, normalizeCredits as k, FALLBACK_WORKBUDDY_AI_MODELS as l, WorkBuddyCredentialStore as m, clearHostHeartbeat as n, workbuddyHostHeartbeatPath as o, WORKBUDDY_AUTH_FILE_ENV as p, appUserAgent as q, isHeartbeatProcessAlive as r, writeHostHeartbeat as s, WORKBUDDY_HOST_HEARTBEAT_FILENAME as t, FALLBACK_WORKBUDDY_MODELS as u, parseWorkBuddyAuth as v, WORKBUDDY_CREDIT_PATH as w, CN_VARIANT as x, workbuddyOwnAuthPath as y, CN_APP_VERSION_FILENAME as z };

package/lib/index.d.ts

@@ -424,6 +424,13 @@ interface ProbeAttempt {
   streamed: boolean;
   /** `extError.code` from a JSON error body, when present. */
   errorCode?: string;
+  /**
+   * `extError.param` from the same body.
+   *
+   * Load-bearing since the upstream started reusing one generic rejection code
+   * for every field: it is what attributes the rejection to the effort value.
+   */
+  param?: string;
   /** Free-form detail for logs; never shown as a capability claim. */
   detail?: string;
 }
@@ -613,13 +620,22 @@ declare function regionOf(domain: string): WorkBuddyRegion;
  * Normalize an OpenAI chat-completions body for the WorkBuddy upstream:
  * force `stream: true` (the upstream rejects non-streaming), flatten
  * `tool_choice` (the upstream's field is a string; object forms return 400),
- * and rewrite `developer` messages as `system`.
+ * rewrite `developer` messages as `system`, neutralize the channel signature
+ * (see {@link neutralizeChannelSignature}), and drop the adapter's own `off`
+ * effort spelling (see {@link dropUnsupportedEffort}).
  *
  * The `developer` rewrite is load-bearing: pi-ai emits the system prompt as
  * `role: "developer"` (the OpenAI convention it adopted), but the WorkBuddy
  * upstream rejects that role with HTTP 400 code 11128 ("Illegal API
  * invocation from an unapproved channel"). Rewriting to `system` is the
  * compatible spelling the upstream accepts.
+ *
+ * Every transformation here is region-agnostic on purpose. The two endpoints
+ * differ in what they *add* (the international one also needs a leading system
+ * prompt — see {@link prepareInternationalChatBody}), not in what they reject:
+ * both refuse the picker's `off` spelling, which is why that strip lives here
+ * rather than in the international layer (issue #13 reversed the earlier
+ * international-only scope decision, which rested on CN accepting it).
  */
 declare function prepareChatBody(source: string): string;
 /** Provenance of one successful catalog fetch, surfaced by the status card. */
@@ -660,7 +676,20 @@ declare class WorkBuddyUpstreamClient {
   /** Provenance of the most recent successful catalog fetch, for the card. */
   lastCatalog: WorkBuddyCatalogFetch | undefined;
   constructor(options?: WorkBuddyUpstreamClientOptions);
-  /** POST the chat endpoint; a successful answer is the raw SSE response. */
+  /**
+   * POST the chat endpoint; a successful answer is the raw SSE response.
+   *
+   * This is the one place every chat request converges on (the loopback shim,
+   * the host LLM route, and any direct caller all end up here), so it is also
+   * where the body is normalized for the upstream — in *both* regions. The
+   * region only decides which extra requirement applies on top: the
+   * international gateway additionally demands a leading system message. It
+   * used to decide whether the body was normalized at all, which left the CN
+   * path sending the picker's `off` spelling verbatim (issue #13).
+   *
+   * Normalization is idempotent, so a caller that already prepared the body
+   * (the shim does) sees no second change.
+   */
   chatStream(credential: WorkBuddyCredential, bodyJson: string, signal?: AbortSignal): Promise<WorkBuddyChatResult>;
   /** POST the token-refresh endpoint; the caller merges the outcome. */
   refreshToken(credential: WorkBuddyCredential): Promise<WorkBuddyRefreshOutcome>;
@@ -833,6 +862,11 @@ declare function modelWithCurrentPromotion(model: WorkBuddyUpstreamModel, now?:
  * merged: existing messages keep their order and wording. A body that is not a
  * JSON object is returned unchanged, exactly as {@link prepareChatBody} does,
  * so this is safe to run over an already-prepared-or-not body.
+ *
+ * This layer now carries *only* that requirement. The `reasoning_effort` strip
+ * used to live here, scoped to this region; issue #13 showed CN rejects the
+ * same spelling, so it moved into the shared {@link prepareChatBody} and this
+ * function no longer touches the effort field at all.
  */
 declare function prepareInternationalChatBody(source: string): string;
 //#endregion

package/lib/index.js

@@ -1,4 +1,4 @@
-import { A as parseModelCatalog, B as chatUserAgent, C as variantFor, D as WorkBuddyUpstreamClient, F as probeModel, G as WORKBUDDY_APP_VERSION_FILENAME, H as readCliVersion, I as randomSentinel, J as readBundleVersion, K as appUserAgent, L as classifyUpstreamError, M as prepareInternationalChatBody, N as regionOf, O as modelWithCurrentPromotion, P as PROBE_EFFORT_CANDIDATES, R as CN_APP_VERSION_FILENAME, S as WORKBUDDY_VARIANTS, U as resolveChatIdentity, V as fallbackChatIdentity, W as validCliVersion, X as validAppVersion, Y as resolveAppVersion, _ as desktopAuthCandidatesFor, a as readHostHeartbeat, b as AI_VARIANT, c as WORKBUDDY_BRIDGE_VERSION, d as WorkBuddyCatalog, f as WORKBUDDY_AUTH_FILENAME, g as defaultDesktopAuthPath, h as defaultDesktopAuthCandidates, i as processStartTimeMs, j as prepareChatBody, k as normalizeCredits, l as FALLBACK_WORKBUDDY_AI_MODELS, m as WorkBuddyCredentialStore, n as clearHostHeartbeat, o as workbuddyHostHeartbeatPath, p as WORKBUDDY_AUTH_FILE_ENV, q as installedAppVersion, r as isHeartbeatProcessAlive, s as writeHostHeartbeat, t as WORKBUDDY_HOST_HEARTBEAT_FILENAME, u as FALLBACK_WORKBUDDY_MODELS, v as parseWorkBuddyAuth, w as WORKBUDDY_CREDIT_PATH, x as CN_VARIANT, y as workbuddyOwnAuthPath, z as FALLBACK_CN_APP_VERSION } from "./heartbeat-BpW2mSgI.js";
+import { A as parseModelCatalog, B as FALLBACK_CN_APP_VERSION, C as variantFor, D as WorkBuddyUpstreamClient, F as probeModel, G as validCliVersion, H as fallbackChatIdentity, I as randomSentinel, J as installedAppVersion, K as WORKBUDDY_APP_VERSION_FILENAME, L as classifyUpstreamError, M as prepareInternationalChatBody, N as regionOf, O as modelWithCurrentPromotion, P as PROBE_EFFORT_CANDIDATES, R as upstreamDisplayMessage, S as WORKBUDDY_VARIANTS, U as readCliVersion, V as chatUserAgent, W as resolveChatIdentity, X as resolveAppVersion, Y as readBundleVersion, Z as validAppVersion, _ as desktopAuthCandidatesFor, a as readHostHeartbeat, b as AI_VARIANT, c as WORKBUDDY_BRIDGE_VERSION, d as WorkBuddyCatalog, f as WORKBUDDY_AUTH_FILENAME, g as defaultDesktopAuthPath, h as defaultDesktopAuthCandidates, i as processStartTimeMs, j as prepareChatBody, k as normalizeCredits, l as FALLBACK_WORKBUDDY_AI_MODELS, m as WorkBuddyCredentialStore, n as clearHostHeartbeat, o as workbuddyHostHeartbeatPath, p as WORKBUDDY_AUTH_FILE_ENV, q as appUserAgent, r as isHeartbeatProcessAlive, s as writeHostHeartbeat, t as WORKBUDDY_HOST_HEARTBEAT_FILENAME, u as FALLBACK_WORKBUDDY_MODELS, v as parseWorkBuddyAuth, w as WORKBUDDY_CREDIT_PATH, x as CN_VARIANT, y as workbuddyOwnAuthPath, z as CN_APP_VERSION_FILENAME } from "./heartbeat-6xWs7ak3.js";
 import z from "@deepseek-ai/schemastery";
 import { dirname, join, resolve } from "node:path";
 import { resolveDshHome } from "@deepseek-ai/dsh-home-paths";
@@ -446,6 +446,13 @@ function withCatalogDisplay(name, info) {
 * The offered set is described internally as "verified accepted", never as
 * "verified effective": acceptance proves the upstream did not reject the
 * spelling, not that it changes what the model does.
+*
+* `off` is a picker name, not a wire spelling. It stays pinned to the literal
+* `'off'` (a `null` here would remove the level from the picker entirely), and
+* the shared preparation in `src/protocol/client.ts` strips that exact value
+* before the request leaves the plugin — in both regions, because both
+* endpoints reject it (issues #49 and #13). Selecting Off therefore means "send
+* no `reasoning_effort`", and what the model then does is upstream's call.
 */
 function reasoningFields(info, observed) {
 	const resolved = resolveEfforts(info, observed);
@@ -798,6 +805,25 @@ function writeOpenAIError(res, status, kind, message) {
 		code: kind
 	} });
 }
+/**
+* The one-line reason a failed upstream request is reported with.
+*
+* The host does not read our HTTP status to classify a failure: `dsh-llm-pi-ai`
+* matches the **message text** (`if (/\b(?:401|403)\b/.test(message)) return
+* "AUTH"`), and the chat UI then replaces whatever we wrote with
+* "API key is invalid". So a status may only appear here when the failure
+* really is an authentication one; every other class keeps its digits out, or
+* a restricted account or a rejected prompt reaches the user as a bad key.
+*
+* The upstream's own `displayMsg` wins over the raw body: it is the sentence
+* written for a human ("账号存在异常行为，已被限制使用"), while the body is a JSON
+* document whose `msg` is often a machine phrase such as `request illegal`.
+*/
+function failureMessage(result) {
+	const reason = upstreamDisplayMessage(result.message) ?? result.message.slice(0, 400);
+	const head = `workbuddy upstream ${result.kind}`;
+	return result.kind === "session_dead" ? `${head} (http ${result.status}): ${reason}` : `${head}: ${reason}`;
+}
 /** Read a request body with a size cap; over-limit bodies fail the request. */
 function readBody$1(req) {
 	return new Promise((resolve, reject) => {
@@ -909,7 +935,7 @@ function createWorkBuddyShim(options) {
 		req.on("close", () => controller.abort());
 		const result = await client.chatStream(credential, prepared, controller.signal);
 		if (!result.ok) {
-			writeOpenAIError(res, KIND_STATUS[result.kind], result.kind, `workbuddy upstream ${result.kind} (http ${result.status}): ${result.message.slice(0, 400)}`);
+			writeOpenAIError(res, KIND_STATUS[result.kind], result.kind, failureMessage(result));
 			return;
 		}
 		res.writeHead(200, {

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-workbuddy-bridge",
   "displayName": "DSH WorkBuddy Bridge",
   "description": "将 WorkBuddy 桌面 App 包含的模型自动接入 DeepSeek Harness — bring WorkBuddy desktop app models into DeepSeek Harness with zero configuration.",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "author": "zlZayn",
   "keywords": [
     "dsh",
@@ -97,7 +97,7 @@
     "react-dom": "^18.2.0"
   },
   "devDependencies": {
-    "@deepseek-ai/cordis": "4.0.4",
+    "@deepseek-ai/cordis": "^4.0.4",
     "@deepseek-ai/dsh-api-remotes": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
     "@deepseek-ai/dsh-atomic-write": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
     "@deepseek-ai/dsh-attachment": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
@@ -119,7 +119,7 @@
     "@deepseek-ai/dsh-settings": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
     "@deepseek-ai/dsh-util-code-language": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
     "@deepseek-ai/dsh-util-workspace-path": "^0.1.7-rc.1 || ^0.2.0-rc.1 || ^0.2.1-rc.1",
-    "@deepseek-ai/schemastery": "3.18.5",
+    "@deepseek-ai/schemastery": "^3.18.4",
     "@earendil-works/pi-ai": "^1.1.0",
     "@eslint/js": "^10.0.1",
     "@shikijs/langs": "^4.4.3",
@@ -150,7 +150,7 @@
     "micromark-util-symbol": "^2.0.1",
     "prettier": "^3.9.9",
     "react": "^18.2.0",
-    "react-dom": "^18.3.1",
+    "react-dom": "^18.2.0",
     "react-test-renderer": "18.3.1",
     "shiki": "^4.4.3",
     "simple-icons": "^16.32.0",