dsh-connect-minimaxcode 0.6.8 → 0.6.9

package/README.en.md

@@ -57,10 +57,47 @@ Either:
 1. **The MiniMax Code desktop app (China region) installed and signed in** — the plugin reuses its sign-in (the easy way)
 2. **Nothing installed** — press "Sign in to MiniMax Code" on the plugin page; the plugin starts an OAuth device code flow and you confirm with your own MiniMax account in a browser (this needs `account.minimax.cn` to be reachable)
 
-Plus DSH desktop (built-in core `>=0.2.1-rc.2 <0.3.0`, see `engines.dsh` in `package.json`; tested on `0.2.1-rc.2`) or the Web profile.
+Plus DSH desktop (built-in core `>=0.1.6-alpha.2 <0.3.0`, see `engines.dsh` in `package.json`; tested on `0.2.2-rc.1`) or the Web profile.
 
 > **Sending a picture needs the host's attachment service**: the plugin does not read images itself — the host's durable attachment service turns a stored reference into request bytes, and the plugin only connects the two. On a host without that service the plugin still loads and text still works; only image requests are refused (`pi-ai image input requires the durable attachment service`).
 
+## Compatibility: the oldest DSH this works on
+
+**The oldest supported DSH is `0.1.6-alpha.2`** — that is the range in `engines.dsh`. The plugin used to declare `0.2.1-rc.2`, which was a conservative floor rather than a technical one; this time the host packages' published history was searched, and the floor moved down to the version where each feature actually exists.
+
+The host publishes its own packages under **the same version numbers as the desktop** (DSH `0.2.2-rc.1` ships `0.2.2-rc.1` packages), so "which release first had this API" can be answered straight from npm. Every row below was read out of that version's published source:
+
+| Host capability | First version | What the plugin uses it for |
+| --- | --- | --- |
+| `llm.registerAdapter` | `0.0.1-rc.1` | registering the MiniMax Code provider |
+| `webServer.register` (`kind: 'exact'`) | `0.0.1-rc.1` | the status, action, generation and capability routes |
+| `attachments.saveImage` | `0.0.1-rc.1` | storing a generated picture as an attachment |
+| client `slots` / `sessions` services | `0.0.1-rc.3` | the credit pill and the composer tool row |
+| `conversation.input.left` slot | `0.0.1-rc.1` | where the pill and the generate entry sit |
+| `dsh.client.inject` / `immediately` | `0.0.1-rc.1` | loading the client half |
+| `session.beginSubmission` / `binding()` / `scope()` | `0.1.2-alpha.2` | the picture going out **and showing up in the conversation** |
+| `inputActions.addAttachments` / `conversation.createDrafts` | `0.1.3-alpha.2` | the picture going into the input box (the draft channel) |
+| **`plugins.bundle.config` slot** | **`0.1.6-alpha.2`** | **the plugin page (generation panel, check-in switch, the full bill)** |
+| **`cordis.patch` manifest patch** | **`0.1.6-alpha.2`** | **offering the provider in the model picker without changing the default** |
+
+**The last two rows are the real floor.** The plugin page and the manifest patch both begin at `0.1.6-alpha.2`; older hosts only have the plugin manager's own `settings.plugin.item` — a card inside the settings section, on a keyed slot — which is not a plugin page.
+
+### What an older host still gets
+
+The plugin is not useless on an older host; it gives up one thing at a time. That is also why the floor sits at `0.1.6-alpha.2` rather than lower: **the plugin page is the plugin's main surface** (the H3 generation panel, the check-in switch and the detailed balance all live there), and claiming support while it is missing would be a lie.
+
+| Host version | What still works | What is missing |
+| --- | --- | --- |
+| `>= 0.1.6-alpha.2` | everything | —— |
+| `0.1.3-alpha.2` – `0.1.6-alpha.1` | the models, the credit pill, the generate entry in the composer, a picture reaching the conversation | no plugin page (the generation panel and the check-in switch live there); the manifest patch has no effect, so the model must be picked by hand |
+| `0.1.2-alpha.2` – `0.1.3-alpha.1` | less again: the picture can still be sent straight through the session | no draft channel (`createDrafts` / `addAttachments` did not exist yet) |
+| `< 0.1.2-alpha.2` | the text models and the credit display | a picture reaches the model but **does not show in the conversation** (no local echo, `beginSubmission`) |
+
+A host that does not know a manifest field ignores it (the manifest is not validated strictly), so an old host does not refuse the plugin over `cordis.patch` — it merely has no effect.
+
+> This table was **read out of the published history of every host package on npm**, version by version — not estimated.
+>
+> **And it does not stop at an inference**: this repository's lockfile resolves the host packages to `0.1.6-alpha.2`, so every release compiles, builds and runs the whole suite **against that oldest host** — the floor is verified on every release, not concluded once. The method is written down in the repository: pull each host package at each version and look for the API in the source it shipped.
 ## Installation
 
 **Option 1: install from the Git repository** (recommended, gets the latest code)
@@ -384,6 +421,15 @@ The OAuth token is valid for about an hour and is refreshed automatically by the
 
 ## Changelog
 
+### 0.6.9 (2026-11-13)
+
+- **The oldest supported DSH moved from `0.2.1-rc.2` down to `0.1.6-alpha.2`.** The old floor was a conservative value, not a technical one. This release searched the host packages' published history version by version and, for every host capability the plugin uses, found the release it first appeared in.
+- **The host publishes its own packages under the same version numbers as the desktop** (DSH `0.2.2-rc.1` ships `0.2.2-rc.1` packages), so "which release first had this API" can be answered straight from npm — every row of the compatibility table was read out of the source that host package version actually shipped.
+- **Two things set the real floor**: the `plugins.bundle.config` slot the plugin page lives in, and the `cordis.patch` manifest patch that offers the provider in the model picker. Both begin at `0.1.6-alpha.2`. Older hosts only have the plugin manager's own `settings.plugin.item` — a card inside the settings section, on a keyed slot — which is not a plugin page.
+- **Older hosts are not useless, they give up one thing at a time** (the README has the full table): from `0.1.3-alpha.2` the models, the credit pill, the generate entry in the composer and a picture reaching the conversation all work, only the plugin page is missing; from `0.1.2-alpha.2` a picture reaches the conversation too, only the draft channel is missing. A host that does not know a manifest field ignores it (the manifest is not validated strictly), so an old host does not refuse the plugin over `cordis.patch` — it merely has no effect.
+- The peer dependency floors for the host packages moved to `>=0.1.6-alpha.2` as well, so an older host's own versions satisfy the range. **The lockfile resolves to `0.1.6-alpha.2`** — so every release compiles, builds and runs the whole suite against that oldest host, and the floor is verified on every release.
+- The README gained a "Compatibility: the oldest DSH this works on" section (in both languages), with the evidence table and the degradation ladder.
+
 ### 0.6.8 (2026-11-13)
 
 

package/README.md

@@ -57,10 +57,47 @@
 1. **已安装并登录 MiniMax Code 桌面 App（国内版）** —— 插件直接复用它的登录态（最省事）
 2. **什么都不装** —— 在插件页面点「登录 MiniMax Code」，插件发起 OAuth 设备码流，你在浏览器里用自己的 MiniMax 账号确认，插件拿到自己的登录态（需要能访问 `account.minimax.cn`）
 
-另外需要 DSH 桌面版（内置内核 `>=0.2.1-rc.2 <0.3.0`，见 `package.json` 的 `engines.dsh`；实测 `0.2.1-rc.2`）或 Web profile。
+另外需要 DSH 桌面版（内置内核 `>=0.1.6-alpha.2 <0.3.0`，见 `package.json` 的 `engines.dsh`；实测 `0.2.2-rc.1`）或 Web profile。
 
 > **发图需要宿主提供附件服务**：图片不是插件自己读的，而是由宿主的持久化附件服务读成请求字节，插件只负责把附件引用接上去。宿主没有附件服务时，插件照常加载、文本照常对话，只是发图会被拒绝（`pi-ai image input requires the durable attachment service`）。
 
+## 兼容性：最低支持哪个 DSH 版本
+
+**最低支持 DSH `0.1.6-alpha.2`**（`engines.dsh` 里写的就是这个区间）。这一版之前插件声明的是 `0.2.1-rc.2`，那是个保守的下限，不是技术上的；这次下探宿主各包的发布历史后，把下限一路降到了每个功能真正存在的那一版。
+
+宿主把它自己的各个包按**与桌面端相同的版本号**发布（DSH `0.2.2-rc.1` 里带的就是 `0.2.2-rc.1` 的包），所以「某个 API 最早出现在哪一版」可以直接对着 npm 上的宿主包查。下面这张表就是这么查出来的 —— 每一行都是宿主包那个版本号里的源码里**实际出现过**这个 API：
+
+| 宿主能力 | 最早版本 | 插件拿它做什么 |
+| --- | --- | --- |
+| `llm.registerAdapter` | `0.0.1-rc.1` | 注册 MiniMax Code 模型提供者 |
+| `webServer.register`（`kind: 'exact'`） | `0.0.1-rc.1` | 状态、动作、生成、自检四条路由 |
+| `attachments.saveImage` | `0.0.1-rc.1` | 把生成的图存成附件 |
+| 客户端 `slots` / `sessions` 服务 | `0.0.1-rc.3` | 积分胶囊与输入框工具行 |
+| `conversation.input.left` 插槽 | `0.0.1-rc.1` | 胶囊与「生成图片」入口的落位 |
+| `dsh.client.inject` / `immediately` | `0.0.1-rc.1` | 客户端半边能被加载 |
+| `session.beginSubmission` / `binding()` / `scope()` | `0.1.2-alpha.2` | 图片发出去**并在对话里显示** |
+| `inputActions.addAttachments` / `conversation.createDrafts` | `0.1.3-alpha.2` | 图片放进输入框（草稿通道） |
+| **`plugins.bundle.config` 插槽** | **`0.1.6-alpha.2`** | **插件页（生成面板、签到开关、完整账单）** |
+| **`cordis.patch` 清单补丁** | **`0.1.6-alpha.2`** | **把提供者加进模型选择器而不改默认模型** |
+
+**最后两行是真正的下限**：插件页与清单补丁都从 `0.1.6-alpha.2` 起才有，更早的宿主只有插件管理器自己的 `settings.plugin.item`（设置页里的一张卡片，keyed 插槽），不是插件页。
+
+### 更早的宿主会怎样
+
+插件在更早的宿主上并非完全不能用，只是逐项减少。这也是为什么下限定在 `0.1.6-alpha.2` 而不是更低：**插件页是插件的主界面**（H3 生成面板、签到开关、完整账单都在里面），缺了它而对外声称支持，是骗人。
+
+| 宿主版本 | 还能用什么 | 缺什么 |
+| --- | --- | --- |
+| `>= 0.1.6-alpha.2` | 全部功能 | —— |
+| `0.1.3-alpha.2` ～ `0.1.6-alpha.1` | 模型、积分胶囊、输入框里的生成入口、图片进对话 | 没有插件页（生成面板与签到开关在插件页上）；清单补丁不生效，需手动选模型 |
+| `0.1.2-alpha.2` ～ `0.1.3-alpha.1` | 再减：图片仍可经会话直接发出 | 草稿通道不可用（`createDrafts` / `addAttachments` 还没有） |
+| `< 0.1.2-alpha.2` | 文本模型与积分显示 | 图片发得出但**对话里不显示**（没有本地回执 `beginSubmission`） |
+
+宿主不认识的清单字段会被忽略（不是严格校验），所以老宿主不会因为 `cordis.patch` 而拒绝安装插件 —— 它只是不生效。
+
+> 这份表是**对着 npm 上宿主各包的发布历史逐版本查出来**的，不是估计的。
+>
+> **而且不只停在推断上**：本仓库的锁文件把宿主包解析到 `0.1.6-alpha.2`，因此每次发布的 CI 都会**对着这个最老的宿主**编译、构建并跑完全部用例 —— 下限是被每次发布验证着的，不是一次性的结论。查询方式见仓库里的说明：把每个宿主包的每个版本拉下来，看它发布出来的源码里有没有那个 API。
 ## 安装
 
 **方式一：从 Git 仓库安装**（推荐，拿到最新代码）
@@ -395,6 +432,15 @@ OAuth 令牌有效期约 1 小时，由客户端自动续期。插件**只在自
 
 ## 更新记录
 
+### 0.6.9（2026-11-13）
+
+- **最低支持的 DSH 版本从 `0.2.1-rc.2` 降到 `0.1.6-alpha.2`**。原来的下限是保守取值，不是技术上的。这一版把宿主各包的发布历史逐版本查了一遍，对每个插件用到的宿主能力，核出它最早出现在宿主包的哪个版本里。
+- **宿主把它自己的包按与桌面端相同的版本号发布**（DSH `0.2.2-rc.1` 里带的就是 `0.2.2-rc.1` 的包），因此「某个 API 最早在哪一版」可以直接对着 npm 查 —— 本次兼容性表里的每一行，都是宿主包该版本号发布出来的源码里**实际出现过**这个 API。
+- **真正的下限由两样东西决定**：插件页所在的 `plugins.bundle.config` 插槽，以及让提供者出现在模型选择器里的 `cordis.patch` 清单补丁 —— 两者都从 `0.1.6-alpha.2` 起才有。更早的宿主只有插件管理器自己的 `settings.plugin.item`（设置页里的一张卡片，keyed 插槽），不是插件页。
+- **更早的宿主并非不能用，只是逐项减少**（README 有完整表格）：`0.1.3-alpha.2` 起模型、积分胶囊、输入框里的生成入口、图片进对话都可用，只是没有插件页；`0.1.2-alpha.2` 起图片能发出并在对话里显示，只是没有草稿通道。宿主不认识的清单字段会被忽略（清单不是严格校验），所以老宿主不会因为 `cordis.patch` 拒绝安装插件 —— 只是它不生效。
+- 宿主包的 peer 依赖下限同步降到 `>=0.1.6-alpha.2`，使老宿主自带的版本能满足区间。**锁文件也解析到 `0.1.6-alpha.2`** —— 于是每次发布的 CI 都会对着这个最老的宿主编译、构建并跑完全部用例，下限是被每次发布验证着的。
+- README 新增「兼容性：最低支持哪个 DSH 版本」一节（中英文），含证据表与降级说明。
+
 ### 0.6.8（2026-11-13）
 
 

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-minimaxcode",
   "displayName": "DSH Connect MiniMax Code",
   "description": "把本机已登录的 MiniMax Code 桌面 App 模型接入 DeepSeek Harness：零配置、Anthropic Messages 兼容、动态模型目录，并显示积分余额与到期 — bring MiniMax Code desktop app models into DSH with a dynamic model catalog and a credit balance with expiry details.",
-  "version": "0.6.8",
+  "version": "0.6.9",
   "author": "JeffTsuiCUG",
   "contributors": [
     {
@@ -39,7 +39,7 @@
   "type": "module",
   "engines": {
     "node": "^22.19.0 || >=24.0.0",
-    "dsh": ">=0.2.1-rc.2 <0.3.0-0"
+    "dsh": ">=0.1.6-alpha.2 <0.3.0-0"
   },
   "icon": "./icon.svg",
   "main": "lib/index.js",
@@ -82,13 +82,13 @@
   ],
   "peerDependencies": {
     "@deepseek-ai/cordis": ">=4.0.4 <5.0.0",
-    "@deepseek-ai/dsh-atomic-write": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-attachment": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-home-paths": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-host-webserver": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-llm": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-llm-pi-ai": ">=0.1.7-rc.1 <0.3.0-0",
-    "@deepseek-ai/dsh-settings": ">=0.1.7-rc.1 <0.3.0-0",
+    "@deepseek-ai/dsh-atomic-write": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-attachment": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-home-paths": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-host-webserver": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-llm": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-llm-pi-ai": ">=0.1.6-alpha.2 <0.3.0-0",
+    "@deepseek-ai/dsh-settings": ">=0.1.6-alpha.2 <0.3.0-0",
     "@deepseek-ai/schemastery": ">=3.18.4 <4.0.0",
     "@earendil-works/pi-ai": ">=0.85.1"
   },