dsh-any-deepseek 0.0.14 → 0.0.15

package/lib/channels.d.ts

@@ -102,7 +102,10 @@ export interface ResolvedChannel {
      * How this endpoint's remaining balance can be read, when it can be.
      *
      * Absent means "no balance API" — a real state, not a missing value. See `presets.ts` for the
-     * three verified shapes and why OpenCode Go deliberately has none.
+     * four verified shapes. Note the two different kinds of "no number": OpenCode Go reports usage
+     * WINDOWS rather than money (it does have a surface), while Open Design publishes no surface at
+     * all (measured: seven candidates, all 404). The panel distinguishes them, and checks liveness
+     * for the latter instead of inventing an amount.
      */
     balance?: BalanceProbe;
     /** Facts the user should see because a default was applied rather than declared. */

package/lib/client.js

@@ -27,12 +27,20 @@ window.__ModuleLoader__.load({
 		*
 		* Deliberately total: every status produces words, never an empty string. A blank cell beside a
 		* working channel is indistinguishable from "zero balance" — the one thing this must never imply.
+		*
+		* 🔴 **`alive` is worded as 「余额未尽」, never as a number.** The check behind it is one minimal
+		* live request, which proves the endpoint serves and the account is not blocked for lack of
+		* credit. It does not measure an amount, so printing one — or printing `0.00` — would invent the
+		* very figure this status exists to avoid inventing (owner directive 2026-10-23: 「不支持查余额的，
+		* 改成直接测通，通则说明余额还是有的，没用完」).
 		* @param row - one row from `/balance`.
 		* @returns a short human label.
 		*/
 		function formatBalance(row) {
+			if (row.status === "alive") return `余额未尽（无余额接口，实测可用：${row.responded === void 0 ? `${Math.round(row.ms)}ms` : `${row.responded} · ${Math.round(row.ms)}ms`}）`;
 			if (row.status !== "ok") {
 				if (row.status === "no-key") return "未配置密钥";
+				if (row.code === "QUOTA") return "余额不足（实测被拒）";
 				if (row.status === "unavailable") return row.code === "HTTP_404" ? "不支持查询" : "读取失败";
 				return "不支持查询";
 			}
@@ -508,6 +516,7 @@ window.__ModuleLoader__.load({
 									type: "button",
 									className: "ad-link",
 									disabled: balancesLoading || rows.length === 0,
+									title: "无余额接口的渠道会用一次最小真实请求测通（消耗一两个 token）",
 									onClick: () => {
 										refreshBalances();
 									},

package/lib/http.d.ts

@@ -121,10 +121,11 @@ export declare function reportedName(text: string): string;
 /**
  * Fetch one channel's remaining balance from whatever surface it declares.
  *
- * 🔴 **Absence is a normal answer here, and is reported as such.** Three outcomes are kept apart
+ * 🔴 **Absence is a normal answer here, and is reported as such.** Outcomes are kept apart
  * because they mean different things to the user:
- *  · `unsupported` — the preset declares no balance shape (OpenCode Go: the provider has an open
- *    request for one, because today the only key-authenticated signal is an error at $0).
+ *  · `unsupported` — the preset declares no balance shape. This is no longer the end of the story
+ *    for the panel: `/{@link balanceRow}` turns it into a liveness verdict, because "the endpoint
+ *    will not tell me the amount" and "the account is fine" are different facts and both matter.
  *  · `unavailable` — a shape was declared but the endpoint did not answer as expected (404,
  *    non-JSON, unexpected body). The relay may simply not implement it.
  *  · `ok` — a reading, which itself may carry only a note (e.g. "unlimited, used $3.20").
@@ -147,6 +148,68 @@ export declare function fetchBalance(channel: ResolvedChannel, key: string, sign
     detail: string;
     code?: string;
 }>;
+/**
+ * One row of `/balance`, as it travels to the panel.
+ *
+ * `alive` is the fourth outcome and exists because of an owner directive (2026-10-23):
+ * 「对于不支持查余额的，改成直接测通，通则说明余额还是有的，没用完，显示出来（消耗一两个token）」.
+ *
+ * 🔴 **`alive` is NOT a balance number and must never be rendered as one.** It is the result of a
+ * minimal real inference request, and it proves exactly three things: the key works, the endpoint
+ * serves, and the account is not blocked for lack of credit (a $0 account answers 402/quota, it
+ * does not answer 200). It says nothing about HOW MUCH is left. The panel wording therefore says
+ * 「余额未尽」 — "not exhausted" — which is the strongest true claim available here, and stops
+ * short of the number a reader might otherwise assume.
+ */
+export type BalanceRowWire = {
+    id: string;
+    label: string;
+    status: 'ok';
+    reading: BalanceReading;
+} | {
+    id: string;
+    label: string;
+    status: 'unsupported';
+    detail: string;
+} | {
+    id: string;
+    label: string;
+    status: 'unavailable';
+    detail: string;
+    code?: string;
+} | {
+    id: string;
+    label: string;
+    status: 'alive';
+    /** How long the liveness request took. */
+    ms: number;
+    /** What the relay called its model — a serving endpoint answers with a name. */
+    responded?: string;
+    detail: string;
+};
+/**
+ * The stated reason an `alive` row carries no number.
+ *
+ * Kept as a constant so the server and every reader of the payload say the same thing: this row
+ * is about liveness, not about a balance.
+ */
+export declare const ALIVE_DETAIL: string;
+/**
+ * Build one `/balance` row, falling back to a liveness probe when there is no balance surface.
+ *
+ * 🔴 **The fallback spends tokens, so it is scoped as tightly as possible**: it runs ONLY when the
+ * balance surface is absent (`unsupported`), never for a channel whose balance API answered `ok`
+ * and never for one that exists but failed (`unavailable` — that is a "try again" state, and
+ * probing it would replace a transient error with a different-looking success).
+ *
+ * The cost is one prompt plus one output token on a completions channel (`max_tokens: 1` in
+ * {@link probeRequest}); the Responses cap is a ceiling, not a spend.
+ * @param channel - the resolved channel.
+ * @param key - its resolved credential (already resolved by the caller, so a probe and a real
+ *   request never read the key differently).
+ * @returns the row, always resolved — one dead relay must not blank the others.
+ */
+export declare function balanceRow(channel: ResolvedChannel, key: string): Promise<BalanceRowWire>;
 /**
  * Register the panel's routes.
  * @param ctx - plugin context (only used to bind the disposer when the host offers one).

package/lib/index.js

@@ -2235,10 +2235,11 @@ function reportedName(text) {
 /**
 * Fetch one channel's remaining balance from whatever surface it declares.
 *
-* 🔴 **Absence is a normal answer here, and is reported as such.** Three outcomes are kept apart
+* 🔴 **Absence is a normal answer here, and is reported as such.** Outcomes are kept apart
 * because they mean different things to the user:
-*  · `unsupported` — the preset declares no balance shape (OpenCode Go: the provider has an open
-*    request for one, because today the only key-authenticated signal is an error at $0).
+*  · `unsupported` — the preset declares no balance shape. This is no longer the end of the story
+*    for the panel: `/{@link balanceRow}` turns it into a liveness verdict, because "the endpoint
+*    will not tell me the amount" and "the account is fine" are different facts and both matter.
 *  · `unavailable` — a shape was declared but the endpoint did not answer as expected (404,
 *    non-JSON, unexpected body). The relay may simply not implement it.
 *  · `ok` — a reading, which itself may carry only a note (e.g. "unlimited, used $3.20").
@@ -2319,6 +2320,61 @@ async function fetchBalance(channel, key, signal) {
 		reading
 	};
 }
+/**
+* The stated reason an `alive` row carries no number.
+*
+* Kept as a constant so the server and every reader of the payload say the same thing: this row
+* is about liveness, not about a balance.
+*/
+const ALIVE_DETAIL = "this endpoint publishes no balance API; a minimal live request succeeded, so it is serving and its credit is not exhausted (no amount is readable)";
+/**
+* Build one `/balance` row, falling back to a liveness probe when there is no balance surface.
+*
+* 🔴 **The fallback spends tokens, so it is scoped as tightly as possible**: it runs ONLY when the
+* balance surface is absent (`unsupported`), never for a channel whose balance API answered `ok`
+* and never for one that exists but failed (`unavailable` — that is a "try again" state, and
+* probing it would replace a transient error with a different-looking success).
+*
+* The cost is one prompt plus one output token on a completions channel (`max_tokens: 1` in
+* {@link probeRequest}); the Responses cap is a ceiling, not a spend.
+* @param channel - the resolved channel.
+* @param key - its resolved credential (already resolved by the caller, so a probe and a real
+*   request never read the key differently).
+* @returns the row, always resolved — one dead relay must not blank the others.
+*/
+async function balanceRow(channel, key) {
+	const outcome = await fetchBalance(channel, key);
+	if (outcome.status !== "unsupported") return {
+		id: channel.id,
+		label: channel.label,
+		...outcome
+	};
+	const verdict = await probeChannel(channel, key, `probe:${channel.id}`);
+	if (!verdict.ok)
+ /**
+	* The liveness request failed, so nothing was learned about the account.
+	*
+	* It is reported as `unavailable` rather than as a verdict of its own because that is what it
+	* is: we tried to find out and did not. `code` is passed through untouched, which is what lets
+	* the panel tell the one FAILURE THAT IS ACTUALLY AN ANSWER (`QUOTA` — the account is out of
+	* credit) from the ones that are just errors.
+	*/
+	return {
+		id: channel.id,
+		label: channel.label,
+		status: "unavailable",
+		detail: `no balance API, and the liveness request failed: ${verdict.message ?? verdict.code ?? "unknown"}`,
+		...verdict.code === void 0 ? {} : { code: verdict.code }
+	};
+	return {
+		id: channel.id,
+		label: channel.label,
+		status: "alive",
+		ms: verdict.ms,
+		...verdict.responded === void 0 || verdict.responded === "" ? {} : { responded: verdict.responded },
+		detail: ALIVE_DETAIL
+	};
+}
 /** Map an HTTP status from a probe onto the same codes the runtime uses. */
 function probeCode(status, body) {
 	if (status === 401 || status === 403) return "AUTH";
@@ -2469,10 +2525,12 @@ function registerStatsRoutes(ctx, webServer, deps) {
 			/**
 			* Remaining balance per channel.
 			*
-			* GET because it reads and costs nothing at the provider (all three surfaces are plain
-			* account reads, not model calls). Every channel is attempted independently: one relay
-			* without a balance API, or one that is down, must not blank the others — the same rule the
-			* channel list follows for a broken entry.
+			* GET because it is a read, but 🔴 **it is no longer free**: a channel whose endpoint has no
+			* balance surface is now checked with one minimal live request (owner directive 2026-10-23),
+			* which costs a prompt plus one output token. The route stays GET because the panel's
+			* button is what triggers it — nothing here fires on render. Every channel is attempted
+			* independently: one relay without a balance API, or one that is down, must not blank the
+			* others — the same rule the channel list follows for a broken entry.
 			*/
 			kind: "exact",
 			path: `${ROUTE_PREFIX}/balance`,
@@ -2486,12 +2544,7 @@ function registerStatsRoutes(ctx, webServer, deps) {
 						status: "no-key",
 						detail: "no key configured"
 					};
-					const outcome = await fetchBalance(channel, key);
-					return {
-						id: channel.id,
-						label: channel.label,
-						...outcome
-					};
+					return balanceRow(channel, key);
 				})) });
 			}
 		}

package/lib/presets.d.ts

@@ -98,7 +98,9 @@ export interface ChannelPreset {
      *
      * Absent means "this endpoint has no balance API we know of" — a real and common state, not an
      * omission. The panel says so explicitly rather than leaving a blank cell that could be read
-     * as zero.
+     * as zero, and then checks the endpoint is ALIVE with one minimal live request (owner directive
+     * 2026-10-23): "no amount is readable" and "the credit is spent" are different facts, and a
+     * successful call proves the second is not true. See `http.ts`'s `balanceRow`.
      */
     balance?: BalanceProbe;
     /** One-line note for the panel, when the relay needs explaining. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-any-deepseek",
-  "version": "0.0.14",
+  "version": "0.0.15",
   "description": "One DeepSeek V4.1 Flash provider for DeepSeek Harness: paste a key per channel, switch channels manually, token usage booked per real upstream.",
   "license": "MIT",
   "repository": {