dsh-opencode-go 0.1.6 → 0.1.8

package/README.en.md

@@ -0,0 +1,130 @@
+# dsh-opencode-go
+
+[中文](README.md)
+
+Use OpenCode Go subscription models in [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness), with streaming replies, tool calls, and image input.
+
+The plugin automatically adds the session headers required by OpenCode Go, reads the gateway model catalog, and displays subscription usage. There is no need to configure model protocols, modalities, context windows, or maximum output tokens manually.
+
+## Features
+
+- **Session headers**: Every request includes the Harness User-Agent and `x-opencode-session`. A session keeps the same ID to maximize cache hits.
+- **Streaming and history**: Supports streaming output, tool calls, and history replay through pi-ai.
+- **Image input**: Supports models that advertise image capability in the catalog.
+- **Model capacity overrides**: Override the context window and maximum output per model, with blank values inheriting the online catalog.
+- **Prompt and caching**: The plugin does not add hidden system prompts; the session ID is used for gateway routing.
+
+## Installation and usage
+
+Supported DSH versions: `0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, `0.1.6-alpha.2`, and `0.1.7-alpha.1`.
+
+### Install from DSH (recommended)
+
+1. Open the **Plugins** page in DSH and click **Add plugin** in the top-right corner.
+2. Enter `dsh-opencode-go` and click **Install**.
+3. If prompted after installation, click **Enable now**.
+
+![Add, install, and enable dsh-opencode-go from DSH (Chinese UI)](docs/assets/install-via-dsh.gif)
+
+Then open **Settings → OpenCode Go**, enter and save your API key, and select an OpenCode Go model in a conversation.
+
+If your DSH version does not have an **Add plugin** entry, use the command-line method below.
+
+### Command-line installation (alternative)
+
+```sh
+dsh plugin --profile web add dsh-opencode-go@0.1.8
+```
+
+Start or restart `dsh web`, then:
+
+1. Open **Settings → OpenCode Go**.
+2. Enter and save your OpenCode Go API key.
+3. Select an OpenCode Go model from the conversation model picker.
+
+### Headless
+
+Install the plugin into the Headless profile:
+
+```sh
+dsh plugin --profile headless add dsh-opencode-go@0.1.8
+```
+
+Save the following as `headless.patch.yml` to select a default model:
+
+```yaml
+- id: agent-default-model
+  config:
+    provider: opencode-go
+    model: deepseek-v4.1-flash
+```
+
+Read the API key in Bash or Zsh, then run a task:
+
+```sh
+read -s OPENCODE_API_KEY
+export OPENCODE_API_KEY
+dsh --profile headless --patch ./headless.patch.yml "Hello"
+```
+
+The model ID must be available in the current gateway catalog. Web and Headless use separate profiles, so install the plugin in each profile you use.
+
+To build from source and install a local package:
+
+```sh
+npm ci --legacy-peer-deps
+npm pack
+dsh plugin --profile web add ./dsh-opencode-go-0.1.8.tgz
+```
+
+The development dependencies include real test packages from multiple DSH generations, so installation requires `--legacy-peer-deps`. For Headless, replace `web` with `headless`.
+
+## Updating the plugin
+
+Update the plugin in the Web profile to the latest npm version:
+
+```sh
+dsh plugin --profile web update dsh-opencode-go --latest
+```
+
+Restart `dsh web` and refresh the browser afterwards. For Headless, replace `web` with `headless`; if both profiles have the plugin installed, update each one separately.
+
+## Subscription usage display
+
+![OpenCode Go usage display](image.png)
+
+## FAQ
+
+### The `opencode-go` route is already in use
+
+Only one adapter in a profile can provide the `opencode-go` route. If another plugin or a generic pi-ai configuration already connects OpenCode Go, disable that configuration first. Other providers can continue to run.
+
+### An expected model is missing
+
+Confirm that the plugin is enabled and an API key is configured, then refresh the model list in Settings. Each model-list read requests the gateway's `/models` endpoint and synchronizes the OpenCode Go configuration from [models.dev](https://models.dev/api.json). Protocol support, context length, output limit, and image capability come from the online configuration, so new models do not require a release of this plugin or pi-ai.
+
+Models that are present in the gateway and have an entry using Anthropic Messages, OpenAI Chat Completions, or OpenAI Responses become available on the next list read or refresh. Refresh bypasses the existing catalog cache; a direct request for a previously unseen model also triggers an immediate resynchronization. The Settings page shows the complete discovery result.
+
+A gateway model ID with no usable protocol or capability configuration is shown in Settings with a configuration-unavailable diagnostic and is kept out of the conversation picker, so one unconfigured model cannot block the rest of the list. Direct requests report the reason. Refresh after the upstream configuration is corrected. A model ID alone is not enough to reliably infer its transport; new protocols or protocol-specific exceptions may still require adapter changes.
+
+A reasoning-capable model without adjustable reasoning levels (for example, `union-alpha`) remains selectable and usable; it simply has no reasoning-strength control.
+
+If the online configuration is temporarily unavailable, the plugin prefers a configuration fetched successfully earlier in the process and falls back to pi-ai's built-in metadata. If the gateway catalog is unavailable, existing requests can use the last catalog; a Settings refresh reports the failure instead of presenting stale data as current. `refreshMinutes` controls the cache lifetime for ongoing model requests, but does not prevent an explicit model-list read from fetching fresh data.
+
+## Uninstall
+
+Remove the plugin from the relevant profile and restart the application:
+
+```sh
+dsh plugin --profile web remove dsh-opencode-go
+# or
+dsh plugin --profile headless remove dsh-opencode-go
+```
+
+## Feedback
+
+Please open an issue for bugs or feature requests.
+
+## License
+
+[MIT](LICENSE)

package/README.md

@@ -1,40 +1,54 @@
 # dsh-opencode-go
 
-在 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 中使用 OpenCode Go 订阅模型，支持流式回复、工具调用、图片输入和 Web 设置页。
+[English](README.en.md)
 
-插件自动添加 OpenCode Go 所需的会话请求头，并从网关获取可用模型目录，显示套餐剩余额度。通过 DSH 插件命令安装，无需修改 DSH 源码。
+功能：让你在 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) 中完美使用 OpenCode Go 订阅模型，支持流式回复、工具调用和图片输入。
 
-无需任何设置，一key开始
+插件会自动添加 OpenCode Go 所需的会话请求头、读取网关模型目录，并显示订阅用量，无需给模型配置协议、模态、上下文长度、最大输出token
 
+## 功能说明
+
+- **会话请求头**：每次请求包含 Harness User-Agent 和 `x-opencode-session`。同一会话保持相同 ID，最佳缓存命中率。
+- **流式与历史**：支持流式输出、工具调用及历史回放，协议请求由 pi-ai 执行。
+- **图片输入**：支持目录中声明图片能力的模型。
+- **模型容量覆盖**：可按模型覆盖上下文窗口和最大输出，空值继承在线目录。
+- **提示与缓存**：插件不增加隐藏系统提示；会话 ID 用于网关路由。
 
 ## 安装与使用
 
-插件 `0.1.6` 兼容 DSH `0.1.5-rc.1`、`0.1.5-rc.2`、`0.1.6-alpha.1` 和 `0.1.6-alpha.2`，并通过这四个版本的真实图片和普通代码请求验证。使用 DSH `0.1.5` 的用户无需升级宿主。
+兼容清单：
+ `0.1.5-rc.1`、`0.1.5-rc.2`、`0.1.6-alpha.1`、`0.1.6-alpha.2` 和 `0.1.7-alpha.1`
+
+### 在 DSH 中安装（推荐）
+
+1. 打开 DSH 的 **插件** 页面，点击右上角 **添加插件**。
+2. 输入 `dsh-opencode-go`，点击 **安装**。
+3. 安装成功后，如果出现 **立即启用**，点击即可。
 
-插件 `0.1.6` 修复了 `0.1.5` 在旧版 DSH 上图片请求缺少 `maxPixels` 的问题（[Issue #2](https://github.com/Duskriver/dsh-opencode-go/issues/2)），同时保留新版宿主要求的图片目标宽高。
+![在 DSH 插件页添加、安装并启用 dsh-opencode-go](docs/assets/install-via-dsh.gif)
 
-npm 包通过 `engines.dsh` 明确声明宿主版本要求，并保留 DSH 组件的 peerDependencies。dshmarket 中本插件的安装来源也是该 npm 包，市场会将其安装到选定的 DSH profile。
+然后打开 **设置 → OpenCode Go**，填入 API Key 并保存，即可在会话中选择 OpenCode Go 模型。
 
-### Web
+若当前 DSH 没有「添加插件」入口，可使用下面的命令行方式。
+
+### 命令行安装（备选）
 
 ```sh
-dsh plugin --profile web add dsh-opencode-go
+dsh plugin --profile web add dsh-opencode-go@0.1.8
 ```
 
-安装后启动或重启 `dsh web`：
+安装后启动或重启 `dsh web`，然后：
 
 1. 打开 **设置 → OpenCode Go**。
 2. 填入 OpenCode Go API Key 并保存。
 3. 在会话的模型选择器中选择 OpenCode Go 模型。
 
-API Key 来自你的 OpenCode Go 订阅。安装插件不会自动更改默认模型。
-
-### Headless
+### 无头模式
 
 安装到 Headless profile：
 
 ```sh
-dsh plugin --profile headless add dsh-opencode-go
+dsh plugin --profile headless add dsh-opencode-go@0.1.8
 ```
 
 将以下内容保存为 `headless.patch.yml`，选择默认模型：
@@ -56,58 +70,32 @@ dsh --profile headless --patch ./headless.patch.yml "你好"
 
 模型 ID 须在当前网关目录中可用。Web 和 Headless 使用各自的 profile，需要分别安装插件。
 
-## 升级插件
-
-更新 Web profile 中的插件到 npm 最新版本：
+如需从源码构建并安装本地包：
 
 ```sh
-dsh plugin --profile web update dsh-opencode-go --latest
+npm ci --legacy-peer-deps
+npm pack
+dsh plugin --profile web add ./dsh-opencode-go-0.1.8.tgz
 ```
 
-完成后重启 `dsh web` 并刷新浏览器。Headless 用户将 `web` 换成 `headless`；如果两个 profile 都安装了插件，需要分别升级。
+开发依赖包含多代 DSH 的真实测试包，安装时需要 `--legacy-peer-deps`。Headless 用户将 `web` 换成 `headless`。
 
-如果此前安装的是本地目录或 `.tgz` 文件，用以下命令切换到 npm 最新版：
+## 升级插件
+
+更新 Web profile 中的插件到 npm 最新版本：
 
 ```sh
-dsh plugin --profile web add dsh-opencode-go@latest
+dsh plugin --profile web update dsh-opencode-go --latest
 ```
 
-升级插件无需卸载，也无需重新填写 API Key。模型目录会自动同步，正常新增模型不需要再次升级插件。
+完成后重启 `dsh web` 并刷新浏览器。Headless 用户将 `web` 换成 `headless`；如果两个 profile 都安装了插件，需要分别升级。
 
 ## 订阅用量显示
 
-![alt text](image.png)
-
-## 配置
-
-Web 用户可直接在 **设置 → OpenCode Go** 中修改配置。启用开关立即生效；
+![OpenCode Go usage display](image.png)
 
 ## 常见问题
 
-### DSH 0.1.5 安装插件后无法启动
-
-插件 `0.1.0`–`0.1.4` 使用了 DSH `0.1.6` 新增的图片接口，在旧版 DSH 上可能出现 `IMAGE_OFFLOAD_REQUIRED_CODE` 导出不存在的启动错误。升级插件到 `0.1.5` 或更新版本后重启即可：
-
-```sh
-dsh plugin --profile web add dsh-opencode-go@0.1.6
-```
-
-Headless 用户将 `web` 换成 `headless`。修复保留了两版宿主的图片处理方式：DSH `0.1.5` 在请求超过图片预算时将最旧图片转成占位文本，DSH `0.1.6` 继续由宿主记录并处理图片卸载。
-
-### 新版本是否必须等待一天才能安装
-
-npm 本身没有统一的 24 小时安装等待期。DSH 插件命令底层使用 pnpm；pnpm 11 起默认设置 `minimumReleaseAge: 1440`，按包名或 `latest` 安装、升级时可能继续选中发布满一天的旧版本。默认的非严格策略允许上面显式指定 `@0.1.6` 的安装；如果 profile 显式配置了严格的发布时间限制，则仍会被阻止。
-
-需要立即安装该修复时，可在对应 profile 的 `pnpm-workspace.yaml`（默认位于 `~/.dsh/profiles/web/`）中，将此版本合并到已有的例外列表，再运行上面的安装命令：
-
-```yaml
-minimumReleaseAgeExclude:
-  - dsh-opencode-go@0.1.6
-```
-
-保留文件中的其他设置和已有例外。此项仅豁免本插件的 `0.1.6`，不改变其他依赖的等待策略。参见 [pnpm 发布时间限制文档](https://pnpm.io/settings/dependency-resolution#minimumreleaseage)。市场目录、兼容性缓存或 npm 镜像也可能晚于官方 registry 更新；页面仍显示旧版本不代表新版尚未发布。
-
-
 ### 提示 `opencode-go` 路由已被占用
 
 同一 profile 中只能有一个适配器提供 `opencode-go` 路由。如果已经通过其他插件或通用 pi-ai 配置接入 OpenCode Go，请先停用那一项配置。其他提供方可以继续使用。
@@ -124,13 +112,6 @@ minimumReleaseAgeExclude:
 
 在线配置暂时不可达时，优先复用本次运行中成功获取的配置，以 pi-ai 内置配置作为备用。网关目录不可达时，已有请求可以使用上次目录；设置页刷新会显示失败，避免把旧目录误认为最新结果。`refreshMinutes` 只控制已有模型请求的缓存时长，不阻止主动读取列表获取新模型。
 
-## 功能说明
-
-- **会话请求头**：每次请求包含 Harness User-Agent 和 `x-opencode-session`。同一会话保持相同 ID，无会话 ID 的请求使用独立随机值。
-- **流式与历史**：支持流式输出、工具调用及历史回放，协议请求由 pi-ai 执行。
-- **图片输入**：支持目录中声明图片能力的模型，需要 DSH attachment 服务。
-- **提示与缓存**：插件不增加隐藏系统提示；会话 ID 用于网关路由；
-
 ## 卸载
 
 从对应 profile 移除插件，再重启应用：
@@ -141,11 +122,9 @@ dsh plugin --profile web remove dsh-opencode-go
 dsh plugin --profile headless remove dsh-opencode-go
 ```
 
-
-
 ## 反馈
 
-遇到bug或有功能建议请提issue
+遇到 bug 或有功能建议请提 issue。
 
 ## 许可证
 

package/docs/verification.md

@@ -1,5 +1,52 @@
 # Verification
 
+## Release 0.1.8 (2026-09-22)
+
+Host/client type checks, the build, and all **181 tests in 16 files** pass on macOS / Node.js 24.14.1. Coverage includes the five supported host versions, deprecated-model visibility, model remote injection, and CSS composition in the distributed client. The upstream UI primitives packages still emit missing-source-map warnings; all assertions pass. This release also synchronizes the English README with the simplified Chinese guide and updates installation examples to 0.1.8.
+
+## Model settings layout and deprecated visibility (2026-09-22)
+
+The settings page uses the selected list/detail layout, real gateway membership, models.dev release dates and deprecation flags, and a default-off `showDeprecatedModels` switch. Deprecated models stay configurable in settings; only conversation picker membership is filtered. Existing conversations can still call a hidden model that the gateway serves. Models found only in metadata or saved overrides are not displayed. Before any successful gateway response, a network failure does not advertise built-in models.
+
+Host/client type checks, the build, and all **181 tests in 16 files** passed. Added checks cover lifecycle date boundaries and ordering, gateway removals, deprecation during metadata outages, real model RPC serialization, immediate visibility changes and picker notifications on legacy settings and the 0.1.7 profile service, and failed toggle writes without discarding other edits. All five published host targets pass the compatibility fixture. Model and usage endpoints share one package contribution so 0.1.7's registry retains both.
+
+The actual React settings component was also rendered in a separate local preview with public live API data. Preview settings remain in memory, and credentials are not read or changed. This is a component/browser check, not a manual five-version host UI matrix. No paid completion or publication was performed.
+
+## Per-model capacities on five hosts (2026-09-22)
+
+PR #3's capacity editor is integrated on main commit `b093842`, preserving both legacy settings and the `0.1.7` profile configuration bridge. Each operation applies its captured overrides to original catalog metadata. The catalog cache remains available during outages, discovery shows the original reference values, and configured output caps also constrain explicit request budgets. Null model entries or fields explicitly restore catalog values over inherited configuration.
+
+The built Host artifact passes the existing compatibility fixture with real published LLM/attachment packages for all five targets:
+
+| DSH target | Capacities, output caps, hot update and reset | Text, image resizing and history checks |
+| --- | --- | --- |
+| 0.1.5-rc.1 | Pass | Pass |
+| 0.1.5-rc.2 | Pass | Pass |
+| 0.1.6-alpha.1 | Pass | Pass |
+| 0.1.6-alpha.2 | Pass | Pass |
+| 0.1.7-alpha.1 | Pass | Pass |
+
+The `0.1.7` fixture uses its actual Loader and settings service to edit and reset capacities without replacing the plugin fiber. Legacy settings tests verify null overrides of inherited capacities. Regressions also cover catalog references, metadata outages, concurrent configuration changes, and explicit output caps across Chat Completions, Responses and Anthropic Messages. Client tests cover Save/Discard, reset followed by another edit, customized counts, and offline reset; the distributed client mounts against both UI primitive generations.
+
+Validation: Host/Client type checks, all **175 tests in 15 files**, build and `npm pack` pass on macOS / Node.js 24.14.1. Dependencies install with `npm ci --legacy-peer-deps` using main's unchanged lock. The older host matrix selects matching LLM/attachment packages through resolution hooks, with other services from the development tree; the `0.1.7` host uses its separately pinned workspace. UI validation is automated component/factory testing, not a manual five-version browser or Desktop matrix. All completions use a loopback fixture and fake credentials; no paid generation or npm publication was performed.
+
+## DSH 0.1.7 compatibility (plugin 0.1.7)
+
+Verified on macOS / Node.js 24.14.1 against published DSH `0.1.7-alpha.1`, while retaining the four previously tested hosts (`0.1.5-rc.1`, `0.1.5-rc.2`, `0.1.6-alpha.1`, `0.1.6-alpha.2`). The independent npm workspace at `tests/hosts/v017` keeps the new Cordis/Loader and DSH service identities separate from the legacy test dependencies. Install development dependencies with `npm ci --legacy-peer-deps`; the aliases deliberately contain incompatible peer ranges from different host generations.
+
+The failures reproduced before their fixes were:
+
+- `engines.dsh` rejected `0.1.7-alpha.1`.
+- The real new settings service did not expose OpenCode Go because `installSection` was removed and the profile form requires volatile Config fields.
+- New `role: 'tool'` history was sent as user text, losing its tool-call identity; tool-result images were rejected.
+- The real Web settings page crashed with React error 130 because the host removed `IconChevronDownOutline14`.
+
+Validation: Host/Client type checks and all **151 tests in 14 files** pass. The fresh-process host matrix exercises the built artifact, real LLM/attachment implementations, text streaming, tool history, image resizing and offload limits. The modern fixture additionally exercises the real usage RPC gateway. The profile-settings fixture uses the real Loader and settings service with an in-memory editor, and verifies live updates without remounting, toggling the route, and invalid-URL rejection. The browser artifact test now renders the actual page against both published UI primitive generations; merely checking registration had missed the removed icon.
+
+An isolated npm consumer with the official `0.1.7-alpha.1` CLI passed `verify:installed` and `verify:headless` against a local fixture gateway. The final browser factory was also checked in that consumer's Web profile: the settings page renders, advanced fields are editable, saving `refreshMinutes: 30` and switching `enabled: false` persist in the real profile patch and survive a full page reload, with no new console errors. No real API key or paid model generation was used. Older custom settings may require the explicit migration described in README because the upstream importer does not map this plugin's legacy namespace to its bundle entry id.
+
+The verification history below describes earlier releases; their live-provider results do not imply live-provider testing of this release.
+
 Verified on macOS with Node.js 24.14.1 and npm-installed DSH 0.1.6-alpha.1. The plugin's dependencies came from npm, with no workspace aliases, symlinks into a checkout, or unpublished DSH exports.
 
 ## Local checks
@@ -125,3 +172,7 @@ All four requests returned HTTP 200 and `finish.kind: stop`. After inspecting ea
 | 0.1.6-alpha.2 | 8/8 passed | 4.759 s | 133 / 702 |
 
 Total: four additional live completion requests and 3,092 reported tokens, including reasoning output. No code corrections or retries were needed. This verifies ordinary text-only code generation and executable output; it does not exercise an agent's multi-turn tool-call workflow. Credential handling was identical to the live image checks above.
+
+The settings build was also loaded in the user's running local `0.1.7-alpha.1` Web profile. This exposed a missing `remote.opencodeGoModels` injection in the browser settings scope; both legacy and modern settings bindings now declare it, and the distributed-client regression checks exercise model loading under that injection requirement. After rebuilding and restarting the Host, the real settings page loaded 40 gateway models, including 3 recent releases and 8 deprecated entries, with the deprecated-model switch off. No completion request was sent during this check.
+
+Local Web layout checks also cover the settings panel's independent scroll body and reserved save/discard footer. The model panel now uses the settings container's available height and stacks at narrow container widths. At a 600×780 viewport, browser geometry confirmed no footer overlap or horizontal overflow and a visible action row. The client artifact test checks inherited disclosure styles because the CSS-module build previously omitted `composes` entries.