dsh-packycode-api 1.2.8 → 1.2.10

package/AGENTS.md

@@ -31,6 +31,7 @@ This file governs the entire `dsh-packycode-api` repository.
 - Edit `src/`; never hand-edit generated `lib/index.js` or `lib/client.js`.
 - `lib/` is tracked and must be regenerated with `pnpm run build` after source changes.
 - `.artifacts/` and `node_modules/` are ignored and must never be committed.
+- `docs/releases/v<version>.md` holds each version's GitHub Release notes. It is tracked and not packaged.
 - Add or update tests under `tests/` for behavior changes.
 
 ## Required validation
@@ -71,7 +72,13 @@ Never reuse, move, delete, or overwrite a published npm version or Git tag. If a
 
    For an unused npm version, `npm view` normally returns `E404`. An existing npm version or Git tag requires choosing a new version.
 
-3. Update all release metadata together: `package.json` version, `CHANGELOG.md`, and any version pinned in `README.md` / `README.en.md`.
+3. Update all release metadata together: `package.json` version, `CHANGELOG.md`, any version pinned in `README.md` / `README.en.md`, and the GitHub Release notes in `docs/releases/v<version>.md`. The notes are in Chinese, like every earlier release:
+   - The first line is `# v<version>：<短标题>`, which becomes the release title.
+   - Then a one-sentence summary and bullets with bold labels.
+   - Then a `验证：…` paragraph.
+   - They close with `在 DSH 插件管理中更新至 **<version>**，然后重新打开 DSH 加载新版。`
+
+   `node scripts/release-notes.mjs <version>` checks the file, and `pnpm run check` fails while the current `package.json` version has no valid notes.
 
 4. Validate and inspect the exact release artifact:
 
@@ -85,7 +92,7 @@ Never reuse, move, delete, or overwrite a published npm version or Git tag. If a
 
 6. Confirm the package has a GitHub Actions trusted publisher before pushing the tag: repository `BaronCyrus/dsh-packycode-api`, workflow filename `publish.yml`, environment empty. Never request that a token, password, or one-time code be pasted into chat.
 
-7. Create the annotated tag and push it. That push publishes with GitHub OIDC. Do not run `npm publish` locally for a release. A local publish cannot attach provenance. Do not set `NODE_AUTH_TOKEN` or a setup-node `registry-url` in the publish workflow; npm treats either as token auth and skips OIDC.
+7. Create the annotated tag and push it. That push publishes with GitHub OIDC. The workflow's `release` job then creates the GitHub Release from `docs/releases/v<version>.md` and attaches the tarball npm published. It is the only job with `contents: write`, and it runs no dependency code. Do not run `npm publish` locally for a release. A local publish cannot attach provenance. Do not set `NODE_AUTH_TOKEN` or a setup-node `registry-url` in the publish workflow; npm treats either as token auth and skips OIDC.
 
    ```sh
    git tag -a v<version> -m "dsh-packycode-api v<version>"
@@ -94,4 +101,6 @@ Never reuse, move, delete, or overwrite a published npm version or Git tag. If a
 
    `workflow_dispatch` on the same workflow only prints the OIDC identity npm will match. It does not publish.
 
-8. Confirm the publish workflow succeeded for that tag before declaring the release public. On an OIDC `package not found` error, fix the trusted publisher and re-run the same workflow. Do not move the tag. If the tagged tree itself must change, publish a new patch version.
+8. Confirm that both jobs of the publish workflow succeeded for that tag before declaring the release public. Then check that npm serves the version and that `gh release view v<version>` shows the notes, the `dsh-packycode-api-<version>.tgz` asset and, for the newest version, the Latest mark. On an OIDC `package not found` error, fix the trusted publisher and re-run the same workflow. Do not move the tag. If the tagged tree itself must change, publish a new patch version.
+
+   If npm published but the release job failed, re-run only that failed job. If the Release must be made by hand, attach the tarball npm serves, not a local `.artifacts` build: CI packs its own, so the local bytes differ. Fetch it with `npm pack dsh-packycode-api@<version>`, and compare its SHA-512 with the registry's `dist.integrity`. Then run `gh release create v<version> <tarball> --verify-tag --title "<the notes' title>" --notes-file <the notes' body>`. The release job leaves an existing Release unchanged.

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 1.2.10
+
+- **OpenAI's transient server error is retried instead of failing the turn.** On the Codex group, a `gpt-6.1-sol` turn sometimes ended in 本轮运行失败 "An error occurred while processing your request. You can retry your request, or contact us through our help center at help.openai.com if the error persists." with `PI_AI_ERROR`. The gateway had already answered HTTP 200 and started the stream when the upstream failed: an SSE `error` event carrying a 503 `server_error`, then `response.failed`, before any output. The OpenAI SDK raises that without an HTTP status, so DSH's adapter, which reads a failure's category from status words, filed it as `PI_AI_ERROR`, a code no retry policy re-runs. The same failure sent as an HTTP 500 is `SERVER` and was already retried. The route now files OpenAI's `server_error` (its sentence, or pi-ai's `server_error:` prefix) as `SERVER` when the adapter left it unclassified, on prepared and direct calls alike, so the route's existing policy (up to 20 retries with backoff) resends the request. Only the code changes: if every retry fails, the upstream sentence still reaches the user, after up to about three minutes, as for an HTTP 500. The key stays enabled and is not rotated. The official Codex client also retries this failure (`ApiError::Retryable`).
+- Validation, 2026-10-16: 457 offline tests (5 new; three of them failed with `PI_AI_ERROR` before the fix), both rebuilt bundles and the versioned tarball. Live on a `codex`-group key at high effort: through the 1.2.9 route, 2 of 14 `gpt-6.1-sol` requests received the relayed 503 at the fourth stream event, before any output, and ended as `PI_AI_ERROR`. One of them was a session's first request with no reasoning replay, and both identical resends succeeded. Through this build, 2 of 20 requests (a first attempt and its immediate resend) received it, and both ended as `SERVER` with the upstream sentence unchanged. A further 16 requests under the route's own retry policy met no upstream failure. `scripts/live-check.mjs` passed: every HTTP model answered, and key rotation and the RPC projections were unchanged. About $0.32 of test quota. No DSH restart.
+- **A release also creates its GitHub Release.** A `v*` tag push publishes to npm and then, in a separate `release` job, creates the GitHub Release from `docs/releases/v<version>.md` with the tarball npm published attached. The publish job refuses a tag whose notes are missing or malformed before npm publishes it. Only the release job holds `contents: write`, and it runs no dependency code. `workflow_dispatch` still only checks the OIDC identity. The notes for 1.2.7–1.2.9, whose Releases were made by hand, are in `docs/releases/`. AGENTS.md's release checklist now covers writing the notes, checking the Release, and making one by hand.
+
+## 1.2.9
+
+- **Remove all works again.** **Remove all** under **Accounts and keys** answered "读取 PackyCode 状态失败: PackyCode request failed" and kept every key. Emptying the ring wrote `activeId: undefined`, and DSH's credential store (`credentials-local`) accepts only plain JSON in a grant payload, so it refused the whole write. The same refusal hit removing the last conversation or image key on its own, and marking the only key unusable after its quota ran out or the gateway rejected it. That last case was only logged ("could not move past key …"), so a lone exhausted key was never shown as disabled. The ring now leaves out a field that has no value: an empty ring stores no `activeId`, and a disabled mark from a hand-edited record stores no empty reason.
+- A credential-store failure now reads "PackyCode could not save the key change in DSH's credential store" instead of the generic "PackyCode request failed". A refused key change is labelled 更新 Key 失败 / "Could not update the keys" instead of being reported as a failed status read.
+- Validation, 2026-10-16: 444 offline tests (7 new), both rebuilt bundles and the versioned tarball. The suite's in-memory credential store now refuses non-JSON payloads exactly as DSH 0.2.0-rc.2's `credentials-local` does, and four existing key-ring tests failed against it before the fix. The change is host-side key storage, not the catalog, the provider composition or failure classification, so no live gateway call was made. No DSH restart.
+
 ## 1.2.8
 
 - **Diagnostics for request problems.** Settings → PackyCode gains a **Diagnostics** card (诊断信息). A user who hits "已达到输出 token 上限" or repeated failures picks the session (the 20 most recent top-level sessions, newest first, labelled by local start time, the workspace folder's base name and whether it is open), clicks **Generate diagnostics** and then **Copy**, and sends the text to the plugin author. Without a clipboard API the text is selected for a manual copy. The host builds the text from DSH's session history over two new RPC endpoints, `diagnostics/sessions` and `diagnostics/session`, in format `packycode-diagnostics/1`. It holds the plugin version; the session id, start time and live state; each stored key by position with its groups and reachable models; the logged request settings (provider, model, reasoning effort, `maxTokens`, and whether DSH's adapter supplied that ceiling); the steps that ended at the output limit; the latest steps' token usage and finish reasons; turn endings; retries and failed attempts with their codes; and the compaction count. Error messages are redacted and cut to 160 characters. Conversation text, reasoning, titles, tool arguments and results, paths, key labels and keys never enter it. An invalid session id or a runtime without session history is refused with its own message.

package/README.en.md

@@ -48,10 +48,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.2.8
+dsh-packycode-api@1.2.10
 ```
 
-Choose the **official** install source, then click **Install**. `1.2.8` 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.2.10` 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**.
 
@@ -72,7 +72,7 @@ Choose a model from the `PackyCode` group. `deepseek-flash`, `gpt-6.1-sol`, `gpt
 
 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.2.8`. 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.2.10`. 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.
 
@@ -213,7 +213,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.2.8`); 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.2.10`); 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.
 
@@ -229,7 +229,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.2.8`), 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.2.10`), 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:
 
@@ -288,7 +288,7 @@ pnpm run check
 
 `node scripts/install-check.mjs` diagnoses an installed plugin that never appears: it reads one profile, lists any host package shadowed by a leftover `node_modules` inside an installed package (with versions) plus the recovery steps, and exits 1 when it finds one. `--profile <name>`, `--home <dir>`, and `--json` are available.
 
-Read [AGENTS.md](AGENTS.md) before agent-assisted changes or a release. Publishing is the [Publish workflow](.github/workflows/publish.yml), triggered by pushing a `v*` tag. Do not run `npm publish` locally.
+Read [AGENTS.md](AGENTS.md) before agent-assisted changes or a release. Publishing is the [Publish workflow](.github/workflows/publish.yml), triggered by pushing a `v*` tag: it publishes to npm, then creates the GitHub Release from `docs/releases/v<version>.md` with the same tarball. Do not run `npm publish` locally.
 
 ## License
 

package/README.md

@@ -48,10 +48,10 @@
 打开桌面应用的**插件**页，点击**添加插件**，在**包名或地址**中填入**带版本号**的包名：
 
 ```text
-dsh-packycode-api@1.2.8
+dsh-packycode-api@1.2.10
 ```
 
-在**安装源**中选择**官方源**，然后点击**安装**。`1.2.8` 是写这份说明时的最新版，当前最新版本号以 [npm 页面](https://www.npmjs.com/package/dsh-packycode-api) 为准。
+在**安装源**中选择**官方源**，然后点击**安装**。`1.2.10` 是写这份说明时的最新版，当前最新版本号以 [npm 页面](https://www.npmjs.com/package/dsh-packycode-api) 为准。
 
 > **一定要带版本号。** 只填 `dsh-packycode-api` 时，安装前的提示显示的是 npm 上的最新版，但 DSH 自带的 pnpm 默认只安装发布满 24 小时的版本，实际装上的可能是好几个版本之前的旧版，而安装提示里看不出这一点。填写精确版本时，pnpm 会直接安装这个版本，并自动把它加入 profile 的 `minimumReleaseAgeExclude`。装好后可以在 **设置 → PackyCode → 插件版本** 核对「当前版本」。
 
@@ -72,7 +72,7 @@ dsh-packycode-api@1.2.8
 
 桌面应用的**插件**页可以看到已安装状态与版本，也可以在那里启用、停用或卸载。
 
-**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.2.8`。不要对 `desktop` 使用它 —— CLI 会直接拒绝（`profile "desktop" is managed exclusively by the Electron application`）。
+**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.2.10`。不要对 `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 自带的包，插件看起来像没装，见「常见问题」。已经那样装过的话，先卸载再按上面的方式重装。
 
@@ -213,7 +213,7 @@ Responses 请求只有 GPT 模型保留 `prompt_cache_key`，其他 Responses
 
 ## 更新与卸载
 
-**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.2.8`），否则装上的可能是发布满 24 小时的旧版。
+**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.2.10`），否则装上的可能是发布满 24 小时的旧版。
 
 **从本地路径安装切回官方源时，必须先卸载。** 「更新」是 `pnpm add`，它只重写包目录里的文件，不会删除更早一次本地路径安装留在包目录内的 `node_modules`；那份旧依赖会继续挡住 DSH 自带的包，插件行加载失败且看不出原因。「卸载」执行的是 `pnpm remove`，会删掉整个包目录，重装才是干净的。用 `node scripts/install-check.mjs` 可以确认当前 profile 是否处于这个状态。
 
@@ -229,7 +229,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.2.8`），然后完全退出并重新打开桌面应用。卸载执行的是 `pnpm remove`，会删掉整个包目录；直接重装或点「更新」只重写文件，不会清掉这份残留。也可以手动删掉上面那个 `node_modules` 再重启。
+修复：到**插件**页**卸载**本插件，再用带版本号的包名重新**安装**（例如 `dsh-packycode-api@1.2.10`），然后完全退出并重新打开桌面应用。卸载执行的是 `pnpm remove`，会删掉整个包目录；直接重装或点「更新」只重写文件，不会清掉这份残留。也可以手动删掉上面那个 `node_modules` 再重启。
 
 **首次安装后，设置页每张卡片都显示 `transport failure for /packycode-api/…: HTTP 405`？** 实际装上的是 1.1.6 或更早的版本，通常是因为安装时只填了包名：安装提示显示的是最新版，pnpm 实际装的却是发布满 24 小时的旧版（见「安装插件」）。这些旧版要等 DSH 重启、重建它的 `connection` 服务之后，才能注册设置通道。所以首次安装后 `/packycode-api` 通道还不存在，请求落到静态页面，返回 405；模型路由和设置页本身照常加载。1.1.7 起首次安装不需要重启。先确认装上的版本：
 
@@ -288,7 +288,7 @@ Claude CLI 的 MCP 接口验证用 `node scripts/cli-search-check.mjs`：运行
 
 排查「装了却看不到插件」用 `node scripts/install-check.mjs`：它只读当前 profile，列出被包内残留 `node_modules` 挡住的宿主包（含版本）和对应的修复步骤，发现问题时以退出码 1 结束；`--profile <name>`、`--home <dir>` 可指定其它 profile，`--json` 输出结构化结果。
 
-使用 Agent 修改或发布时，先读 [AGENTS.md](AGENTS.md)。发布由推送 `v*` 标签触发 [Publish workflow](.github/workflows/publish.yml)，不要在本机执行 `npm publish`。
+使用 Agent 修改或发布时，先读 [AGENTS.md](AGENTS.md)。发布由推送 `v*` 标签触发 [Publish workflow](.github/workflows/publish.yml)：先发布到 npm，再用 `docs/releases/v<版本>.md` 和同一个包创建 GitHub Release。不要在本机执行 `npm publish`。
 
 ## License
 

package/lib/client.js

@@ -118,6 +118,7 @@ window.__ModuleLoader__.load({
 			add: "添加",
 			notWritable: "当前 profile 不允许写入设置，改动只在本次运行内生效。",
 			error: "读取 PackyCode 状态失败",
+			saveError: "更新 Key 失败",
 			groupsTitle: "分组",
 			groupsChecking: "正在读取分组…",
 			groupsUnknown: "分组未读到",
@@ -317,6 +318,7 @@ window.__ModuleLoader__.load({
 			add: "Add",
 			notWritable: "This profile does not allow settings writes; changes apply to this run only.",
 			error: "Could not read PackyCode status",
+			saveError: "Could not update the keys",
 			groupsTitle: "Groups",
 			groupsChecking: "Reading groups…",
 			groupsUnknown: "Groups not read",
@@ -2192,7 +2194,10 @@ window.__ModuleLoader__.load({
 					setStatus(nextStatus);
 					setBalance(nextBalance);
 				}).catch((failure) => {
-					if (generation.current === current) setError(clearMessage(failure));
+					if (generation.current === current) setError({
+						kind: "read",
+						message: clearMessage(failure)
+					});
 				}).finally(() => {
 					if (generation.current === current) setBusy(false);
 				});
@@ -2203,14 +2208,21 @@ window.__ModuleLoader__.load({
 					generation.current += 1;
 				};
 			}, [load]);
+			/** A refused change says so; a balance read after a stored change is a read. */
 			const mutate = (endpoint, payload) => {
 				setBusy(true);
 				setError(void 0);
 				return call(endpoint, payload).then((nextStatus) => {
 					setStatus(nextStatus);
 					readGroups(false);
-					return call("balance", { force: true });
-				}).then(setBalance).catch((failure) => setError(clearMessage(failure))).finally(() => setBusy(false));
+					return call("balance", { force: true }).then(setBalance, (failure) => setError({
+						kind: "read",
+						message: clearMessage(failure)
+					}));
+				}, (failure) => setError({
+					kind: "save",
+					message: clearMessage(failure)
+				})).finally(() => setBusy(false));
 			};
 			const addKey = (event) => {
 				event.preventDefault();
@@ -2319,7 +2331,7 @@ window.__ModuleLoader__.load({
 					error !== void 0 && /* @__PURE__ */ (0, react_jsx_runtime.jsx)("p", {
 						className: "pkc-error",
 						role: "alert",
-						children: `${t("error")}: ${error}`
+						children: `${t(error.kind === "save" ? "saveError" : "error")}: ${error.message}`
 					}),
 					/* @__PURE__ */ (0, react_jsx_runtime.jsxs)("details", {
 						className: "pkc-advanced",

package/lib/index.js

@@ -852,6 +852,23 @@ function classifyClientPolicy(message) {
 	return CLIENT_POLICY_WORDING.test(typeof message === "string" ? message : "");
 }
 /**
+* OpenAI's generic transient failure: the sentence its `server_error` carries,
+* or the `server_error:` prefix pi-ai writes when the event names the code.
+* The gateway can relay it inside a stream it has already answered 200 for —
+* an SSE `error` event with a 503 `server_error`, then `response.failed` — so
+* no HTTP status comes with it.
+*/
+const UPSTREAM_SERVER_ERROR = /an error occurred while processing your request\b[\s\S]*\bhelp\.openai\.com\b|^(?:error code\s+)?server_error:/iu;
+/**
+* Whether a failure is the upstream's transient server error, which a resent
+* request clears. The key is not at fault.
+* @param message - provider failure text, as pi-ai carries it.
+* @returns true for OpenAI's generic `server_error`.
+*/
+function classifyUpstreamServerError(message) {
+	return UPSTREAM_SERVER_ERROR.test(typeof message === "string" ? message : "");
+}
+/**
 * Classify a gateway failure message.
 *
 * Quota wording wins over a status token: an exhausted balance is often
@@ -6351,28 +6368,48 @@ var PackyCodeKeyRing = class {
 	async #read() {
 		return normalizeState(await this.#credentials.readRecord(this.#recordKey));
 	}
+	/**
+	* Replace the record with what `mutate` decides. The store accepts plain
+	* JSON only and refuses a payload holding `undefined`, so a field without a
+	* value is left out: an emptied ring has no `activeId`, and a disabled mark
+	* from a hand-edited record may have no reason. A store failure is reported
+	* in the ring's own words, since the store's may quote the credential file.
+	*/
 	async #write(mutate) {
-		return normalizeState(await this.#credentials.modifyRecord(this.#recordKey, async (current) => {
-			const updated = await mutate(normalizeState(current));
-			if (updated === void 0) return current;
-			return {
-				kind: "grant",
-				payload: {
-					version: RECORD_VERSION,
-					activeId: updated.activeId,
-					keys: updated.keys.map((candidate) => ({
-						id: candidate.id,
-						label: candidate.label,
-						key: candidate.key,
-						addedAt: candidate.addedAt,
-						...candidate.disabledAt === void 0 ? {} : {
-							disabledAt: candidate.disabledAt,
-							disabledReason: candidate.disabledReason
-						}
-					}))
+		let refused = false;
+		let next;
+		try {
+			next = await this.#credentials.modifyRecord(this.#recordKey, async (current) => {
+				const state = normalizeState(current);
+				let updated;
+				try {
+					updated = await mutate(state);
+				} catch (error) {
+					refused = true;
+					throw error;
 				}
-			};
-		}));
+				if (updated === void 0) return current;
+				return {
+					kind: "grant",
+					payload: {
+						version: RECORD_VERSION,
+						...updated.activeId === void 0 ? {} : { activeId: updated.activeId },
+						keys: updated.keys.map((candidate) => ({
+							id: candidate.id,
+							label: candidate.label,
+							key: candidate.key,
+							addedAt: candidate.addedAt,
+							...candidate.disabledAt === void 0 ? {} : { disabledAt: candidate.disabledAt },
+							...candidate.disabledAt === void 0 || candidate.disabledReason === void 0 ? {} : { disabledReason: candidate.disabledReason }
+						}))
+					}
+				};
+			});
+		} catch (error) {
+			if (refused) throw error;
+			throw new Error("PackyCode could not save the key change in DSH's credential store", { cause: error });
+		}
+		return normalizeState(next);
 	}
 	/** The keys as the browser may see them. */
 	async list() {
@@ -7125,6 +7162,32 @@ const REQUEST_LIMITS = Object.freeze({
 	requestImageMaxBytes: 1024 * 1024
 });
 /**
+* Give the retry policy a failure the host adapter cannot classify.
+*
+* The host reads a failure's category from status words in its text. An
+* upstream `server_error` relayed inside an accepted stream carries none, so
+* it arrives as the catch-all PI_AI_ERROR, which no retry re-runs — while the
+* same failure as an HTTP 500 is SERVER and is retried. Only the code
+* changes: if every retry fails, the upstream sentence reaches the user as is.
+* @param stream - the adapter's harness chunks.
+* @returns the same chunks, with that failure filed as SERVER.
+*/
+async function* classifyRouteFailures(stream) {
+	for await (const chunk of stream) {
+		const failure = chunk.type === "finish" && chunk.reason?.kind === "error" ? chunk.reason.failure : void 0;
+		yield failure?.code === "PI_AI_ERROR" && classifyUpstreamServerError(failure.message) ? {
+			...chunk,
+			reason: {
+				...chunk.reason,
+				failure: {
+					...failure,
+					code: "SERVER"
+				}
+			}
+		} : chunk;
+	}
+}
+/**
 * pi-ai's credential store over the key ring.
 *
 * Reads answer with the active key so pi-ai's own auth reporting stays honest,
@@ -7237,6 +7300,16 @@ function createRouteAdapter({ ring, keys, fallbackSessionId, resolveAttachments,
 	});
 	const profiles = /* @__PURE__ */ new Map([[PROVIDER, createPackyCodeProfile(provider)]]);
 	return new class extends PiAiAdapter {
+		async prepareCall(provider, model, signal) {
+			const prepared = await super.prepareCall(provider, model, signal);
+			return {
+				...prepared,
+				stream: (options) => classifyRouteFailures(prepared.stream(options))
+			};
+		}
+		stream(options) {
+			return classifyRouteFailures(super.stream(options));
+		}
 		async listModels(provider) {
 			return (await super.listModels(provider)).filter((model) => isModelVisible(model.id));
 		}
@@ -8664,4 +8737,4 @@ function apply(ctx, config) {
 	});
 }
 //#endregion
-export { AUTO_CLAUDE_MODE, CHANNEL, CLAUDE_CLI_MODES, CLAUDE_INSTALL_COMMAND, CLAUDE_MISSING_MESSAGE, CLAUDE_NPM_PACKAGE, CLAUDE_TOOL_INSTRUCTIONS, CLI_BACKED_MODEL_IDS, CLI_IMAGE_LIMITS, Config, DEFAULT_API_HOST, DEFAULT_APPEND_SYSTEM_PROMPT, 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_CLI_IMAGE_CALLS, MAX_IMAGE_BYTES, MCP_IMAGE_SCHEMA, 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, TITLE_MODEL_ID, TITLE_MODEL_ROUTES, accountHostOrder, apply, assertApiKey, buildClaudeArgs, buildClaudeEnvironment, buildClaudeInput, buildDelegatedContent, buildSearchRequest, capClaudeMode, catalogCoverage, classifyClientPolicy, classifyGatewayFailure, claudeBinaryCandidates, claudeModeFor, claudeModeForSession, cliSearchInstructions, createBalanceReader, createClaudeCliAdapter, createClaudeCliManager, createClaudeCodeTool, createClaudeImageService, createClaudeRunner, createClaudeSearchBridge, createDiagnostics, createGroupReader, createImageController, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decodeImagePng, delegationInstructions, describeRunKey, explainCliClientPolicyFailure, explainCliGroupFailure, explainClientPolicyFailure, explainNpmFailure, findClaudeBinary, guardKeyRotation, inject, keyNote, locateClaudeBinary, locateNpm, name, normalizeFailureMessage, normalizeHost, npmCandidates, parseBillingSubscription, parseBillingUsage, parseClaudeResult, parseClaudeVersion, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, planModeForSession, planModeForToolExecution, pngDimensions, readClaudeStreamEvents, readHiddenModels, readImagePreference, readSearchChoice, renderAuxiliaryPrompt, renderDelegatedPrompt, renderTitlePrompt, resolveSpawnCommand, statusHostOrder, summarizeSessionEvents, summarizeToolUse, unwrapTitle, validateImageOptions };
+export { AUTO_CLAUDE_MODE, CHANNEL, CLAUDE_CLI_MODES, CLAUDE_INSTALL_COMMAND, CLAUDE_MISSING_MESSAGE, CLAUDE_NPM_PACKAGE, CLAUDE_TOOL_INSTRUCTIONS, CLI_BACKED_MODEL_IDS, CLI_IMAGE_LIMITS, Config, DEFAULT_API_HOST, DEFAULT_APPEND_SYSTEM_PROMPT, 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_CLI_IMAGE_CALLS, MAX_IMAGE_BYTES, MCP_IMAGE_SCHEMA, 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, TITLE_MODEL_ID, TITLE_MODEL_ROUTES, accountHostOrder, apply, assertApiKey, buildClaudeArgs, buildClaudeEnvironment, buildClaudeInput, buildDelegatedContent, buildSearchRequest, capClaudeMode, catalogCoverage, classifyClientPolicy, classifyGatewayFailure, classifyUpstreamServerError, claudeBinaryCandidates, claudeModeFor, claudeModeForSession, cliSearchInstructions, createBalanceReader, createClaudeCliAdapter, createClaudeCliManager, createClaudeCodeTool, createClaudeImageService, createClaudeRunner, createClaudeSearchBridge, createDiagnostics, createGroupReader, createImageController, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decodeImagePng, delegationInstructions, describeRunKey, explainCliClientPolicyFailure, explainCliGroupFailure, explainClientPolicyFailure, explainNpmFailure, findClaudeBinary, guardKeyRotation, inject, keyNote, locateClaudeBinary, locateNpm, name, normalizeFailureMessage, normalizeHost, npmCandidates, parseBillingSubscription, parseBillingUsage, parseClaudeResult, parseClaudeVersion, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, planModeForSession, planModeForToolExecution, pngDimensions, readClaudeStreamEvents, readHiddenModels, readImagePreference, readSearchChoice, renderAuxiliaryPrompt, renderDelegatedPrompt, renderTitlePrompt, resolveSpawnCommand, statusHostOrder, summarizeSessionEvents, summarizeToolUse, unwrapTitle, validateImageOptions };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-packycode-api",
-  "version": "1.2.8",
+  "version": "1.2.10",
   "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",