dsh-packycode-api 1.3.0 → 1.3.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 1.3.1
+
+- **The balance read no longer requests PackyCode's billing endpoints.** Every conversation balance refresh called `/v1/dashboard/billing/subscription` and `/v1/dashboard/billing/usage` and treated the answers as account-wide billing. PackyCode answers them per key: a live check on 2026-10-17 returned each key's own grant as `hard_limit_usd`, its own spend in cents as `total_usage` (`1387.9536` for $13.8795 used), and the placeholder `hard_limit_usd: 100000000` for an unlimited key. Nothing has displayed these figures since the account line was removed — its large negative remaining came from reading cents as dollars — so the requests only delayed each refresh. An API key cannot read the account's own balance at all; that sits behind the dashboard API, which takes a login session. An unlimited key therefore still shows only its own used amount.
+- The `balance` RPC no longer returns an `account` field. `createBalanceReader` drops its `includeAccount` option, and `parseBillingSubscription`, `parseBillingUsage` and `accountHostOrder` are no longer exported. A 402/403 on a key's balance read now says the gateway refused that read rather than naming the account. `scripts/live-check.mjs` prints the key's own used amount instead of the account line.
+- Validation, 2026-10-17: 393 offline tests (three account-only cases removed with the code, one added), both rebuilt bundles and the versioned tarball. Live, before the change: for three stored keys the billing endpoints echoed each key's own grant and its spend in cents, the unlimited key answered `hard_limit_usd: 100000000`, and `www.packyapi.ai/api/user/self` answered a scripted request with a Cloudflare 403. After it: the built reader made one `/api/usage/token/` request per stored key and no billing request, and read the unlimited key as `unlimitedQuota: true`. `scripts/live-check.mjs` passed: every HTTP model answered, and key rotation and the RPC projections were unchanged. No DSH restart.
+
 ## 1.3.0
 
 - **Claude runs directly inside the plugin.** Opus, Sonnet and Haiku now use the native Anthropic Messages HTTP route with DSH tools, attachments, permissions, plan mode and durable history. Claude session titles use Haiku over HTTP. No Claude Code installation, login or subprocess is required.

package/README.en.md

@@ -47,10 +47,10 @@ You need **DeepSeek Harness** and a **PackyCode (PackyAPI) API key**. For DSH se
 Open the desktop application's **Plugins** page, click **Add plugin**, and enter the package name **with a version** as the **package name or address**:
 
 ```text
-dsh-packycode-api@1.3.0
+dsh-packycode-api@1.3.1
 ```
 
-Choose the **official** install source, then click **Install**. `1.3.0` was the latest release when this was written; the [npm page](https://www.npmjs.com/package/dsh-packycode-api) shows the current one.
+Choose the **official** install source, then click **Install**. `1.3.1` was the latest release when this was written; the [npm page](https://www.npmjs.com/package/dsh-packycode-api) shows the current one.
 
 > **Always include the version.** With a bare `dsh-packycode-api`, the install prompt shows the newest version on npm, but DSH's bundled pnpm by default installs only versions published at least 24 hours ago, so you can end up several releases behind with no sign of it in the prompt. With an exact version, pnpm installs that version and adds it to the profile's `minimumReleaseAgeExclude` itself. Afterwards, check **Current version** under **Settings → PackyCode → Plugin version**.
 
@@ -71,7 +71,7 @@ Choose a model from the `PackyCode` group. All nine models use the plugin’s HT
 
 The **Plugins** page shows the installed state and version, and is also where you enable, disable, or uninstall.
 
-**For non-desktop profiles only:** `dsh plugin --profile <name> add dsh-packycode-api@1.3.0`. Do not use it for `desktop` — the CLI refuses it (`profile "desktop" is managed exclusively by the Electron application`).
+**For non-desktop profiles only:** `dsh plugin --profile <name> add dsh-packycode-api@1.3.1`. Do not use it for `desktop` — the CLI refuses it (`profile "desktop" is managed exclusively by the Electron application`).
 
 For a local checkout, keep the `link:` prefix: `dsh plugin --profile <name> add link:/path/to/dsh-packycode-api`. **Do not pass a bare path or `file:`** — that install copies the whole checkout, `node_modules` included, into the profile, where it then shadows the packages the DSH installation itself provides and the plugin looks uninstalled; see the FAQ. If you already installed that way, uninstall first and reinstall as above.
 
@@ -200,7 +200,7 @@ Only GPT Responses requests keep `prompt_cache_key`; other Responses models omit
 
 ## Update and uninstall
 
-**Update:** open **Settings → PackyCode** and, when a newer version is listed, click **Update plugin**. It installs that exact version into the owning profile with DSH's bundled pnpm and reads `package.json` back before reporting success. A local `link:` checkout does not get the button. Then quit and reopen the desktop application. A page refresh does not reload the Host. Reinstalling from the **Plugins** page works too, again with the version in the package name (for example `dsh-packycode-api@1.3.0`); without it you may get a version that is merely the newest one published at least 24 hours ago.
+**Update:** open **Settings → PackyCode** and, when a newer version is listed, click **Update plugin**. It installs that exact version into the owning profile with DSH's bundled pnpm and reads `package.json` back before reporting success. A local `link:` checkout does not get the button. Then quit and reopen the desktop application. A page refresh does not reload the Host. Reinstalling from the **Plugins** page works too, again with the version in the package name (for example `dsh-packycode-api@1.3.1`); without it you may get a version that is merely the newest one published at least 24 hours ago.
 
 **Coming back from a local-path install, uninstall first.** An update is a `pnpm add`: it rewrites the files inside the package directory and leaves a `node_modules` that an earlier local-path install left there. That older tree keeps shadowing the packages the DSH installation provides, so the plugin row fails to load with no visible reason. **Uninstall** runs `pnpm remove`, which deletes the package directory outright — only a reinstall after that is clean. `node scripts/install-check.mjs` reports whether a profile is in that state.
 
@@ -216,7 +216,7 @@ ls ~/.dsh/profiles/desktop/node_modules/dsh-packycode-api/node_modules
 
 Output means a leftover tree: a registry install ships no `node_modules`, so this one usually comes from an earlier local-path install (`file:`, or a bare path instead of `link:`). It sits inside the profile directory, and DSH resolves a plugin's imports from inside the profile first, so the plugin gets those old copies — for example `@deepseek-ai/schemastery` 3.18.2, which has no `Schema.volatile()`, so the module throws while it is imported. When an import fails the Loader creates no fiber for that row and no client bundle is composed either, so the model route, the RPC channel, and the settings panel all stay absent.
 
-Recovery: **uninstall** the plugin on the **Plugins** page, **install** it again with the version in the package name (for example `dsh-packycode-api@1.3.0`), then quit and reopen the desktop application. Uninstall runs `pnpm remove` and deletes the whole package directory; reinstalling or clicking **Update** only rewrites files and keeps the leftover tree. Deleting that `node_modules` by hand and restarting works too.
+Recovery: **uninstall** the plugin on the **Plugins** page, **install** it again with the version in the package name (for example `dsh-packycode-api@1.3.1`), then quit and reopen the desktop application. Uninstall runs `pnpm remove` and deletes the whole package directory; reinstalling or clicking **Update** only rewrites files and keeps the leftover tree. Deleting that `node_modules` by hand and restarting works too.
 
 **Right after a first install, every card in Settings shows `transport failure for /packycode-api/…: HTTP 405`?** The installed version is 1.1.6 or earlier, usually because only the bare package name was entered: the install prompt shows the newest version, but pnpm installs the newest one published at least 24 hours ago (see **Install the plugin**). Those older versions can register their settings channel only after DSH restarts and rebuilds its `connection` service. So right after a first install `/packycode-api` does not exist yet, requests fall through to the static page, and it answers 405; the model route and the settings panel itself load normally. From 1.1.7 on, a first install needs no restart. Check which version was installed:
 

package/README.md

@@ -47,10 +47,10 @@
 打开桌面应用的**插件**页，点击**添加插件**，在**包名或地址**中填入**带版本号**的包名：
 
 ```text
-dsh-packycode-api@1.3.0
+dsh-packycode-api@1.3.1
 ```
 
-在**安装源**中选择**官方源**，然后点击**安装**。`1.3.0` 是写这份说明时的最新版，当前最新版本号以 [npm 页面](https://www.npmjs.com/package/dsh-packycode-api) 为准。
+在**安装源**中选择**官方源**，然后点击**安装**。`1.3.1` 是写这份说明时的最新版，当前最新版本号以 [npm 页面](https://www.npmjs.com/package/dsh-packycode-api) 为准。
 
 > **一定要带版本号。** 只填 `dsh-packycode-api` 时，安装前的提示显示的是 npm 上的最新版，但 DSH 自带的 pnpm 默认只安装发布满 24 小时的版本，实际装上的可能是好几个版本之前的旧版，而安装提示里看不出这一点。填写精确版本时，pnpm 会直接安装这个版本，并自动把它加入 profile 的 `minimumReleaseAgeExclude`。装好后可以在 **设置 → PackyCode → 插件版本** 核对「当前版本」。
 
@@ -71,7 +71,7 @@ dsh-packycode-api@1.3.0
 
 桌面应用的**插件**页可以看到已安装状态与版本，也可以在那里启用、停用或卸载。
 
-**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.3.0`。不要对 `desktop` 使用它 —— CLI 会直接拒绝（`profile "desktop" is managed exclusively by the Electron application`）。
+**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.3.1`。不要对 `desktop` 使用它 —— CLI 会直接拒绝（`profile "desktop" is managed exclusively by the Electron application`）。
 
 本地开发要加 `link:` 前缀：`dsh plugin --profile <name> add link:/path/to/dsh-packycode-api`。**不要直接写路径（或 `file:`）** —— 那样的安装会把整个仓库目录（连同 `node_modules`）复制进 profile，之后它会在 profile 内部挡住 DSH 自带的包，插件看起来像没装，见「常见问题」。已经那样装过的话，先卸载再按上面的方式重装。
 
@@ -200,7 +200,7 @@ Responses 请求只有 GPT 模型保留 `prompt_cache_key`，其他 Responses
 
 ## 更新与卸载
 
-**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.3.0`），否则装上的可能是发布满 24 小时的旧版。
+**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.3.1`），否则装上的可能是发布满 24 小时的旧版。
 
 **从本地路径安装切回官方源时，必须先卸载。** 「更新」是 `pnpm add`，它只重写包目录里的文件，不会删除更早一次本地路径安装留在包目录内的 `node_modules`；那份旧依赖会继续挡住 DSH 自带的包，插件行加载失败且看不出原因。「卸载」执行的是 `pnpm remove`，会删掉整个包目录，重装才是干净的。用 `node scripts/install-check.mjs` 可以确认当前 profile 是否处于这个状态。
 
@@ -216,7 +216,7 @@ ls ~/.dsh/profiles/desktop/node_modules/dsh-packycode-api/node_modules
 
 有输出就是残留：从 npm 安装的包不会自带 `node_modules`，这一份通常来自更早一次「本地路径」安装（`file:` 或直接写路径，而不是 `link:`）。它位于 profile 目录内部，而 DSH 解析插件导入时优先使用 profile 内的副本，所以插件拿到的仍是那份旧依赖 —— 例如 `@deepseek-ai/schemastery` 3.18.2 没有 `Schema.volatile()`，模块在导入阶段就抛错。导入失败时 Loader 不会为这一行创建 fiber，客户端 bundle 也不会被组合，于是模型路由、RPC 通道和设置页全都不会出现。
 
-修复：到**插件**页**卸载**本插件，再用带版本号的包名重新**安装**（例如 `dsh-packycode-api@1.3.0`），然后完全退出并重新打开桌面应用。卸载执行的是 `pnpm remove`，会删掉整个包目录；直接重装或点「更新」只重写文件，不会清掉这份残留。也可以手动删掉上面那个 `node_modules` 再重启。
+修复：到**插件**页**卸载**本插件，再用带版本号的包名重新**安装**（例如 `dsh-packycode-api@1.3.1`），然后完全退出并重新打开桌面应用。卸载执行的是 `pnpm remove`，会删掉整个包目录；直接重装或点「更新」只重写文件，不会清掉这份残留。也可以手动删掉上面那个 `node_modules` 再重启。
 
 **首次安装后，设置页每张卡片都显示 `transport failure for /packycode-api/…: HTTP 405`？** 实际装上的是 1.1.6 或更早的版本，通常是因为安装时只填了包名：安装提示显示的是最新版，pnpm 实际装的却是发布满 24 小时的旧版（见「安装插件」）。这些旧版要等 DSH 重启、重建它的 `connection` 服务之后，才能注册设置通道。所以首次安装后 `/packycode-api` 通道还不存在，请求落到静态页面，返回 405；模型路由和设置页本身照常加载。1.1.7 起首次安装不需要重启。先确认装上的版本：
 

package/lib/client.js

@@ -592,10 +592,9 @@ window.__ModuleLoader__.load({
 		* Totals across the keys a balance read returned.
 		*
 		* The per-key quota (`/api/usage/token/`) is what a key can spend, so the
-		* combined figure is the sum of those rows. PackyCode also reports account
-		* level billing (`/v1/dashboard/billing/*`), which is a different scope — it
-		* counts every token on the account — and is deliberately not what this sum
-		* shows.
+		* combined figure is the sum of those rows. An API key cannot read the
+		* PackyCode account's own balance, so tokens on the same account that are not
+		* stored here never appear in it.
 		*
 		* @module dsh-packycode-api/totals
 		*/

package/lib/index.js

@@ -218,11 +218,10 @@ const DEFAULT_REASONING_LEVEL = "high";
 /**
 * Which hosts a read goes to.
 *
-* PackyCode serves models and the billing endpoints from `cf.api.fan`, and
-* the per-key `/api/*` family plus public pricing from the PackyAPI site
-* (`cf.api.fan` answers 404 there). A saved legacy status host
-* (`www.packyapi.com`, DNS-poisoned on mainland networks) is tried after the
-* current default, never before it.
+* PackyCode serves models from `cf.api.fan`, and the per-key `/api/*` family
+* plus public pricing from the PackyAPI site (`cf.api.fan` answers 404
+* there). A saved legacy status host (`www.packyapi.com`, DNS-poisoned on
+* mainland networks) is tried after the current default, never before it.
 *
 * @module dsh-packycode-api/hosts
 */
@@ -257,19 +256,6 @@ function statusHostOrder(hosts) {
 		DEFAULT_API_HOST
 	]);
 }
-/**
-* The hosts the account read tries: the model hosts first (they serve the
-* billing endpoints), then the status hosts.
-* @param hosts - the resolved host settings.
-* @returns unique origins.
-*/
-function accountHostOrder(hosts) {
-	return unique([
-		hosts?.apiHost,
-		DEFAULT_API_HOST,
-		...statusHostOrder(hosts)
-	]);
-}
 //#endregion
 //#region src/secret-redactor.js
 /**
@@ -288,15 +274,20 @@ function redactSecrets(text, values) {
 //#endregion
 //#region src/balance.js
 /**
-* Account and per-key balance.
+* Per-key balance.
 *
-* PackyCode is a new-api style relay: `/api/usage/token/` reports the quota of
-* the key that authorized the request, and `/v1/dashboard/billing/*` reports
-* the account. Only the second family exists on the model host (`cf.api.fan`
-* answers 404 for `/api/*`), so a read tries the configured host first and
-* falls back to the PackyAPI host — the same fallback the PackyCode status
-* tooling uses. A saved legacy status host (`www.packyapi.com`, DNS-poisoned
-* on mainland networks) is tried after the current default, not before it.
+* PackyCode is a new-api style relay, and an API key can read only its own
+* figures: `/api/usage/token/` reports the quota of the key that authorized
+* the request. The `/v1/dashboard/billing/*` family is per key on this gateway
+* as well — `hard_limit_usd` is the key's own grant, `total_usage` its own
+* spend in cents, and an unlimited key reports the placeholder limit
+* 100000000 — so it adds nothing and is not requested. The account's own
+* balance sits behind the dashboard API, which takes a login session rather
+* than a key. `cf.api.fan` answers 404 for the whole `/api/*` family, so a read
+* tries the status host first and falls back through the other PackyCode
+* hosts — the same fallback the PackyCode status tooling uses. A saved legacy
+* status host (`www.packyapi.com`, DNS-poisoned on mainland networks) is tried
+* after the current default, not before it.
 *
 * Credentials and response bodies stay host-side; the browser receives only
 * the projection built here.
@@ -354,25 +345,9 @@ function parseTokenUsage(payload) {
 		...expiresAt === void 0 || expiresAt <= 0 ? {} : { expiresAt }
 	};
 }
-/** Normalize `/v1/dashboard/billing/subscription`. */
-function parseBillingSubscription(payload) {
-	if (!record$2(payload)) return void 0;
-	return {
-		...number(payload.soft_limit_usd) === void 0 ? {} : { softLimitUsd: number(payload.soft_limit_usd) },
-		...number(payload.hard_limit_usd) === void 0 ? {} : { hardLimitUsd: number(payload.hard_limit_usd) },
-		...number(payload.system_hard_limit_usd) === void 0 ? {} : { systemHardLimitUsd: number(payload.system_hard_limit_usd) },
-		...number(payload.access_until) === void 0 || number(payload.access_until) <= 0 ? {} : { accessUntil: number(payload.access_until) }
-	};
-}
-/** Normalize `/v1/dashboard/billing/usage`. */
-function parseBillingUsage(payload) {
-	if (!record$2(payload)) return void 0;
-	const total = number(payload.total_usage);
-	return total === void 0 ? {} : { totalUsageUsd: Math.round(total * 1e6) / 1e6 };
-}
 function statusMessage(status) {
 	if (status === 401) return "this API key was rejected (401)";
-	if (status === 402 || status === 403) return "the account cannot be read with this key (402/403)";
+	if (status === 402 || status === 403) return "the gateway refused this key's balance read (402/403)";
 	if (status === 429) return "the gateway is rate limiting balance reads (429)";
 	return `the gateway answered HTTP ${status}`;
 }
@@ -416,17 +391,16 @@ async function withFallback(hosts, path, key, options) {
 * A read that fails for one key — the gateway throttled it, a host was
 * unreachable — keeps showing the last balance that key did report, marked
 * `stale` with when it was read and why this read failed, instead of blanking
-* the row. The same holds for the account figures. These last-good values
-* live in the host process: a page refresh keeps them, a restart does not.
+* the row. These last-good values live in the host process: a page refresh
+* keeps them, a restart does not.
 * @param options - key listing, host resolution, and transport knobs.
 * @returns `{ read({force, signal}), invalidate() }`.
 */
-function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now = Date.now, ttlMs = DEFAULT_BALANCE_TTL_MS, timeoutMs = DEFAULT_REQUEST_TIMEOUT_MS, includeAccount = true } = {}) {
+function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now = Date.now, ttlMs = DEFAULT_BALANCE_TTL_MS, timeoutMs = DEFAULT_REQUEST_TIMEOUT_MS } = {}) {
 	if (typeof listKeys !== "function") throw new Error("PackyCode balance reader requires listKeys");
 	if (typeof getHosts !== "function") throw new Error("PackyCode balance reader requires getHosts");
-	/** Last successful per-key usage, by key id, and the last account figures. */
+	/** Last successful per-key usage, by key id. */
 	const lastGood = /* @__PURE__ */ new Map();
-	let lastAccount;
 	const loadKey = async (entry, hosts, signal) => {
 		const { payload } = await withFallback(statusHostOrder(hosts), "/api/usage/token/", entry.key, {
 			fetchImpl,
@@ -437,43 +411,6 @@ function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now
 		if (usage === void 0) throw new Error("the gateway returned an unrecognized usage payload");
 		return usage;
 	};
-	/**
-	* The account endpoints need one working key. Candidates are ordered by
-	* evidence: a key whose per-key read just succeeded, then the key that
-	* answered this read last time, then the rest — so an invalid key sitting
-	* first in the ring cannot blank the account total.
-	*/
-	let accountKeyId;
-	const loadAccount = async (keys, hosts, signal, usableIds = []) => {
-		const candidates = [.../* @__PURE__ */ new Set([
-			...usableIds,
-			accountKeyId,
-			...keys.filter((entry) => entry.disabled !== true).map((entry) => entry.id)
-		])].map((id) => keys.find((entry) => entry.id === id)).filter((entry) => entry !== void 0);
-		if (candidates.length === 0) throw new Error("add a PackyCode API key to read the account balance");
-		const hostsToTry = accountHostOrder(hosts);
-		const options = {
-			fetchImpl,
-			timeoutMs,
-			signal
-		};
-		let lastError;
-		for (const key of candidates) try {
-			const subscription = parseBillingSubscription((await withFallback(hostsToTry, "/v1/dashboard/billing/subscription", key.key, options)).payload);
-			const usage = parseBillingUsage((await withFallback(hostsToTry, "/v1/dashboard/billing/usage", key.key, options)).payload);
-			const remaining = subscription?.hardLimitUsd === void 0 || usage?.totalUsageUsd === void 0 ? void 0 : Math.round((subscription.hardLimitUsd - usage.totalUsageUsd) * 1e6) / 1e6;
-			accountKeyId = key.id;
-			return {
-				...subscription,
-				...usage,
-				...remaining === void 0 ? {} : { remainingUsd: remaining },
-				keyId: key.id
-			};
-		} catch (error) {
-			lastError = error;
-		}
-		throw lastError;
-	};
 	const load = async (signal) => {
 		signal?.throwIfAborted();
 		const hosts = getHosts();
@@ -482,7 +419,6 @@ function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now
 		const safe = (value) => redactSecrets(value, secrets);
 		for (const id of lastGood.keys()) if (!keys.some((entry) => entry.id === id)) lastGood.delete(id);
 		const entries = [];
-		const usableIds = [];
 		for (const entry of keys) {
 			const base = {
 				id: entry.id,
@@ -501,7 +437,6 @@ function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now
 					...base,
 					usage
 				});
-				usableIds.push(entry.id);
 			} catch (error) {
 				signal?.throwIfAborted();
 				const message = safe(error instanceof Error ? error.message : String(error));
@@ -519,27 +454,8 @@ function createBalanceReader({ listKeys, getHosts, fetchImpl = ambientFetch, now
 				});
 			}
 		}
-		let account;
-		if (includeAccount) try {
-			account = await loadAccount(keys, hosts, signal, usableIds);
-			lastAccount = {
-				account,
-				fetchedAt: now()
-			};
-		} catch (error) {
-			signal?.throwIfAborted();
-			const message = safe(error instanceof Error ? error.message : String(error));
-			account = lastAccount === void 0 || !keys.some((entry) => entry.id === lastAccount.account.keyId) ? { error: message } : {
-				...lastAccount.account,
-				stale: {
-					fetchedAt: lastAccount.fetchedAt,
-					error: message
-				}
-			};
-		}
 		return {
 			keys: entries,
-			...includeAccount ? { account } : {},
 			hosts,
 			fetchedAt: now()
 		};
@@ -5183,8 +5099,7 @@ function apply(ctx, config) {
 	});
 	const imageBalance = createBalanceReader({
 		listKeys: () => imageRing.secrets(),
-		getHosts: hosts,
-		includeAccount: false
+		getHosts: hosts
 	});
 	/**
 	* Which token groups each key is in, and so which models it can reach.
@@ -5403,4 +5318,4 @@ function apply(ctx, config) {
 	});
 }
 //#endregion
-export { CHANNEL, Config, DEFAULT_API_HOST, DEFAULT_IMAGE_MODEL, DEFAULT_SEARCH_BACKEND, DEFAULT_STATUS_HOST, DIAGNOSTICS_FORMAT, DIAGNOSTICS_LIMITS, DISPLAY_NAME, IMAGE_MODELS, IMAGE_MODEL_IDS, IMAGE_QUALITIES, IMAGE_TIMEOUT_MS, IMAGE_TOOL_NAME, LEGACY_STATUS_HOSTS, MAX_IMAGE_BYTES, PACKYCODE_AUTO_SEARCH_PROVIDER_ID, PACKYCODE_MODELS, PACKYCODE_MODEL_IDS, PACKYCODE_SEARCH_PROVIDER_ID, PLUGIN_ID, PROVIDER, PackyCodeKeyRing, SEARCH_BACKENDS, SEARCH_BACKEND_MODELS, SEARCH_MODES, SETTINGS_NAMESPACE, TEST_MESSAGE_POLICY_CODE, accountHostOrder, apply, assertApiKey, buildSearchRequest, catalogCoverage, classifyClientPolicy, classifyGatewayFailure, classifyTestMessagePolicy, classifyUpstreamServerError, createBalanceReader, createDiagnostics, createGroupReader, createImageController, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decodeImagePng, explainClientPolicyFailure, explainTestMessagePolicyFailure, guardKeyRotation, inject, name, normalizeFailureMessage, normalizeHost, parseBillingSubscription, parseBillingUsage, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, pngDimensions, readHiddenModels, readImagePreference, readSearchChoice, statusHostOrder, summarizeSessionEvents, validateImageOptions };
+export { CHANNEL, Config, DEFAULT_API_HOST, DEFAULT_IMAGE_MODEL, DEFAULT_SEARCH_BACKEND, DEFAULT_STATUS_HOST, DIAGNOSTICS_FORMAT, DIAGNOSTICS_LIMITS, DISPLAY_NAME, IMAGE_MODELS, IMAGE_MODEL_IDS, IMAGE_QUALITIES, IMAGE_TIMEOUT_MS, IMAGE_TOOL_NAME, LEGACY_STATUS_HOSTS, MAX_IMAGE_BYTES, PACKYCODE_AUTO_SEARCH_PROVIDER_ID, PACKYCODE_MODELS, PACKYCODE_MODEL_IDS, PACKYCODE_SEARCH_PROVIDER_ID, PLUGIN_ID, PROVIDER, PackyCodeKeyRing, SEARCH_BACKENDS, SEARCH_BACKEND_MODELS, SEARCH_MODES, SETTINGS_NAMESPACE, TEST_MESSAGE_POLICY_CODE, apply, assertApiKey, buildSearchRequest, catalogCoverage, classifyClientPolicy, classifyGatewayFailure, classifyTestMessagePolicy, classifyUpstreamServerError, createBalanceReader, createDiagnostics, createGroupReader, createImageController, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decodeImagePng, explainClientPolicyFailure, explainTestMessagePolicyFailure, guardKeyRotation, inject, name, normalizeFailureMessage, normalizeHost, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, pngDimensions, readHiddenModels, readImagePreference, readSearchChoice, statusHostOrder, summarizeSessionEvents, validateImageOptions };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-packycode-api",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "Use PackyCode API keys in DeepSeek Harness with multi-protocol models, image generation and editing, separate key rings, and balance display",
   "type": "module",
   "main": "./lib/index.js",