dsh-packycode-api 1.4.8 → 1.4.9

package/CHANGELOG.md

@@ -1,5 +1,14 @@
 # Changelog
 
+## 1.4.9
+
+- **Auto review asks `jev-1.14.0`.** PackyCode retired the `jev-latest` alias: on 2026-11-13 `/api/pricing` lists `jev-1.14.0` and `jev-1.13.0` in `typesafe-officially` and no `jev-latest`, and a `/v1/systemone` request naming `jev-latest` is refused before any upstream (`400 model_not_found`, `当前令牌未覆盖供应商`), while `jev-1.14.0` answered in about 1.3 s. The reviewer, the classifier descriptor whose group coverage the settings read, the denial reasons and every failure sentence now use `jev-1.14.0`.
+- **A saved `jev-latest` choice keeps working.** Taking the alias out of the Config schema would make the plugin's Config fail to parse for anyone who had picked it. The schema keeps it as a hidden value, and the preference reader maps it to `jev-1.14.0` (`RETIRED_AUTO_REVIEW_MODELS` in `src/auto-review.js`). The card offers only the versioned reviewer and refuses the alias on write.
+- Validation, 2026-11-13:
+  - **Offline:** 570 tests (new: a saved `jev-latest` parses through the plugin Config, stays out of the offered choices, reads as `jev-1.14.0` in the preference, the status and the `llm/stream` listener, and is refused on write; Jev's request body, denial reason and coverage sentence name `jev-1.14.0`; the classifier descriptor, the client's coverage line and the settings card use it), both rebuilt bundles and the versioned tarball.
+  - **Live, `scripts/live-check.mjs` with the test key:** the group reading reached `jev-1.14.0`. The official review request was answered by `jev-1.14.0` with allow → allow (low risk) in 0.46 s and deny → deny (high risk) in 0.47 s, and by DeepSeek Flash with 1.28 s and 1.50 s. All fourteen catalog models answered through the route, and key rotation, the rejected-key classification, the RPC projections and the Claude CLI route were unchanged. A direct `/v1/systemone` request named `jev-1.14.0` answered; one naming `jev-latest` was refused.
+  - **Not checked:** the settings card in the desktop app (its rendering is covered by the built-bundle test, not by a look at the app). The id is pinned, so the next time PackyCode retires a Jev version the constant needs the same change.
+
 ## 1.4.8
 
 - **Claude Fable 5.2 joins the catalog.** On 2026-11-11 `/api/pricing` lists `claude-fable-5-2` with the `anthropic` endpoint alone, in `cc`, `cc-sale`, `cc-expensive`, `claude-officially` and `aws-q`. It takes the route of the other Claude models: `anthropic-messages` at `https://cf.api.fan`, text and image input, 1,000,000 context and 128,000 output, first in the picker's Claude models. Anthropic's [Claude Fable 5.2 overview](https://platform.claude.com/docs/en/models/fable-5-2/overview) gives the 1M context window (its default and maximum) and 128K output, thinking that is always on and adaptive, `output_config.effort` `low` to `max` as the only depth control, and no `temperature`; so it offers `low` / `medium` / `high` / `xhigh` / `max` and cannot be turned off, like the 5.5 models. A key in `cc` runs it through the Claude Code CLI as the agent; the other Claude groups use HTTP, where it asks for progress-update thinking (`display: "updates"` with the `thinking-display-updates-2026-08-18` beta) as Opus and Sonnet 5.5 do. Its session titles run on `claude-haiku-5-5`. The settings page counts it in each key's Claude coverage, and `scripts/claude-check.mjs` and `scripts/claude-agent-check.mjs` include it; the six-hour `scripts/claude-stability.mjs` window still samples the three 5.5 models, which its request budget is sized for.

package/README.en.md

@@ -32,7 +32,7 @@ The `PackyCode` model group ships with the plugin. No YAML edits and no separate
 | **Claude route by group** | The `cc` group only serves the official client, so Claude sessions on `cc` keys are carried out by this device's Claude Code itself, with its own system prompt and tools, while DSH shows every tool call and handles permissions, plan review and questions; `cc-sale`, `cc-expensive`, `claude-officially` and other groups use the plugin's HTTP route with DSH's own agent |
 | **Web search through PackyCode** | Optional: DSH's `web_search` searches through PackyCode, with a DeepSeek or GPT backend, for every request or for PackyCode models only |
 | **Image generation and editing** | Separate image keys, GPT Image 2 / 2.6 Flare / 2.6 Sunburst, model and quality settings, reference edits and original PNG storage; generation and editing verified against the gateway |
-| **Auto review on your model** | With DSH's built-in “Auto authorization review” switched on, the permission menu's Auto review can review each tool call with jev-latest or DeepSeek Flash; the rules and outcomes stay the official ones |
+| **Auto review on your model** | With DSH's built-in “Auto authorization review” switched on, the permission menu's Auto review can review each tool call with jev-1.14.0 or DeepSeek Flash; the rules and outcomes stay the official ones |
 | **Credentials stay on the machine** | Keys live in the DSH credential file. The browser receives labels, state, and balances only |
 
 <img width="774" height="455" alt="截屏2026-10-15 10 34 28" src="https://github.com/user-attachments/assets/c5eaa535-dd1e-4e2f-be9f-c181404d4dd6" />
@@ -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.4.8
+dsh-packycode-api@1.4.9
 ```
 
-Choose the **official** install source, then click **Install**. `1.4.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.4.9` 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. Of the thirteen models, Claude runs t
 
 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.4.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.4.9`. 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.
 
@@ -185,10 +185,12 @@ By default DSH reviews with the conversation's own model. This plugin leaves the
 
 | Reviewer | Notes | Group needed |
 | --- | --- | --- |
-| jev-latest (default) | TypeSafe's decision classifier: about 0.4 s per review, billed by input only; a denial names only the risk level | `typesafe-officially` |
+| jev-1.14.0 (default) | TypeSafe's decision classifier: about 0.4 s per review, billed by input only; a denial names only the risk level | `typesafe-officially` |
 | DeepSeek Flash | About 2 s per review, and a denial says why | `deepseek-officially` / `deepseek-sale` |
 | Conversation model | Leave the review alone, as DSH does by default | — |
 
+A saved `jev-latest` still works and reviews with `jev-1.14.0`.
+
 Steps:
 
 1. Switch on “Auto authorization review” on DSH's Plugins page in the sidebar.
@@ -206,17 +208,17 @@ The card shows whether DSH's plugin is on, how many reviews this plugin answered
   - and it expects one `{"risk","decision","reason"?}` object back.
 - Every model request passes DSH's `llm/stream` waterfall. The plugin recognizes only this request there; conversation turns and everything else go on untouched.
 - **DeepSeek Flash** gets the same request, re-addressed to the PackyCode route; DSH still reads its answer.
-- **jev-latest** cannot write that object. The plugin passes the four sections and the official policy text to System One as the state and asks two questions: the risk, and whether you explicitly asked for this action.
+- **jev-1.14.0** cannot write that object. The plugin passes the four sections and the official policy text to System One as the state and asks two questions: the risk, and whether you explicitly asked for this action.
   - It allows a call when the probability of "low risk, or medium risk you asked for" is at least 0.6 and that of high risk is below 0.2.
-  - A denial says that jev-latest judged the call medium or high risk.
-  - jev-latest has a small context, so a long history is cut starting from the oldest entries; your instructions are kept first.
-- What is reviewed, the rules, and what an allow or a denial does all stay DSH's. DSH refuses a call whose review failed (for example, no key reaches jev-latest), and the plugin keeps that.
+  - A denial says that jev-1.14.0 judged the call medium or high risk.
+  - jev-1.14.0 has a small context, so a long history is cut starting from the oldest entries; your instructions are kept first.
+- What is reviewed, the rules, and what an allow or a denial does all stay DSH's. DSH refuses a call whose review failed (for example, no key reaches jev-1.14.0), and the plugin keeps that.
 - Measured on 37 scenarios with the official request format and the official parser: both reviewers matched all 35 scenarios that have a clear answer.
-  - jev-latest's median was 0.35 s, DeepSeek Flash's 2.3 s.
+  - jev-1.14.0's median was 0.35 s, DeepSeek Flash's 2.3 s.
 - If a later DSH changes the review request:
   - a request the plugin no longer recognizes goes on untouched, reviewed by the conversation model;
-  - a format jev-latest cannot read fails that review, which shows in the card's counts.
-- The description under Auto review in the menu says the same model reviews; that is DSH's text. With jev-latest or DeepSeek Flash chosen, that model reviews.
+  - a format jev-1.14.0 cannot read fails that review, which shows in the card's counts.
+- The description under Auto review in the menu says the same model reviews; that is DSH's text. With jev-1.14.0 or DeepSeek Flash chosen, that model reviews.
 
 </details>
 
@@ -241,7 +243,7 @@ The card shows whether DSH's plugin is on, how many reviews this plugin answered
 
 A model in the list does not mean the current token group allows it. When changing groups, do not drop the group that serves the model you still want.
 
-`jev-latest` (TypeSafe Jev) is not in the model picker: it is a decision model that answers classification questions and cannot hold a conversation, so it only serves [Auto review](#auto-review). The plugin calls `/v1/systemone` host-side; it needs a key in the `typesafe-officially` group, and each key's Jev entry under Accounts and keys shows whether it can.
+`jev-1.14.0` (TypeSafe Jev) is not in the model picker: it is a decision model that answers classification questions and cannot hold a conversation, so it only serves [Auto review](#auto-review). PackyCode lists it by version and no longer offers the `jev-latest` alias, so the plugin sends `jev-1.14.0` itself. It calls `/v1/systemone` host-side and needs a key in the `typesafe-officially` group; each key's Jev entry under Accounts and keys shows whether it can.
 
 Of the thirteen models in the current catalog, all but DeepSeek V4 Pro declare text and image input. DeepSeek Flash follows the [official vision guide](https://api-docs.deepseek.com/guides/vision/); images are read through DSH's attachment service and sent with the Responses request. DeepSeek V4 Pro takes text only, per DeepSeek's [models and pricing page](https://api-docs.deepseek.com/quick_start/pricing/): DSH does not let you attach an image to it, and an image already in the session (say, one switched over from Flash) is sent as a one-line "image omitted" note. PackyCode's gateway does not refuse an image sent to V4 Pro; it drops it.
 
@@ -280,9 +282,9 @@ DeepSeek Flash uses the gateway's Responses endpoint (`/api/pricing` lists `open
 
 ## Update and uninstall
 
-> **Upgrading from 1.3.2 or earlier:** install `dsh-packycode-api@1.4.8` on the Plugins page instead of clicking **Update plugin** in the old settings card. The old button bypasses pnpm's release-age policy: if the version it installs is less than 24 hours old, the profile refuses every other plugin install until that version is 24 hours old. After the install and a restart, the button is the fixed one, and later updates can use it.
+> **Upgrading from 1.3.2 or earlier:** install `dsh-packycode-api@1.4.9` on the Plugins page instead of clicking **Update plugin** in the old settings card. The old button bypasses pnpm's release-age policy: if the version it installs is less than 24 hours old, the profile refuses every other plugin install until that version is 24 hours old. After the install and a restart, the button is the fixed one, and later updates can use it.
 
-**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. The install keeps pnpm's release-age policy instead of overriding it: by default pnpm installs the version at once and records it in the profile's `minimumReleaseAgeExclude`; under a stricter pnpm policy the button says when the update can run. The newer version is read from npm, while pnpm downloads it from the profile's own install source: right after a release that source (a regional mirror in particular) may not have it yet, and the button asks you to update again in a few minutes; when the source cannot be reached, it asks you to check the network or proxy. 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.4.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. The install keeps pnpm's release-age policy instead of overriding it: by default pnpm installs the version at once and records it in the profile's `minimumReleaseAgeExclude`; under a stricter pnpm policy the button says when the update can run. The newer version is read from npm, while pnpm downloads it from the profile's own install source: right after a release that source (a regional mirror in particular) may not have it yet, and the button asks you to update again in a few minutes; when the source cannot be reached, it asks you to check the network or proxy. 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.4.9`); 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.
 
@@ -298,7 +300,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.4.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.4.9`), 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

@@ -32,7 +32,7 @@
 | **Claude 按分组选通道** | `cc` 分组只接受官方客户端，这些 Key 的 Claude 会话由本机 Claude Code 自己完成：它用自己的系统提示词和工具做事，DSH 显示每次工具调用，并负责授权、计划审阅和提问；`cc-sale`、`cc-expensive`、`claude-officially` 等分组走插件内 HTTP，由 DSH 自己的 agent 执行 |
 | **网页搜索可走 PackyCode** | 可选：DSH 的 `web_search` 改用 PackyCode 搜索，后端在 DeepSeek 与 GPT 之间切换；可只对 PackyCode 模型生效 |
 | **图片生成与编辑** | 独立图片 Key，支持 GPT Image 2 / 2.6 Flare / 2.6 Sunburst、型号与质量设置、参考图编辑和 PNG 原图保存；已通过网关生图与编辑实测 |
-| **自动审查可换模型** | 开启 DSH 自带的「自动授权审查」后，权限菜单里的「自动审查」可改用 jev-latest 或 DeepSeek Flash 审查每次工具调用，审查规则和处理方式保持官方原样 |
+| **自动审查可换模型** | 开启 DSH 自带的「自动授权审查」后，权限菜单里的「自动审查」可改用 jev-1.14.0 或 DeepSeek Flash 审查每次工具调用，审查规则和处理方式保持官方原样 |
 | **凭据不离开本机** | Key 只存在 DSH 凭据文件里。浏览器只能看到备注、状态和余额，拿不到 Key |
 
 <img width="774" height="455" alt="截屏2026-10-15 10 34 28" src="https://github.com/user-attachments/assets/060c4192-00ea-40e6-9b85-bbec605b5c31" />
@@ -48,10 +48,10 @@
 打开桌面应用的**插件**页，点击**添加插件**，在**包名或地址**中填入**带版本号**的包名：
 
 ```text
-dsh-packycode-api@1.4.8
+dsh-packycode-api@1.4.9
 ```
 
-在**安装源**中选择**官方源**，然后点击**安装**。`1.4.8` 是写这份说明时的最新版，当前最新版本号以 [npm 页面](https://www.npmjs.com/package/dsh-packycode-api) 为准。
+在**安装源**中选择**官方源**，然后点击**安装**。`1.4.9` 是写这份说明时的最新版，当前最新版本号以 [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.4.8
 
 桌面应用的**插件**页可以看到已安装状态与版本，也可以在那里启用、停用或卸载。
 
-**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.4.8`。不要对 `desktop` 使用它 —— CLI 会直接拒绝（`profile "desktop" is managed exclusively by the Electron application`）。
+**仅用于非 desktop profile：** `dsh plugin --profile <name> add dsh-packycode-api@1.4.9`。不要对 `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 自带的包，插件看起来像没装，见「常见问题」。已经那样装过的话，先卸载再按上面的方式重装。
 
@@ -185,10 +185,12 @@ DSH 自带一个实验性插件「自动授权审查」，默认关闭。开启
 
 | 审查模型 | 说明 | 需要的分组 |
 | --- | --- | --- |
-| jev-latest（默认） | TypeSafe 的决策分类模型，一次约 0.4 秒，只按输入计费；拒绝时只给出风险等级 | `typesafe-officially` |
+| jev-1.14.0（默认） | TypeSafe 的决策分类模型，一次约 0.4 秒，只按输入计费；拒绝时只给出风险等级 | `typesafe-officially` |
 | DeepSeek Flash | 一次约 2 秒，拒绝时写明原因 | `deepseek-officially` / `deepseek-sale` |
 | 跟随对话模型 | 不接管，按官方默认审查 | — |
 
+以前保存的 `jev-latest` 仍然有效，会按 `jev-1.14.0` 审查。
+
 使用步骤：
 
 1. 在 DSH 左侧「插件」页开启「自动授权审查」。
@@ -206,17 +208,17 @@ DSH 自带一个实验性插件「自动授权审查」，默认关闭。开启
   - 要求返回一个 `{"risk","decision","reason"?}` 对象。
 - 所有模型请求都经过 DSH 的 `llm/stream` 流水线。本插件在这里只认这一种请求，对话等其它请求原样放过。
 - **DeepSeek Flash**：同一个请求原样改发到 PackyCode 线路，结果仍由官方解析。
-- **jev-latest**：它写不出 JSON。插件把四段内容和官方规则原文作为 System One 的 state，问两个问题：风险等级，以及你是否明确要求过这个操作。
+- **jev-1.14.0**：它写不出 JSON。插件把四段内容和官方规则原文作为 System One 的 state，问两个问题：风险等级，以及你是否明确要求过这个操作。
   - 放行条件：「低风险，或中风险且你要求过」的概率不低于 0.6，且高风险概率低于 0.2。
-  - 拒绝时，理由里写明是 jev-latest 判定的中风险或高风险。
-  - jev-latest 上下文较小，过长的历史会从最旧的开始截掉，你的指令优先保留。
-- 看什么、按什么规则判、放行或拒绝后怎么处理，都由官方插件决定。官方对审查失败（例如 Key 调不了 jev-latest）的处理是拒绝这次调用，本插件不改变这一点。
+  - 拒绝时，理由里写明是 jev-1.14.0 判定的中风险或高风险。
+  - jev-1.14.0 上下文较小，过长的历史会从最旧的开始截掉，你的指令优先保留。
+- 看什么、按什么规则判、放行或拒绝后怎么处理，都由官方插件决定。官方对审查失败（例如 Key 调不了 jev-1.14.0）的处理是拒绝这次调用，本插件不改变这一点。
 - 实测方式：37 个场景，用官方的请求格式和官方解析器。其中 35 个有明确答案，两个模型都全部符合预期。
-  - jev-latest 中位 0.35 秒，DeepSeek Flash 中位 2.3 秒。
+  - jev-1.14.0 中位 0.35 秒，DeepSeek Flash 中位 2.3 秒。
 - 如果以后 DSH 改了审查请求的格式：
   - 认不出这个请求时，原样放过，由对话模型审查；
-  - jev-latest 读不懂新格式时，这次审查失败，卡片计数里会看到。
-- 菜单里「自动审查」的说明写的是「由同一模型审查」，那是 DSH 的文字。选了 jev-latest 或 DeepSeek Flash 时，实际由所选模型审查。
+  - jev-1.14.0 读不懂新格式时，这次审查失败，卡片计数里会看到。
+- 菜单里「自动审查」的说明写的是「由同一模型审查」，那是 DSH 的文字。选了 jev-1.14.0 或 DeepSeek Flash 时，实际由所选模型审查。
 
 </details>
 
@@ -241,7 +243,7 @@ DSH 自带一个实验性插件「自动授权审查」，默认关闭。开启
 
 列表里看得到模型，不代表当前令牌分组一定放行。换分组时不要把对应分组一起去掉。
 
-`jev-latest`（TypeSafe Jev）不在模型选择器里：它是只回答分类问题的决策模型，不能对话，只用于[自动审查](#自动审查)。插件在宿主侧直接调用 `/v1/systemone`，需要 Key 在 `typesafe-officially` 分组；「账户与 Key」里每个 Key 的「Jev」一项会显示能否使用。
+`jev-1.14.0`（TypeSafe Jev）不在模型选择器里：它是只回答分类问题的决策模型，不能对话，只用于[自动审查](#自动审查)。PackyCode 按版本号列出它，不再提供 `jev-latest` 别名，所以插件直接发送 `jev-1.14.0`。插件在宿主侧直接调用 `/v1/systemone`，需要 Key 在 `typesafe-officially` 分组；「账户与 Key」里每个 Key 的「Jev」一项会显示能否使用。
 
 当前目录的 13 个模型中，除 DeepSeek V4 Pro 外都声明了文字和图像输入。DeepSeek Flash 的识图能力按 [官方图像理解文档](https://api-docs.deepseek.com/zh-cn/guides/vision/) 配置；图片通过 DSH 附件服务读取，再随 Responses 请求发送。DeepSeek V4 Pro 按 [官方模型与价格页](https://api-docs.deepseek.com/zh-cn/quick_start/pricing/) 只收文字：DSH 不让给它附图，会话里已有的图片（比如从 Flash 切过来的会话）会换成一行「图片已省略」的说明再发送。PackyCode 网关收到发给 V4 Pro 的图片不报错，而是直接丢掉。
 
@@ -280,9 +282,9 @@ DeepSeek Flash 走网关的 Responses 接口（`/api/pricing` 列出 `openai-res
 
 ## 更新与卸载
 
-> **从 1.3.2 或更早版本升级：** 请在插件页填写 `dsh-packycode-api@1.4.8` 安装，不要点旧版设置页里的「更新插件」。旧按钮安装时会绕过 pnpm 的发布冷却期：装到的版本如果发布还不满 24 小时，这个 profile 在它满 24 小时之前就装不了其他插件。装好并重启后，按钮就换成了修好的版本，以后直接点即可。
+> **从 1.3.2 或更早版本升级：** 请在插件页填写 `dsh-packycode-api@1.4.9` 安装，不要点旧版设置页里的「更新插件」。旧按钮安装时会绕过 pnpm 的发布冷却期：装到的版本如果发布还不满 24 小时，这个 profile 在它满 24 小时之前就装不了其他插件。装好并重启后，按钮就换成了修好的版本，以后直接点即可。
 
-**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。安装遵守 pnpm 的发布冷却策略，不会绕过它：默认情况下 pnpm 会直接装上这个版本，并把它记进 profile 的 `minimumReleaseAgeExclude`；如果你给 pnpm 配了更严格的策略，按钮会提示什么时候可以更新。新版本号是从 npm 读到的，pnpm 却从 profile 配置的安装源下载：刚发布的版本，安装源（尤其是国内镜像）可能还没同步到，这时按钮会提示过几分钟再更新；连不上安装源时，会提示检查网络或代理。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.4.8`），否则装上的可能是发布满 24 小时的旧版。
+**更新：** 打开 **设置 → PackyCode**，有新版本时点「更新插件」。它会在当前 profile 目录里用 DSH 自带的 pnpm 安装精确版本，并读回 `package.json` 确认版本落地。安装遵守 pnpm 的发布冷却策略，不会绕过它：默认情况下 pnpm 会直接装上这个版本，并把它记进 profile 的 `minimumReleaseAgeExclude`；如果你给 pnpm 配了更严格的策略，按钮会提示什么时候可以更新。新版本号是从 npm 读到的，pnpm 却从 profile 配置的安装源下载：刚发布的版本，安装源（尤其是国内镜像）可能还没同步到，这时按钮会提示过几分钟再更新；连不上安装源时，会提示检查网络或代理。本地 `link:` 开发安装不会出现这个按钮。完成后完全退出并重新打开桌面应用。只刷新页面不会重载 Host。也可以在**插件**页重新安装，同样要填写带版本号的包名（例如 `dsh-packycode-api@1.4.9`），否则装上的可能是发布满 24 小时的旧版。
 
 **从本地路径安装切回官方源时，必须先卸载。** 「更新」是 `pnpm add`，它只重写包目录里的文件，不会删除更早一次本地路径安装留在包目录内的 `node_modules`；那份旧依赖会继续挡住 DSH 自带的包，插件行加载失败且看不出原因。「卸载」执行的是 `pnpm remove`，会删掉整个包目录，重装才是干净的。用 `node scripts/install-check.mjs` 可以确认当前 profile 是否处于这个状态。
 
@@ -298,7 +300,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.4.8`），然后完全退出并重新打开桌面应用。卸载执行的是 `pnpm remove`，会删掉整个包目录；直接重装或点「更新」只重写文件，不会清掉这份残留。也可以手动删掉上面那个 `node_modules` 再重启。
+修复：到**插件**页**卸载**本插件，再用带版本号的包名重新**安装**（例如 `dsh-packycode-api@1.4.9`），然后完全退出并重新打开桌面应用。卸载执行的是 `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

@@ -260,7 +260,7 @@ window.__ModuleLoader__.load({
 			reviewOfficialOff: "官方自动审查未开启",
 			reviewEnableHint: "还没有开启：在 DSH 左侧「插件」页找到「自动授权审查」并开启，然后在输入框的权限菜单里选「自动审查」。",
 			reviewModelTitle: "审查模型",
-			reviewModelJev: "jev-latest",
+			reviewModelJev: "jev-1.14.0",
 			reviewModelFlash: "DeepSeek Flash",
 			reviewModelSession: "跟随对话模型",
 			reviewModelJevHint: "TypeSafe 的决策分类模型，一次约 0.4 秒，只按输入计费；拒绝时只给出风险等级。需要 Key 的分组包含 typesafe-officially。",
@@ -272,7 +272,7 @@ window.__ModuleLoader__.load({
 			reviewOutcomeAllowed: "放行",
 			reviewOutcomeDenied: "拒绝",
 			reviewOutcomeFailed: "失败",
-			reviewMenuNote: "权限菜单里「自动审查」的说明写的是「由同一模型审查」，那是 DSH 的文字；选了 jev-latest 或 DeepSeek Flash 时，实际由所选模型审查。审查失败时，官方会拒绝这次调用，不会执行。"
+			reviewMenuNote: "权限菜单里「自动审查」的说明写的是「由同一模型审查」，那是 DSH 的文字；选了 jev-1.14.0 或 DeepSeek Flash 时，实际由所选模型审查。审查失败时，官方会拒绝这次调用，不会执行。"
 		};
 		const en = {
 			nav: "PackyCode",
@@ -499,7 +499,7 @@ window.__ModuleLoader__.load({
 			reviewOfficialOff: "Official auto review is off",
 			reviewEnableHint: "Not on yet: open DSH’s Plugins page in the sidebar, switch on “Auto authorization review”, then pick Auto review in the composer’s permission menu.",
 			reviewModelTitle: "Reviewer",
-			reviewModelJev: "jev-latest",
+			reviewModelJev: "jev-1.14.0",
 			reviewModelFlash: "DeepSeek Flash",
 			reviewModelSession: "Conversation model",
 			reviewModelJevHint: "TypeSafe’s decision classifier: about 0.4 s per review, billed by input only; a denial names only the risk level. Needs a key whose group includes typesafe-officially.",
@@ -511,7 +511,7 @@ window.__ModuleLoader__.load({
 			reviewOutcomeAllowed: "allowed",
 			reviewOutcomeDenied: "denied",
 			reviewOutcomeFailed: "failed",
-			reviewMenuNote: "The description under Auto review in the permission menu comes from DSH and says the same model reviews; with jev-latest or DeepSeek Flash chosen here, that model reviews. When a review fails, DSH refuses the call instead of running it."
+			reviewMenuNote: "The description under Auto review in the permission menu comes from DSH and says the same model reviews; with jev-1.14.0 or DeepSeek Flash chosen here, that model reviews. When a review fails, DSH refuses the call instead of running it."
 		};
 		//#endregion
 		//#region src/client-style.js
@@ -2059,7 +2059,7 @@ window.__ModuleLoader__.load({
 				"claude-sonnet-5-5",
 				"claude-haiku-5-5"
 			]],
-			["Jev", ["jev-latest"]]
+			["Jev", ["jev-1.14.0"]]
 		];
 		/**
 		* The one way this bundle talks to the host. The transport drops an
@@ -2745,12 +2745,12 @@ window.__ModuleLoader__.load({
 			failed: "reviewOutcomeFailed"
 		};
 		const REVIEW_LABELS = {
-			"jev-latest": "reviewModelJev",
+			"jev-1.14.0": "reviewModelJev",
 			"deepseek-flash": "reviewModelFlash",
 			session: "reviewModelSession"
 		};
 		const REVIEW_HINTS = {
-			"jev-latest": "reviewModelJevHint",
+			"jev-1.14.0": "reviewModelJevHint",
 			"deepseek-flash": "reviewModelFlashHint",
 			session: "reviewModelSessionHint"
 		};

package/lib/index.js

@@ -1392,11 +1392,13 @@ const PACKYCODE_MODEL_IDS = Object.freeze(PACKYCODE_MODELS.map((model) => model.
 * JSON state over the System One protocol, which PackyCode lists as the
 * `systemone` endpoint (`POST /v1/systemone`) in the `typesafe-officially`
 * group. Auto review asks it whether a tool call may run. The descriptor
-* follows pi-ai's own TypeSafe catalog entry (64K context, text only).
+* follows pi-ai's own TypeSafe catalog entry (64K context, text only), and
+* the id is the version PackyCode publishes, since it no longer lists a
+* `jev-latest` alias.
 */
 const PACKYCODE_CLASSIFIER_MODELS = Object.freeze([Object.freeze({
 	type: "classifier",
-	id: "jev-latest",
+	id: "jev-1.14.0",
 	name: "Jev",
 	api: "typesafe-system-one",
 	provider: PROVIDER,
@@ -1984,15 +1986,19 @@ function createKeyChooser({ ring, groups, onRotated, logger, waitMs = DEFAULT_GR
 * with an optional `reason` on a denial.
 *
 * - `deepseek-flash` gets the same request, addressed to the PackyCode route.
-* - `jev-latest`, TypeSafe's classifier, cannot write that object. The
+* - `jev-1.14.0`, TypeSafe's classifier, cannot write that object. The
 *   sections become a System One state with the official policy in it, Jev
 *   answers two typed questions, and the decision is written back as the
 *   official JSON object.
 *
 * @module dsh-packycode-api/auto-review
 */
-/** TypeSafe's decision model, reached through the `typesafe-officially` group. */
-const AUTO_REVIEW_JEV = "jev-latest";
+/**
+* TypeSafe's decision model, reached through the `typesafe-officially` group.
+* PackyCode publishes it under its exact version (the `jev-latest` alias was
+* retired), so this id moves with TypeSafe's releases.
+*/
+const AUTO_REVIEW_JEV = "jev-1.14.0";
 /** DeepSeek Flash on the PackyCode route. */
 const AUTO_REVIEW_FLASH = "deepseek-flash";
 /** Leave the official reviewer on the session's own model. */
@@ -2004,9 +2010,16 @@ const AUTO_REVIEW_MODELS = Object.freeze([
 	AUTO_REVIEW_SESSION
 ]);
 const DEFAULT_AUTO_REVIEW_MODEL = AUTO_REVIEW_JEV;
+/**
+* Reviewer values the settings once offered, mapped to what replaced them. A
+* saved preference still names them, so the Config keeps them as hidden
+* values (dropping them would fail the plugin's Config at load) and reading
+* the preference moves them to the successor.
+*/
+const RETIRED_AUTO_REVIEW_MODELS = Object.freeze({ "jev-latest": AUTO_REVIEW_JEV });
 /** Names for logs and the settings card; the card localizes the session choice. */
 const AUTO_REVIEW_MODEL_NAMES = Object.freeze({
-	[AUTO_REVIEW_JEV]: "jev-latest",
+	[AUTO_REVIEW_JEV]: AUTO_REVIEW_JEV,
 	[AUTO_REVIEW_FLASH]: "DeepSeek Flash",
 	[AUTO_REVIEW_SESSION]: "session model"
 });
@@ -2240,8 +2253,8 @@ function decideFromJev(body) {
 	const low = probability(shares?.low);
 	const medium = probability(shares?.medium);
 	const high = probability(shares?.high);
-	if (risk?.type !== "choice" || low === void 0 || medium === void 0 || high === void 0) throw new Error("PackyCode auto review: jev-latest returned no risk answer");
-	if (authorized === void 0) throw new Error("PackyCode auto review: jev-latest returned no authorization answer");
+	if (risk?.type !== "choice" || low === void 0 || medium === void 0 || high === void 0) throw new Error(`PackyCode auto review: ${AUTO_REVIEW_JEV} returned no risk answer`);
+	if (authorized === void 0) throw new Error(`PackyCode auto review: ${AUTO_REVIEW_JEV} returned no authorization answer`);
 	const allowProbability = low + medium * authorized;
 	const allowed = allowProbability >= .6 && high < .2;
 	const usage = record$4(body?.usage) && Number.isFinite(body.usage.input_tokens) ? {
@@ -2262,7 +2275,7 @@ function decideFromJev(body) {
 	return {
 		decision: "deny",
 		risk: blocking,
-		reason: blocking === "high" ? "jev-latest 判定为高风险操作（如外发凭据或敏感数据），需要你亲自决定" : "jev-latest 判定为中风险操作，且没有找到你对此操作的明确指示",
+		reason: blocking === "high" ? `${AUTO_REVIEW_JEV} 判定为高风险操作（如外发凭据或敏感数据），需要你亲自决定` : `${AUTO_REVIEW_JEV} 判定为中风险操作，且没有找到你对此操作的明确指示`,
 		...common
 	};
 }
@@ -2392,7 +2405,7 @@ function createJevReviewer({ ring, hosts, covers, onKeyFailure, fetchImpl = ambi
 			parsed = await response.json();
 		} catch (error) {
 			if (signal?.aborted === true) throw error;
-			throw new Error("PackyCode auto review got an unreadable answer from jev-latest", { cause: error });
+			throw new Error(`PackyCode auto review got an unreadable answer from ${AUTO_REVIEW_JEV}`, { cause: error });
 		}
 		if (record$4(parsed?.error)) return {
 			failure: mask$1(text$2(parsed.error.message) || JSON.stringify(parsed.error).slice(0, MAX_ERROR_DETAIL_CHARS$1), key),
@@ -2435,7 +2448,7 @@ function createJevReviewer({ ring, hosts, covers, onKeyFailure, fetchImpl = ambi
 			}
 			break;
 		}
-		if (uncovered) throw new Error(`PackyCode auto review: no stored API key's group covers jev-latest. Gateway said: ${lastFailure}`);
+		if (uncovered) throw new Error(`PackyCode auto review: no stored API key's group covers ${AUTO_REVIEW_JEV}. Gateway said: ${lastFailure}`);
 		throw new Error(`PackyCode auto review failed: ${lastFailure ?? "no detail"}`);
 	} });
 }
@@ -2545,7 +2558,7 @@ function connectSettings(settingsCtx, { ctx, Config, namespace, source, setSourc
 * request per tool call passes through DSH's `llm/stream` waterfall like
 * every model call; the listener recognizes it and answers it with the
 * reviewer chosen under Settings → PackyCode:
-* - `jev-latest`: over System One, written back as the official answer;
+* - `jev-1.14.0`: over System One, written back as the official answer;
 * - `deepseek-flash`: the same request, addressed to the PackyCode route;
 * - `session`: untouched, as without this plugin.
 * Every other request, conversation turns included, goes on unchanged. A
@@ -2558,9 +2571,10 @@ function connectSettings(settingsCtx, { ctx, Config, namespace, source, setSourc
 const DSH_AUTO_REVIEW_ROW = "auto-review";
 /** DSH's id of the 自动审查 permission preset. */
 const AUTO_PRESET = "auto";
-/** Normalize a stored preference; anything unknown reads as the default. */
+/** Normalize a stored preference; a retired reviewer reads as its successor, anything else unknown as the default. */
 function readAutoReviewChoice(value) {
-	const model = fieldValue(value?.autoReviewModel);
+	const saved = fieldValue(value?.autoReviewModel);
+	const model = Object.hasOwn(RETIRED_AUTO_REVIEW_MODELS, saved) ? RETIRED_AUTO_REVIEW_MODELS[saved] : saved;
 	return { model: AUTO_REVIEW_MODELS.includes(model) ? model : DEFAULT_AUTO_REVIEW_MODEL };
 }
 const errorText$1 = (error) => (error instanceof Error ? error.message : String(error)).slice(0, 300);
@@ -2618,7 +2632,7 @@ function createAutoReviewController({ jev, stream, readPreference, writePreferen
 			tool = sections.pendingAction.name;
 			const decision = await jev.review(options.system, sections, signal);
 			settle(decision.decision === "allow" ? "allowed" : "denied", {
-				model: "jev-latest",
+				model: AUTO_REVIEW_JEV,
 				tool,
 				ms: now() - started,
 				risk: decision.risk,
@@ -2632,7 +2646,7 @@ function createAutoReviewController({ jev, stream, readPreference, writePreferen
 			}
 			const message = errorText$1(error);
 			settle("failed", {
-				model: "jev-latest",
+				model: AUTO_REVIEW_JEV,
 				tool,
 				ms: now() - started,
 				error: message
@@ -9936,10 +9950,12 @@ const Config = z.object({
 	/** Path to the Claude Code CLI; empty means "the usual install places, then PATH". */
 	claudeCliPath: live(z.string().default("")),
 	/**
-	* Which model DSH's official 自动审查 reviews with: `jev-latest` or
-	* `deepseek-flash` through PackyCode, or `session` for its own default.
+	* Which model DSH's official 自动审查 reviews with: `jev-1.14.0` or
+	* `deepseek-flash` through PackyCode, or `session` for its own default. A
+	* retired reviewer value still parses as a hidden choice and reads as its
+	* successor, like a retired image engine.
 	*/
-	autoReviewModel: live(z.union([...AUTO_REVIEW_MODELS]).default(DEFAULT_AUTO_REVIEW_MODEL))
+	autoReviewModel: live(z.union([...AUTO_REVIEW_MODELS, ...Object.keys(RETIRED_AUTO_REVIEW_MODELS).map((id) => z.const(id).hidden())]).default(DEFAULT_AUTO_REVIEW_MODEL))
 });
 function apply(ctx, config) {
 	const ring = new PackyCodeKeyRing(ctx.credentials);
@@ -10391,4 +10407,4 @@ function apply(ctx, config) {
 	});
 }
 //#endregion
-export { AUTO_PRESET, AUTO_REVIEW_FLASH, AUTO_REVIEW_JEV, AUTO_REVIEW_MODELS, AUTO_REVIEW_MODEL_NAMES, AUTO_REVIEW_SESSION, AUTO_REVIEW_TIMEOUT_MS, CHANNEL, CLAUDE_INSTALL_COMMAND, CLAUDE_MIN_VERSION, CLAUDE_MISSING_MESSAGE, CLAUDE_NPM_LATEST_URL, CLAUDE_NPM_PACKAGE, CLAUDE_NPM_UPDATE_COMMAND, CLAUDE_PERMISSION_MODES, CLAUDE_SELF_UPDATE_COMMAND, CLI_ONLY_GROUPS, CLI_PROJECT_DIR_NAME, CLI_SESSION_IDLE_MS, Config, DEFAULT_API_HOST, DEFAULT_AUTO_REVIEW_MODEL, DEFAULT_CLAUDE_CONFIG_DIR, DEFAULT_IMAGE_MODEL, DEFAULT_SEARCH_BACKEND, DEFAULT_STATUS_HOST, DIAGNOSTICS_FORMAT, DIAGNOSTICS_LIMITS, DISPLAY_NAME, DSH_AUTO_REVIEW_ROW, HTTP_CLAUDE_GROUPS, IMAGE_MODELS, IMAGE_MODEL_IDS, IMAGE_QUALITIES, IMAGE_TIMEOUT_MS, IMAGE_TOOL_NAME, JEV_ALLOW_THRESHOLD, JEV_HIGH_RISK_LIMIT, JEV_LIMITS, JEV_QUESTIONS, LEGACY_STATUS_HOSTS, MAX_IMAGE_BYTES, MAX_LIVE_CLI_SESSIONS, MIRROR_TOOL, PACKYCODE_AUTO_SEARCH_PROVIDER_ID, PACKYCODE_CLASSIFIER_MODELS, PACKYCODE_COVERED_MODEL_IDS, PACKYCODE_MODELS, PACKYCODE_MODEL_IDS, PACKYCODE_SEARCH_PROVIDER_ID, PLAN_TOOL, PLUGIN_ID, PROVIDER, PackyCodeKeyRing, RETIRED_IMAGE_MODELS, SEARCH_BACKENDS, SEARCH_BACKEND_MODELS, SEARCH_MODES, SETTINGS_NAMESPACE, TEST_MESSAGE_POLICY_CODE, answerChunks, answersFor, apply, approvalReason, assertApiKey, baseUrlOf, buildCliArgs, buildCliEnvironment, buildSearchRequest, buildTranscript, catalogCoverage, classifyCliOutdated, classifyCliUnavailable, classifyClientPolicy, classifyGatewayFailure, classifyTestMessagePolicy, classifyUpstreamServerError, claudeBinaryCandidates, claudePermissionMode, claudeTransportFor, cliErrorMessage, compactionSummary, createAutoReviewController, createBalanceReader, createClaudeAgentBridge, createClaudeCliManager, createClaudeCliTransport, createClaudeLatestReader, createClaudeToolNames, createDiagnostics, createGroupReader, createImageController, createJevReviewer, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decideFromJev, decodeImagePng, describeRequest, dshSystemText, explainCliClientPolicyFailure, explainCliOutdated, explainCliUnavailable, explainClientPolicyFailure, explainNpmFailure, explainTestMessagePolicyFailure, failureChunk, guardKeyRotation, inject, isClaudeCliOutdated, isNpmClaudeInstall, isOfficialReviewRequest, jevState, locateClaudeBinary, locateNpm, messageFingerprint, name, normalizeFailureMessage, normalizeHost, officialAnswer, orderKeysFor, parseClaudeVersion, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, planAnswer, planContinuation, pngDimensions, presentClaudeCall, presentClaudeResult, questionPrompt, questionsFor, readAutoReviewChoice, readHiddenModels, readImagePreference, readReviewSections, readSearchChoice, refusalMessage, resolveSpawnCommand, responseFingerprint, sessionUuid, splitAtLastAnswer, startClaudeCliSession, statusHostOrder, summarizeSessionEvents, textResponse, titlePrompt, toCliHistory, toolResultText, validateImageOptions };
+export { AUTO_PRESET, AUTO_REVIEW_FLASH, AUTO_REVIEW_JEV, AUTO_REVIEW_MODELS, AUTO_REVIEW_MODEL_NAMES, AUTO_REVIEW_SESSION, AUTO_REVIEW_TIMEOUT_MS, CHANNEL, CLAUDE_INSTALL_COMMAND, CLAUDE_MIN_VERSION, CLAUDE_MISSING_MESSAGE, CLAUDE_NPM_LATEST_URL, CLAUDE_NPM_PACKAGE, CLAUDE_NPM_UPDATE_COMMAND, CLAUDE_PERMISSION_MODES, CLAUDE_SELF_UPDATE_COMMAND, CLI_ONLY_GROUPS, CLI_PROJECT_DIR_NAME, CLI_SESSION_IDLE_MS, Config, DEFAULT_API_HOST, DEFAULT_AUTO_REVIEW_MODEL, DEFAULT_CLAUDE_CONFIG_DIR, DEFAULT_IMAGE_MODEL, DEFAULT_SEARCH_BACKEND, DEFAULT_STATUS_HOST, DIAGNOSTICS_FORMAT, DIAGNOSTICS_LIMITS, DISPLAY_NAME, DSH_AUTO_REVIEW_ROW, HTTP_CLAUDE_GROUPS, IMAGE_MODELS, IMAGE_MODEL_IDS, IMAGE_QUALITIES, IMAGE_TIMEOUT_MS, IMAGE_TOOL_NAME, JEV_ALLOW_THRESHOLD, JEV_HIGH_RISK_LIMIT, JEV_LIMITS, JEV_QUESTIONS, LEGACY_STATUS_HOSTS, MAX_IMAGE_BYTES, MAX_LIVE_CLI_SESSIONS, MIRROR_TOOL, PACKYCODE_AUTO_SEARCH_PROVIDER_ID, PACKYCODE_CLASSIFIER_MODELS, PACKYCODE_COVERED_MODEL_IDS, PACKYCODE_MODELS, PACKYCODE_MODEL_IDS, PACKYCODE_SEARCH_PROVIDER_ID, PLAN_TOOL, PLUGIN_ID, PROVIDER, PackyCodeKeyRing, RETIRED_AUTO_REVIEW_MODELS, RETIRED_IMAGE_MODELS, SEARCH_BACKENDS, SEARCH_BACKEND_MODELS, SEARCH_MODES, SETTINGS_NAMESPACE, TEST_MESSAGE_POLICY_CODE, answerChunks, answersFor, apply, approvalReason, assertApiKey, baseUrlOf, buildCliArgs, buildCliEnvironment, buildSearchRequest, buildTranscript, catalogCoverage, classifyCliOutdated, classifyCliUnavailable, classifyClientPolicy, classifyGatewayFailure, classifyTestMessagePolicy, classifyUpstreamServerError, claudeBinaryCandidates, claudePermissionMode, claudeTransportFor, cliErrorMessage, compactionSummary, createAutoReviewController, createBalanceReader, createClaudeAgentBridge, createClaudeCliManager, createClaudeCliTransport, createClaudeLatestReader, createClaudeToolNames, createDiagnostics, createGroupReader, createImageController, createJevReviewer, createKeyChooser, createModelSelectionController, createPackyCodeAutoSearchProvider, createPackyCodeImageClient, createPackyCodeImageTool, createPackyCodeProfile, createPackyCodeProvider, createPackyCodeRpc, createPackyCodeSearchProvider, createProfileSearchComposition, createRouteAdapter, createSearchComposition, createSearchController, decideFromJev, decodeImagePng, describeRequest, dshSystemText, explainCliClientPolicyFailure, explainCliOutdated, explainCliUnavailable, explainClientPolicyFailure, explainNpmFailure, explainTestMessagePolicyFailure, failureChunk, guardKeyRotation, inject, isClaudeCliOutdated, isNpmClaudeInstall, isOfficialReviewRequest, jevState, locateClaudeBinary, locateNpm, messageFingerprint, name, normalizeFailureMessage, normalizeHost, officialAnswer, orderKeysFor, parseClaudeVersion, parseMessagesSearchResponse, parsePricing, parseResponsesSearchResponse, parseSelectedGroups, parseTokenUsage, pickKeyForModel, planAnswer, planContinuation, pngDimensions, presentClaudeCall, presentClaudeResult, questionPrompt, questionsFor, readAutoReviewChoice, readHiddenModels, readImagePreference, readReviewSections, readSearchChoice, refusalMessage, resolveSpawnCommand, responseFingerprint, sessionUuid, splitAtLastAnswer, startClaudeCliSession, statusHostOrder, summarizeSessionEvents, textResponse, titlePrompt, toCliHistory, toolResultText, validateImageOptions };

package/package.json

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