dsh-connect-minimaxcode 0.6.7 → 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,47 @@ 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)
+
+
+- **The plan tier moved into the Plan box**: the tier and the day it ends used to be a row of their own below the two boxes, stretched into a band of empty space. The tier is now the Plan box's headline line, wearing **the balance's own big-number size and height** (20px), and the day it ends stays the small text it was, on the right and on the tier's baseline; the box itself is named "Plan" rather than "Plan allowance".
+- **The grid has no hole any more**: the tier row no longer occupies a grid cell, so the check-in and the expiring grants now sit side by side in the second row and both columns are filled — the empty band under the left column and the hole at the bottom right are gone together. The Plan box did not grow by a row either: the tier line takes the place of the invisible number that used to hold the row height open.
+- The tier is still **the value the upstream sends** (`token_plan_tier`), not a fixed label: another plan shows its own name, and only an answer without that field falls back to "M Plan subscription".
+
+
+- **Fixed "Could not send it to the conversation": the session method was never bound.** Before this release the composer's **Generate an image** entry failed *every* time, reporting "Could not send it to the conversation; generate on the plugin page and download it instead." The plugin took `session.prompt` off the session object and then called it as a standalone function:
+
+  ```ts
+  const send = binding?.session?.prompt
+  return typeof send === 'function' ? { prompt: send } : undefined
+  ```
+
+  The host's own `Session.prompt` reaches the gateway **through `this.remote`**:
+
+  ```ts
+  result = await this.remote.session.prompt({ ... })
+  ```
+
+  Once the method is taken off the object, `this` no longer points at the session but at the `{ prompt: send }` wrapper, so `this.remote` is `undefined` and the call throws `undefined is not an object (evaluating 'this.remote.session')`. The method is now bound back to its session (`beginSubmission` for the same reason), and the picture actually goes out.
+
+  Worth noting: the draft channel in the same file has always written `create.bind(conversation)` — only the send path missed it. And because the send path is tried first, the draft path never runs, so that correct binding could not rescue it.
+
+- **A sent picture now shows up in the conversation.** The plugin used to invent its own `requestId` (`minimax-h3-${Date.now()}`) and hand it to `prompt()`: the model received the picture, but the **conversation showed no such message** — the host wants a local submission echo registered with `beginSubmission()` first, and the prompt to carry the identity that registration mints. The dock now does what the host's own composer does, and the picture arrives as part of that turn.
+
+- **A refusal is no longer read as a success.** A refused prompt resolves with `{ ok: false }` rather than throwing, and the plugin used to treat that as success and clear the note, leaving nothing on screen. The outcome is now read, and a refusal says so.
+
+- **Three new regression cases.** The mock in `tests/generate-dock.spec.ts` used to be an **arrow function that never reads `this`**, so whether the method was bound could not be observed — while the real host reads `this.remote`, and that is exactly the difference. The new cases make the mock read `this.remote` the way the host does, and pin three things: the call keeps the session as its receiver, the prompt carries the identity `beginSubmission` minted, and a refusal is reported. **Revert the fix and they fail at once.**
+
+
 ### 0.6.7 (2026-11-12)
 
 - **Merged PR [#5](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/5) by [azsora](https://github.com/azsora)**:
@@ -643,6 +721,8 @@ Fixing it yourself is even better — just open the PR. The format does not matt
 - **[azsora](https://github.com/azsora)** — found the plan's rate-limit endpoint in the desktop app's own traffic and wired the 5-hour and weekly usage windows into the credit pill and the plugin page ([#4](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/4)): the window length is derived from the response's own edges rather than hard-coded. It became 0.5.5.
 - **[qzz19970504](https://github.com/qzz19970504)** — found and fixed the wiring gap that made every image upload fail ([#3](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/3)): the catalog declared the `image` modality, but the adapter never connected the host's durable attachment service, so pi-ai refused image requests before they were sent. The fix became 0.5.3.
 - **[azsora](https://github.com/azsora)** — found that the official quota endpoint renamed its window field and inverted its meaning (the share used became the share remaining), closed the gap where a 200 with an unreadable shape never reached the older path, and reworked the pill detail and the page card into rounded sub-cards that say why there are no windows ([#5](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/5)). It became 0.6.7.
+- **[lulunick](https://github.com/lulunick)** — found the real reason the "Generate an image" entry failed **every** time: the plugin took `session.prompt` off the session object and called it as a standalone function, so `this` pointed at the wrapper instead of at the session — and the host's own `Session.prompt` reaches the gateway through `this.remote`, which made the call throw `undefined is not an object`. With the methods bound back to their session the picture actually goes out; he also added the local submission echo the host asks for (`beginSubmission()` — the plugin used to invent its own `requestId`, so the model received the picture and the conversation showed nothing) and reports a refusal honestly (the host resolves with `{ ok: false }` rather than throwing). The test's mock now reads `this.remote` the way the host does, which is what makes all three observable ([#7](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/7)). It became 0.6.8.
+- **[azsora](https://github.com/azsora)** — moved the plan tier into the Plan box as its headline line, at the balance box's own big-number size, named the box "Plan", and left no hole in the grid ([#6](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/6)). It became 0.6.8.
 - Plugin author: **[JeffTsuiCUG](https://github.com/JeffTsuiCUG)**
 
 ## Acknowledgements

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,47 @@ 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）
+
+
+- **套餐档位移进 Plan 框**：档位与到期日原本是卡片网格里独立的一行，横在两个框下面，被拉伸成一片空白。现在档位成为 Plan 框的标题行，**字号与高度和余额框的大数字完全一致**（20px），到期日仍是原来的小字、靠右基线对齐；Plan 框的名字由「Plan 额度」简化为「Plan」。
+- **网格不再留洞**：档位行不再占一个网格单元，「每日签到」与「到期批次」因此并排落到第二行，两列都填满 —— 之前左列下方那条空白与右下角的空格子一并消失。Plan 框内的高度也一行不多：档位行顶替的正是原先用来对齐行高的那个隐藏占位。
+- 档位本身仍是**上游给的值**（`token_plan_tier`），不是写死的标签：别的套餐会显示它自己的名字；只有上游没返回该字段时，才回落到「M Plan 订阅」。
+
+
+- **修复「无法发送到对话」：会话方法没有绑定 `this`**。这一版之前，输入框里的「生成图片」**必然**失败，提示「无法发送到对话，请到插件页生成后下载」。原因在插件把 `session.prompt` 从会话对象上摘下来之后，以独立函数的方式调用：
+
+  ```ts
+  const send = binding?.session?.prompt
+  return typeof send === 'function' ? { prompt: send } : undefined
+  ```
+
+  宿主自己的 `Session.prompt` 是**通过 `this.remote` 走到网关**的：
+
+  ```ts
+  result = await this.remote.session.prompt({ ... })
+  ```
+
+  方法一旦被摘下来，`this` 就不再指向会话，而是指向外面那个 `{ prompt: send }` 包装对象，于是 `this.remote` 是 `undefined`，调用抛出 `undefined is not an object (evaluating 'this.remote.session')`。现在方法被绑回会话对象（`beginSubmission` 同理），图片就能真正发出去了。
+
+  顺带一提：同一个文件里的草稿通道**一直**写着 `create.bind(conversation)`，只是发送通道漏了 —— 而发送通道优先，草稿通道根本走不到，所以那个正确的绑定救不了场。
+
+- **发图现在会出现在对话里**。此前插件自己编了一个 `requestId`（`minimax-h3-${Date.now()}`）交给 `prompt()`：模型能收到图片，但**对话里不显示这条消息** —— 宿主要求先用 `beginSubmission()` 注册一次本地回执、再用它给出的身份发送。现在照宿主输入框的做法走，图片作为这一轮消息的一部分出现。
+
+- **不再把失败当成功**。`prompt()` 被拒绝时返回的是 `{ ok: false }` 而不是抛异常，插件此前会把它当成功、把提示条清空，于是屏幕上什么都不剩。现在会读出结果，拒绝时如实说「无法发送到对话」。
+
+- **新增回归测试（3 个用例）**。此前 `tests/generate-dock.spec.ts` 的 mock 是个**不读 `this`** 的箭头函数，因此方法有没有绑定根本测不出来 —— 真实宿主要读 `this.remote`，差别正在于此。这次的新用例让 mock 像宿主一样读 `this.remote`，三条断言分别钉住：调用带着会话当接收者、发送的是 `beginSubmission` 给出的身份、宿主拒绝时如实提示。**把这三条用例里的修复撤掉，它们会立刻失败。**
+
+
 ### 0.6.7（2026-11-12）
 
 - **并入 PR [#5](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/5)（作者 [azsora](https://github.com/azsora)）**：
@@ -656,6 +734,8 @@ dsh plugin --profile desktop add dsh-qoder-connect
 - **[azsora](https://github.com/azsora)** —— 从桌面 App 的实际调用里找出了套餐的**限额窗口接口**，并把 5 小时与每周两个窗口的用量接进了积分胶囊与插件页卡片（[#4](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/4)）：窗口时长从响应自身的起止字段推导，不写死。该功能成为 0.5.5。
 - **[qzz19970504](https://github.com/qzz19970504)** —— 定位并修复了「发图必然失败」的接线缺口（[#3](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/3)）：模型目录声明了 `image` 模态，但适配器没有把宿主的持久化附件服务接上，导致带图请求被 pi-ai 在发出前拒掉。该修复成为 0.5.3。
 - **[azsora](https://github.com/azsora)** —— 找出官方额度接口改名并反转语义（「已用百分比」→「剩余百分比」）这件事，补上了「200 但形状读不懂时也要回落旧路径」的缺口，并把积分胶囊与插件页卡片重排为圆角分栏、让「为什么没有窗口」逐项有说法（[#5](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/5)）。该合并成为 0.6.7。
+- **[lulunick](https://github.com/lulunick)** —— 找到了「生成图片**必然**失败」的真正原因：插件把 `session.prompt` 从会话对象上摘下来后以独立函数调用，`this` 因此指向了包装对象而不是会话，宿主自己的 `Session.prompt` 正是通过 `this.remote` 走到网关的，于是抛 `undefined is not an object`。方法被绑回会话后图片才真正发得出去；顺带补上了宿主要求的 `beginSubmission()` 本地回执（此前插件自己编 `requestId`，模型收到了图片但对话里不显示），以及被拒绝时（返回 `{ ok: false }` 而非抛异常）的如实提示。他同时把测试里的 mock 改成像宿主一样读 `this.remote`，让这三点钉得住（[#7](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/7)）。该修复成为 0.6.8。
+- **[azsora](https://github.com/azsora)** —— 把套餐档位移进 Plan 框当标题行，字号与余额框的大数字一致，Plan 框改名为「Plan」，网格也不再留洞（[#6](https://github.com/JeffTsuiCUG/dsh-connect-minimaxcode/pull/6)）。该重排成为 0.6.8。
 - 插件作者：**[JeffTsuiCUG](https://github.com/JeffTsuiCUG)**
 
 ## 致谢

package/lib/client.js

@@ -50,7 +50,7 @@
         expiringAmount: '{amount} 积分',
         nextExpiry: '最近到期日',
         creditsBox: '积分',
-        planTitle: 'Plan 额度',
+        planTitle: 'Plan',
         usageTitle: '本机用量',
         usageTotal: '累计',
         lots: '到期批次',
@@ -136,7 +136,7 @@
         expiringAmount: '{amount} credits',
         nextExpiry: 'Next expiry',
         creditsBox: 'Credits',
-        planTitle: 'Plan allowance',
+        planTitle: 'Plan',
         usageTitle: 'Local usage',
         usageTotal: 'Total',
         lots: 'Expiring grants',
@@ -440,6 +440,11 @@
              * it nothing: the rolling windows it does not have are already
              * explained by the notice beside them. What this adds is for the
              * accounts that do hold one — the tier's name and the day it ends.
+             *
+             * It heads the plan box rather than standing on its own below it: the
+             * tier is the plan's headline fact, so it wears the balance's own big
+             * number size. The day it ends is a detail beside the tier, and keeps
+             * the row size.
              */
             function planLine(t, plan) {
                 if (plan === undefined || !plan.active)
@@ -448,7 +453,7 @@
                 const expiry = plan.expiresAtMs === undefined
                     ? null
                     : t('planExpires', { date: day(plan.expiresAtMs) });
-                return h('div', { style: rowStyle, 'data-minimax-plan': true }, h('span', null, tier), h('span', null, expiry ?? ''));
+                return h('div', { style: planHeadStyle, 'data-minimax-plan': true }, h('span', null, tier), h('span', { style: planExpiryStyle }, expiry ?? ''));
             }
             /** The pill itself; the gate decides whether it is drawn at all. */
             function CreditPill(props) {
@@ -612,14 +617,32 @@
                  * `binding(id).session.prompt(content, mode, signal, requestId)` is
                  * what the composer calls when the person presses send, so a picture
                  * sent this way is a normal turn.
+                 *
+                 * The method is taken off the session object, so it has to be bound to
+                 * that object before it is called. `prompt` reaches the gateway
+                 * through `this.remote`, and an unbound call runs with `this` pointing
+                 * at the wrapper below instead of at the session — which throws
+                 * `undefined is not an object (evaluating 'this.remote.session')` and
+                 * leaves the dock reporting that it cannot send the picture.
                  */
                 const sessionFace = () => {
                     const id = sessionId();
                     if (id === undefined)
                         return undefined;
                     const binding = clientContext?.sessions?.binding?.(id);
-                    const send = binding?.session?.prompt;
-                    return typeof send === 'function' ? { prompt: send } : undefined;
+                    const session = binding?.session;
+                    const send = session?.prompt;
+                    if (typeof send !== 'function')
+                        return undefined;
+                    // `beginSubmission` is taken off the session for the same reason: it
+                    // is a method of the session and must keep its receiver.
+                    const begin = session?.beginSubmission;
+                    return {
+                        prompt: send.bind(session),
+                        ...(typeof begin === 'function'
+                            ? { beginSubmission: begin.bind(session) }
+                            : {}),
+                    };
                 };
                 /**
                  * The conversation's own draft channel.
@@ -692,7 +715,24 @@
                                     : t('generateNoBinding'));
                         }
                         if (face !== undefined) {
-                            await face.prompt([part, { type: 'text', text }], 'queue', undefined, `minimax-h3-${Date.now()}`);
+                            // The host registers a local submission echo before it prompts,
+                            // and the identity that registration mints is the one the prompt
+                            // must carry — that is how the sent picture shows up as this
+                            // turn's message. A made-up identity reaches the model but leaves
+                            // no echo, so the conversation would not show what was sent.
+                            const submission = face.beginSubmission?.({
+                                mode: 'queue',
+                                text,
+                                attachments: [],
+                            });
+                            const result = await face.prompt([part, { type: 'text', text }], 'queue', undefined, submission?.requestId);
+                            // A refused prompt resolves with `{ ok: false }` rather than
+                            // throwing, so the outcome has to be read: either way the picture
+                            // did not arrive.
+                            if (result === undefined || result.ok !== true) {
+                                setNote(t('generateSendFailed'));
+                                return;
+                            }
                             setPrompt('');
                             setOpen(false);
                             // The picture's own arrival is the feedback: it is in the
@@ -1020,6 +1060,9 @@
                 // account's usage history across both.
                 const lots = [...(credits_.upcoming ?? [])].sort((a, b) => a.expireAtMs - b.expireAtMs);
                 const windows = rateLimitRows(t, status?.rateLimit);
+                // The tier and the day it ends, for an account that holds one. It
+                // heads the plan box rather than standing on its own below it.
+                const planHead = planLine(t, status?.plan);
                 const profileLines = usageProfileRows(t, status?.usageProfile);
                 const updated = credits_.updatedAtMs !== undefined
                     ? t('updated', { time: new Date(credits_.updatedAtMs).toLocaleTimeString() })
@@ -1027,18 +1070,18 @@
                 const loginLine = login?.state === 'signed-in'
                     ? (login.source === 'plugin' ? t('loginPlugin') : t('loginDesktop'))
                     : undefined;
-                return h('div', { style: pageStyle, 'data-minimax-page': true }, h('div', { style: cardStyle, 'data-minimax-credits-card': true }, h('div', { style: cardHeadStyle }, h('span', { style: cardTitleStyle }, t('title')), h('span', { style: mutedStyle }, [loginLine, updated].filter(line => line !== undefined).join(' · '))), h('div', { style: gridStyle }, h('div', { style: boxStyle }, h('div', { style: boxTitleStyle }, t('creditsBox')), h('div', { style: bigNumberStyle }, credits(credits_.total, 2)), row(t('free'), credits(credits_.free, 3)), row(t('purchased'), credits(credits_.purchased, 3)), ...expiryRows(t, credits_).slice(0, 1)), h('div', { style: boxStyle, 'data-minimax-rate-limit': true }, h('div', { style: boxTitleStyle }, t('planTitle')), ...(windows.length > 0
-                    ? [
-                        // The invisible number keeps the windows lined up with
-                        // the balance box's rows, which sit below its own big
-                        // number. With no windows to align, it is only noise.
-                        h('div', { style: { ...bigNumberStyle, visibility: 'hidden' }, 'aria-hidden': 'true' }, '—'),
-                        ...windows,
-                    ]
-                    : [rateLimitFallback(t, status?.rateLimit)])), 
-                // The tier and the day it ends, for an account that holds one.
-                // An account without a plan has nothing to say here.
-                planLine(t, status?.plan), signinBlock(t, signin, refresh), h('div', { style: boxStyle }, h('div', { style: boxTitleStyle }, t('lots')), 
+                return h('div', { style: pageStyle, 'data-minimax-page': true }, h('div', { style: cardStyle, 'data-minimax-credits-card': true }, h('div', { style: cardHeadStyle }, h('span', { style: cardTitleStyle }, t('title')), h('span', { style: mutedStyle }, [loginLine, updated].filter(line => line !== undefined).join(' · '))), h('div', { style: gridStyle }, h('div', { style: boxStyle }, h('div', { style: boxTitleStyle }, t('creditsBox')), h('div', { style: bigNumberStyle }, credits(credits_.total, 2)), row(t('free'), credits(credits_.free, 3)), row(t('purchased'), credits(credits_.purchased, 3)), ...expiryRows(t, credits_).slice(0, 1)), h('div', { style: boxStyle, 'data-minimax-rate-limit': true }, h('div', { style: boxTitleStyle }, t('planTitle')), 
+                // The tier heads the box, wearing the balance's own big number
+                // size. An account without a plan has no headline to show, and
+                // the invisible number keeps the windows lined up with the
+                // balance box's rows instead.
+                ...(planHead !== null
+                    ? [planHead]
+                    : windows.length > 0
+                        ? [h('div', { style: { ...bigNumberStyle, visibility: 'hidden' }, 'aria-hidden': 'true' }, '—')]
+                        : []), ...(windows.length > 0
+                    ? windows
+                    : [rateLimitFallback(t, status?.rateLimit)])), signinBlock(t, signin, refresh), h('div', { style: boxStyle }, h('div', { style: boxTitleStyle }, t('lots')), 
                 // The upstream already caps the list at the five soonest lots
                 // with credits left; the sort only keeps that promise honest.
                 ...(lots.length === 0
@@ -1177,6 +1220,17 @@
             };
             const cardTitleStyle = { fontWeight: 600 };
             const bigNumberStyle = { fontSize: '20px', fontWeight: 600, marginBottom: '2px' };
+            // The plan's headline line: the tier wears the balance's own big number
+            // size, so the two boxes' headline lines are the same height, and the
+            // day it ends stays at the row size beside it.
+            const planHeadStyle = {
+                ...bigNumberStyle,
+                display: 'flex',
+                justifyContent: 'space-between',
+                alignItems: 'baseline',
+                gap: '16px',
+            };
+            const planExpiryStyle = { fontSize: '13px', fontWeight: 400, lineHeight: '1.6' };
             const mutedStyle = { opacity: 0.7, fontSize: '12px' };
             const actionButtonStyle = {
                 appearance: 'none',

package/package.json

@@ -2,20 +2,20 @@
   "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.7",
+  "version": "0.6.9",
   "author": "JeffTsuiCUG",
   "contributors": [
     {
       "name": "JeffTsuiCUG",
       "url": "https://github.com/JeffTsuiCUG"
     },
-    {
-      "name": "eghrhegpe",
-      "url": "https://github.com/eghrhegpe"
+    {
+      "name": "eghrhegpe",
+      "url": "https://github.com/eghrhegpe"
     },
-    {
-      "name": "qzz19970504",
-      "url": "https://github.com/qzz19970504"
+    {
+      "name": "qzz19970504",
+      "url": "https://github.com/qzz19970504"
     },
     {
       "name": "azsora",
@@ -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"
   },