dsh-codex-connect 0.1.0-alpha.4.49 → 0.1.0-alpha.4.50

package/INSTALL.md

@@ -1,10 +1,10 @@
 # Installation Runbook for CLI Agents
 
-Published Alpha 4.47 is verified with the exact DSH `0.1.7-rc.1` model-runtime pairing and pi-ai `0.85.1`. Earlier DSH pairings retain their separately published plugin versions below.
+Published Alpha 4.49 is verified with the exact DSH `0.1.7-rc.1` model-runtime pairing and pi-ai `0.85.1`. Earlier DSH pairings retain their separately published plugin versions below.
 
 Install `dsh-codex-connect` into one requested DeepSeek Harness profile without changing its current default model, search route, global configuration, or OAuth state.
 
-Channel snapshot on 2026-09-24: npm `alpha` and `latest` both point to `0.1.0-alpha.4.47`. Use the exact-version command for the installed DSH version; moving npm tags are not compatibility guarantees.
+Channel snapshot on 2026-09-26: npm `alpha` points to `0.1.0-alpha.4.49`; `latest` remains `0.1.0-alpha.4.47`. Use the exact-version command for the installed DSH version; moving npm tags are not compatibility guarantees.
 
 ## Safety requirements
 
@@ -30,11 +30,17 @@ Check `dsh --version` before changing the requested profile. Use `dsh --help` to
 | `0.1.5-alpha.1` | `0.1.0-alpha.4.41` |
 | `0.1.5-rc.1` | `0.1.0-alpha.4.41` |
 | `0.1.5-rc.2` | `0.1.0-alpha.4.41` |
-| `0.1.7-rc.1` | `0.1.0-alpha.4.47` |
+| `0.1.7-rc.1` | `0.1.0-alpha.4.49` |
 
 If your exact DSH version is unknown or not listed, preserve the installed host, report that the combination is unverified, and verify it before making installation changes. A missing record does not prove incompatibility, and the catalog's latest verified DSH version is not the latest upstream release. Do not recommend upgrading or downgrading DSH merely to match a row. Investigate any specific failure and seek verification of the installed combination. Do not blindly install `dsh-codex-connect@alpha`: `alpha` is a moving tag, not a compatibility guarantee. Do not infer support for newer DSH versions from these rows.
 
-Alpha 4.47 requires one consistent DSH `0.1.7-rc.1` plugin API and pi-ai `0.85.1`; its direct runtime imports include `@deepseek-ai/schemastery` `3.18.4` and `@earendil-works/pi-ai` `0.85.1` so an isolated profile need not already provide them. Node.js remains `^22.19.0 || >=24.0.0`. It does not support the older DSH rows. Alpha 4.41 remains the choice for DSH `0.1.2-rc.1` with pi-ai `^0.84.2`, or `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` with pi-ai `0.85.1`. Mixed host versions and other DSH/pi-ai combinations remain unverified. Alpha 4.25 remains the verified choice for DSH `0.1.2-alpha.5`, Alpha 4.23 for DSH `0.1.2-alpha.2`, Alpha 4.21 for DSH `0.1.1-rc.2`, and Alpha 4.14 for DSH `0.1.0-rc.7`. Changing DSH is a separate operation requiring the user's explicit request; a plugin update request does not authorize it. The repository's `pnpm --silent run check:compatibility` remains a strict development/release dependency gate, not a recommendation to change a user's host.
+Alpha 4.49 requires one consistent DSH `0.1.7-rc.1` plugin API and pi-ai `0.85.1`; its direct runtime imports include `@deepseek-ai/schemastery` `3.18.4` and `@earendil-works/pi-ai` `0.85.1` so an isolated profile need not already provide them. Node.js remains `^22.19.0 || >=24.0.0`. It does not support the older DSH rows. Alpha 4.41 remains the choice for DSH `0.1.2-rc.1` with pi-ai `^0.84.2`, or `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` with pi-ai `0.85.1`. Mixed host versions and other DSH/pi-ai combinations remain unverified. Alpha 4.25 remains the verified choice for DSH `0.1.2-alpha.5`, Alpha 4.23 for DSH `0.1.2-alpha.2`, Alpha 4.21 for DSH `0.1.1-rc.2`, and Alpha 4.14 for DSH `0.1.0-rc.7`. Changing DSH is a separate operation requiring the user's explicit request; a plugin update request does not authorize it. The repository's `pnpm --silent run check:compatibility` remains a strict development/release dependency gate, not a recommendation to change a user's host.
+
+The Alpha 4.49 recommendation follows [exact-release main CI](https://github.com/franksong2702/dsh-codex-connect/actions/runs/36212638824) on Node 22/24, browser and keyless Windows checks, plus the stock DSH `0.1.7-rc.1` same-artifact installation matrix. It fixes both independently reproduced Alpha 4.48 image-editing defects: reuploaded copies could select historical originals, and safe actionable input errors were hidden. The three original reproduction tests pass; a separate ephemeral GPT-6 Astra process reviewed the correction's source without implementation history and found no blockers in that scope.
+
+The [original 4.49 publish run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/36212860716) successfully published npm but failed its bounded public-readback step. It was not rerun. The [recovery-only run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/36213209903) verified npm metadata and exact archive bytes against the original verified artifact, then created the [matching tag and prerelease](https://github.com/franksong2702/dsh-codex-connect/releases/tag/v0.1.0-alpha.4.49). npm exact version and `alpha` were independently read back as 4.49; `latest` remains 4.47. These checks do not claim new real-account image/selection acceptance, physical Windows/mobile behavior or pixel-perfect edits. Stock rc.1 keeps Task controls paused. The 4.48 package and tag remain unchanged and affected; select 4.49 for the corrected behavior.
+
+Historical Alpha 4.47 evidence:
 
 The Alpha 4.47 recommendation follows [exact-release main CI](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35994106350) on Node 22/24, browser and keyless Windows checks, plus the stock DSH `0.1.7-rc.1` same-artifact installation matrix. The [original publish run](https://github.com/franksong2702/dsh-codex-connect/actions/runs/35994578156) uploaded the verified package but failed during npm public readback; do not rerun publication. Recovery-only local verification matched the public npm archive byte-for-byte to the original artifact and created the [Git tag and prerelease](https://github.com/franksong2702/dsh-codex-connect/releases/tag/v0.1.0-alpha.4.47) without republishing. npm `alpha` and `latest` were independently read back as 4.47. These checks are not fresh real Chrome OAuth, live model/tool/image requests, or Windows application acceptance. Stock rc.1 keeps Task controls paused; migration of old Task grants across a Harness upgrade remains unverified.
 
@@ -79,10 +85,10 @@ Alpha 4.33 omits the `modelErrors` profile field required by RC model packages,
    dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.41
    ```
 
-   For the exact DSH `0.1.7-rc.1` pairing, use Alpha 4.47:
+   For the exact DSH `0.1.7-rc.1` pairing, use Alpha 4.49:
 
    ```sh
-   dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.47
+   dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.49
    ```
 
    For DSH `0.1.2-alpha.5`, use Alpha 4.25:
@@ -93,7 +99,7 @@ Alpha 4.33 omits the `modelErrors` profile field required by RC model packages,
 
    If npm is unavailable after the matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.21'` only for the DSH `0.1.1-rc.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.23'` only for the DSH `0.1.2-alpha.2` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.25'` only for the DSH `0.1.2-alpha.5` combination, `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.41'` only for the DSH `0.1.2-rc.1`, `0.1.5-alpha.1`, `0.1.5-rc.1`, and `0.1.5-rc.2` combinations, or `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.46'` only for DSH `0.1.7-rc.1`.
 
-   For the current DSH `0.1.7-rc.1` pairing, if npm is unavailable after the matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.47'`.
+   For the current DSH `0.1.7-rc.1` pairing, if npm is unavailable after the matching GitHub prerelease is created, use `dsh plugin --profile web add 'github:franksong2702/dsh-codex-connect#v0.1.0-alpha.4.49'`.
 
 3. Run `dsh web --help` once to compose the installed profile without starting the server. DSH `0.1.2-rc.1` prepares profile plugin dependency fallback during this step.
 4. Run `dsh --profile web --dump-config` and require exactly one `llm-openai-codex` row loading `dsh-codex-connect`.

package/README.i18n.yaml

@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   git hash-object README.md docs/README.zh.md
-README.md: 6758656bc0916de3460b0359eed96f32e1f65c72
-docs/README.zh.md: 380041f418a4420409a82adc93fe9ff119803663
+README.md: f3f28e552d752052e0ba8c9e032081a50d1bb259
+docs/README.zh.md: 48a2e1ec57cc7027927640968d629c503d2ed5f3

package/README.md

@@ -4,7 +4,7 @@
 
 English | [中文](docs/README.zh.md)
 
-Connect your ChatGPT subscription to DeepSeek Harness with OAuth, optional GPT Image generation, user-controlled defaults, Harness-native approvals, diagnostics, and reliable session recovery.
+Connect your ChatGPT subscription to DeepSeek Harness with OAuth, optional GPT Image generation and editing, user-controlled defaults, Harness-native approvals, diagnostics, and reliable session recovery.
 
 Community Alpha — not affiliated with or endorsed by OpenAI, ChatGPT, Codex, DeepSeek, or DeepSeek Harness.
 
@@ -16,19 +16,19 @@ This guide describes the published pairing below. Check `dsh --version` first an
 
 | Requirement | Verified pairing |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.47` |
+| Codex Connect | `0.1.0-alpha.4.49` |
 | DeepSeek Harness | `0.1.7-rc.1` |
 | Node.js | `^22.19.0 \|\| >=24.0.0` |
 | Account | ChatGPT OAuth with access to the requested Codex model; availability is decided by OpenAI |
 
-As of 2026-09-24, npm `alpha` and `latest` both point to 4.47. Use the exact version below for this DSH pairing; a moving npm tag is not a compatibility guarantee for other hosts.
+As of 2026-09-26, npm `alpha` points to 4.49 while `latest` remains 4.47; publishing this release did not promote `latest`. Use the exact version below for this DSH pairing; a moving npm tag is not a compatibility guarantee for other hosts.
 
 On stock DSH `0.1.7-rc.1`, ordinary Composer works, but Task controls remain paused: activation is rejected and fresh Sessions do not show them. Migration of earlier Task grants across a Harness upgrade is not verified. Older supported pairings and their task behavior are documented in [Installation and upgrades](INSTALL.md).
 
 ### 1. Install
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.47
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.49
 dsh web
 ```
 
@@ -79,7 +79,7 @@ All options below are off on a fresh installation. Edit them in **Settings → P
 | Codex Search | `enableSearch` | Selects Codex for the entire profile's search route; disabling restores the previously active route. |
 | Luna Reserve | `enableReserveFallback` | Uses the hidden Reserve route only when the backend explicitly authorizes it for the captured account; never changes global defaults or retries a generic `429`. |
 | Image viewing | `enableImageTool` | Adds `view_image` to vision-capable models for local files and validated public HTTP(S) images. |
-| GPT Image generation | `enableImageGeneration` | Prompt-only generation; availability, dimensions, and quota remain account- and service-controlled. |
+| GPT Image generation and editing | `enableImageGeneration` | Generate from a prompt or edit selected conversation images with ordered references. Availability, dimensions, and quota remain account- and service-controlled. |
 | Auto-review | `enableAutoReview` | Sends bounded approval context, tool arguments, working directory, and the planned action to `chatgpt.com`, with confirmation on first enablement. Failures return to human approval. |
 
 **Published experiment:** Alpha 4.35 includes Luna Reserve fallback, disabled by default. Real-account Reserve entry and recovery remain unverified; Alpha 4.34 does not include this feature.
@@ -88,6 +88,8 @@ With `enableReserveFallback: true`, the account UI and agent routing share one i
 
 Use the image generation capability included with your current GPT subscription. Successful images appear below the conversation answer without opening its processing details; the original tool card remains available there. Generated originals are stored separately from attachment previews; disabling the capability or uninstalling the plugin does not delete them. See [Configuration and recovery](docs/reference.md#search-and-image-tools) for storage and access rules.
 
+Alpha 4.49 fixes the re-uploaded-copy/original confusion and hidden safe failure reasons found in 4.48. Ambiguous inputs require an explicit selection rather than silently changing the target. The original package remains unchanged; use the exact 4.49 release.
+
 Auto-review operates after Harness policy requires approval; it does not bypass that policy. See [Auto-review behavior](docs/auto-review.md) before enabling it.
 
 ## FAQ and important limits

package/compatibility.json

@@ -5,11 +5,18 @@
   },
   "dshPluginApi": {
     "version": "0.1.7-rc.1",
-    "versions": ["0.1.7-rc.1"],
+    "versions": [
+      "0.1.7-rc.1",
+      "0.1.7-rc.2"
+    ],
     "packages": [
       "@deepseek-ai/dsh-agent",
       "@deepseek-ai/dsh-atomic-write",
       "@deepseek-ai/dsh-attachment",
+      "@deepseek-ai/dsh-client-ui-chat",
+      "@deepseek-ai/dsh-client-ui-layout",
+      "@deepseek-ai/dsh-client-ui-primitives",
+      "@deepseek-ai/dsh-client-ui-tool",
       "@deepseek-ai/dsh-compaction",
       "@deepseek-ai/dsh-home-paths",
       "@deepseek-ai/dsh-host-webserver",

package/docs/README.zh.md

@@ -4,7 +4,7 @@
 
 [English](../README.md) | 中文
 
-通过 OAuth 把你的 ChatGPT 订阅接入 DeepSeek Harness，并提供可选的 GPT Image 图片生成、由用户控制的默认设置、Harness 原生审批、诊断与可靠的会话恢复。
+通过 OAuth 把你的 ChatGPT 订阅接入 DeepSeek Harness，并提供可选的 GPT Image 图片生成与编辑、由用户控制的默认设置、Harness 原生审批、诊断与可靠的会话恢复。
 
 社区 Alpha 项目——与 OpenAI、ChatGPT、Codex、DeepSeek 或 DeepSeek Harness 不存在隶属关系，也未获得其背书。
 
@@ -16,19 +16,19 @@ Codex Connect 为标准 Harness agent loop 添加 `openai-codex` 模型提供方
 
 | 要求 | 已验证组合 |
 |---|---|
-| Codex Connect | `0.1.0-alpha.4.47` |
+| Codex Connect | `0.1.0-alpha.4.49` |
 | DeepSeek Harness | `0.1.7-rc.1` |
 | Node.js | `^22.19.0 \|\| >=24.0.0` |
 | 账户 | 通过 ChatGPT OAuth 使用所请求的 Codex 模型；可用性由 OpenAI 决定 |
 
-截至 2026-09-24，npm `alpha` 和 `latest` 均指向 4.47。安装此 DSH 组合请使用下方精确版本命令；会移动的 npm tag 不保证其他宿主版本的兼容性。
+截至 2026-09-26，npm `alpha` 指向 4.49，`latest` 仍为 4.47；本次发布没有提升 `latest`。安装此 DSH 组合请使用下方精确版本命令；会移动的 npm tag 不保证其他宿主版本的兼容性。
 
 在原版 DSH `0.1.7-rc.1` 上，普通 Composer 可用，但 Task 控件仍暂停：激活请求会被拒绝，新 Session 不显示这些控件。跨 Harness 升级迁移旧任务授权尚未验证。较旧组合及其任务行为见[安装与升级](../INSTALL.md)。
 
 ### 1. 安装
 
 ```sh
-dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.47
+dsh plugin --profile web add dsh-codex-connect@0.1.0-alpha.4.49
 dsh web
 ```
 
@@ -79,7 +79,7 @@ Alpha 4.40 还会在旧提供方目录缺失时补充 `gpt-6-sol` 和 `gpt-6-lun
 | Codex 搜索 | `enableSearch` | 将整个 profile 的搜索路由切换为 Codex；关闭后恢复之前的路由。 |
 | Luna Reserve | `enableReserveFallback` | 只在服务端为当前已固定账户明确授权时使用隐藏的 Reserve 路由；不修改全局默认模型，也不因普通 `429` 重试。 |
 | 图片查看 | `enableImageTool` | 为视觉模型添加 `view_image`，读取本地文件和经过校验的公网 HTTP(S) 图片。 |
-| GPT Image 图片生成 | `enableImageGeneration` | 只接受提示词；可用性、尺寸和额度仍由账户及服务端控制。 |
+| GPT Image 图片生成与编辑 | `enableImageGeneration` | 根据提示词生图，或编辑明确选定的会话图片并使用有顺序的参考图；可用性、尺寸和额度仍由账户及服务端控制。 |
 | 自动审查 | `enableAutoReview` | 将有界的审批上下文、工具参数、工作目录和待执行动作发送到 `chatgpt.com`，首次启用需要确认。失败时交还人工审批。 |
 
 **已发布的实验功能：** Alpha 4.35 包含 Luna Reserve 回退，仍默认关闭。真实账户进入 Reserve 及恢复普通模型的过程仍未验证；Alpha 4.34 不包含该功能。
@@ -88,6 +88,8 @@ Alpha 4.40 还会在旧提供方目录缺失时补充 `gpt-6-sol` 和 `gpt-6-lun
 
 使用你当前 GPT 订阅计划提供的图片生成能力。成功生成的图片会显示在对话回复下方，无需展开处理过程；原工具卡片仍保留在处理过程里。生成原文件与附件预览分开保存；关闭能力或卸载插件不会删除这些文件。存储和访问规则见[配置与恢复](reference.zh.md#搜索与图片工具)。
 
+Alpha 4.49 修复了 4.48 中重新上传的副本与历史原图混淆、以及安全失败原因未显示的问题。输入有歧义时要求明确选择，不会静默更换编辑对象。旧安装包保持不变，请使用精确的 4.49 版本。
+
 自动审查在 Harness 策略判定需要审批后执行，不会绕过该策略。启用前请阅读[自动审查行为](auto-review.zh.md)。
 
 ## 常见问题与重要限制

package/docs/agent-notes/issue-271-independent-review.md

@@ -0,0 +1,47 @@
+# Issue #271 independent source review — 2026-09-26
+
+Two separate ephemeral read-only Codex CLI processes used `gpt-6-astra`, receiving the exact source bundle and upstream declaration comparison, without implementation conversation history. They did not execute tests or perform live acceptance. The final source hashes in the machine-readable evidence still match the reviewed files.
+
+Final input SHA-256: `fc62714c31cab46943d41b4fb41b69cb7737b8af6740d970e5228b471ff5ac47`; report SHA-256: `39eb7ac3d99fcf39ae0d24f297984c3d933cf17f1116a604368a22d231d06646`.
+
+## Initial report — BLOCKED (preserved)
+
+**BLOCKED — 存在一项源码级混合版本校验缺口。** 此结论仅依据所给源码，不代表已确认 rc.2 的实际运行故障。
+
+1. **[P2] 扩大 peer 范围后，四个必需 UI peer 的 rc.1/rc.2 混装可以通过现有一致性检查。**
+
+   - `package.json:118–121` 将 `dsh-client-ui-chat`、`dsh-client-ui-layout`、`dsh-client-ui-primitives`、`dsh-client-ui-tool` 分别放宽为两个版本任选。
+   - 这四个包均不在 `compatibility.json:12–28` 和 `src/compatibility.ts:13–29` 的检查清单内。
+   - `scripts/check-compatibility.mjs:121–127` 只检查该清单的一致性；`src/capability-diagnostics.ts:119–131` 也只对该清单执行版本读取和混装判断。
+
+   **具体反例：** 清单中的 DSH 包全部为 rc.2、pi-ai 为 `0.85.1`，但 `dsh-client-ui-chat` 为 rc.1。在其他条件满足时，该组合满足新增的 peer 范围，版本检查仍可通过，capabilities 仍会报告 `supported`。补丁前，rc.2 清单包不满足精确 rc.1 peer 要求；补丁放宽后，原有检查遗漏成为两个受支持版本之间的放行缺口。
+
+   这证明的是**未强制要求完整、同版本的 host 集合**，并非证明该混装必然崩溃。应将这些必需 peer 纳入一致性检查，并覆盖混装及元数据缺失场景。可选的 `dsh-commands` 应单独处理其缺席语义。
+
+其余审查结果：
+
+- `src/compatibility.ts:168–174` 保留了三个核心 DSH 包相互相等、版本精确命中及 pi-ai 精确为 `0.85.1` 的条件；未发现这里新增了未来版本或核心混装放行。
+- 已检查包的未知状态仍阻止探测；凭据读取位于 runtime 门控及显式 `probe` 判断之后（`src/capability-diagnostics.ts:155–162`）。未发现本补丁新增的凭据泄露路径。
+- 新增的 `pending: null` fixture 本身不能证明 rc.2 类型或浏览器兼容。
+
+**独立验证仍待完成：** 两个精确版本的同产物安装/runtime matrix、分别针对 rc.1 和 rc.2 的 typecheck，以及浏览器回归。当前开发依赖仍固定 rc.1（`package.json:146–204`）；matrix 会检查产物哈希一致（`scripts/check-dsh-matrix.mjs:46–48`），但源码中的检查逻辑不等于检查已经通过。提供的上游声明差异也不能证明插件是否使用了被移除的 `OnboardingSurface` 或变更的 `LayoutController` 构造签名。
+
+未执行工具、命令、测试或真实 provider 请求，也未检查源码包以外的文件。
+
+## Final report after five reproduced UI-peer controls — PASS
+
+**PASS（仅限所提供源码的静态审查）**。此前“四个 mandatory UI peers 未纳入一致性列表”的问题已修复；未发现足以阻塞本补丁的确定性回归。此结论不代表安装、运行时或浏览器验证通过。
+
+- **UI/core 混装检查已补齐。** `src/compatibility.ts:17–20` 与 `compatibility.json:16–19` 均加入四个 UI peers。`scripts/check-compatibility.mjs:121–132` 校验列表与全部 mandatory DSH peers 精确相等，并要求安装版本一致。`src/capability-diagnostics.ts:119–131` 会拒绝 core/UI 混装；UI 元数据缺失返回 `unknown`，在第 155–157 行阻止凭据读取和网络探针。
+- **rc.1 保留，rc.2 是精确扩展。** `src/compatibility.ts:7–10,172–178` 接受一致的 rc.1 或 rc.2，均固定配对 pi-ai `0.85.1`；不放行混合核心版本、rc.3 或其他 pi-ai 配对。开发依赖仍保留 rc.1。测试 fixture 添加 `pending: null` 没有引入生产代码对 rc.2 API 的依赖。
+- **optional commands 没有被误设为必需。** `package.json:122,137–140` 保留其 optional 属性及精确版本范围；缺席不会使完整 mandatory 集合失效。但一致性检查**不检查已安装的 commands 版本**，因此不能宣称这些诊断证明了可选命令服务的版本一致性或行为兼容；提供的材料不足以据此认定实际回归。
+- **不同检查的范围不能混同。** `src/compatibility.ts:35–40,241–250` 的 `detectCompatibility` 仍只检查三个核心包及 pi-ai。因此 doctor 的 `compatible` 单独不能排除 UI 混装或 UI 元数据缺失；完整 mandatory 检查存在于上述 capability diagnostics 和检查脚本中。
+
+证据限制：
+
+- `src/capability-diagnostics.ts:64–78,194–198` 只将完成响应视为所选模型、固定请求的成功；HTTP 200 本身不足，成功也不证明活动 profile、浏览器、续接或可选能力兼容。
+- `scripts/canary-multiversion.test.mjs:27–36` 使用记录环境变量并退出的替身子进程，证明的是 canary 路由与分类逻辑，不是真实安装成功。
+- `scripts/check-dsh-matrix.mjs:17–47` 要求两版本完整报告、相同制品哈希，并排除修补过的宿主候选；这些是验收逻辑，**未提供实际执行结果**。合成 runtime 报告也不能替代真实 provider 或浏览器验收。
+- 上游声明存在构造函数变化及导出移除；未提供对应插件消费代码，不能断言命中或不命中。仅凭这些上游变化不能制造具体阻塞项。
+
+按要求未使用工具、运行命令或引用实施历史。

package/docs/experiments/dsh-017rc2-compatibility.md

@@ -0,0 +1,31 @@
+# Exact DSH 0.1.7-rc.2 compatibility — Issue #271
+
+Alpha 4.50 candidate adds exact DSH `0.1.7-rc.2` while retaining `0.1.7-rc.1`. Both pair with plugin-owned pi-ai `0.85.1` and schemastery `3.18.4`. This is not support for intermediate alpha releases, rc.3, mixed versions, or a newer pi-ai. Current publication status is established by the matching npm package/tag/Release, not this candidate record. Public installation recommendations stay on the previously published version until readback.
+
+## Contract and API investigation
+
+The peer range is the explicit union `0.1.7-rc.1 || 0.1.7-rc.2`, not a wildcard. Development dependencies and the committed frozen lock remain at rc.1. Runtime diagnostics and the strict development checker require a consistent declared version. All **19 mandatory DSH peers**, including the four UI peers, are listed in the common compatibility contract; the checker asserts that list equals the mandatory DSH peer set. The optional commands service remains optional. The ordinary doctor's compact four-package report is not a complete UI-peer audit; use the capability diagnostics/strict checks for that broader scope. Neither output proves live model entitlement.
+
+Compared integrity-verified registry declarations from 25 rc.2 packages against the installed rc.1 package declarations; nine had changes. Important additions include session/tool-history projection, the pending model-selection state, localized approval display fields and optional Modal controls. The atomic-write package now documents dead-PID lock recovery. Changed layout construction and removed OnboardingSurface are not consumed by this plugin. No new rc.2-only runtime API was required for the existing behavior. Do not infer cross-host/PID-namespace lock safety or native deferred-tool support from this compatibility update.
+
+## Reproduced findings and repairs
+
+The new rc.2 compatibility case failed before the declaration/pair update. An independent source reviewer then found that union peers could permit UI/core mixtures if mandatory UI peers were omitted from the consistency list. Five regression cases reproduced this gap before the fix; all pass after adding the UI peers and the mandatory-list invariant. The final independent review returned PASS within its static-source scope.
+
+The rc.2 source fixture first failed types because three ModelDirectoryState test fixtures lacked the new `pending` field. They now explicitly supply `pending: null` with a type compatible with both hosts; production types were not weakened. Initial browser loading then failed because rc.2's UI primitives import the newly split `dsh-util-code-language` source helper. The disposable source-test fixture adds the actual published `0.1.7-rc.2` helper, not a stub; the full DSH distribution supplies it through dsh-tool-fs. No installed host library, default, plugin-manager exemption, or production dependency was patched for the passing installed checks.
+
+## Executed evidence
+
+- Frozen rc.1 dependency install and full check: **125 files / 1,452 tests**, lint, types, build, proxy/import isolation, CLI, strict compatibility and package audit passed.
+- Final Chromium on rc.1: **13 files / 73 tests**.
+- Disposable rc.2 source fixture: all 60 direct DSH development/source-helper packages pinned to rc.2; full host/client typecheck passed; Chromium **13 files / 73 tests** passed; nine focused image/selection/diagnostic suites **130 tests** and ten additional auth/transport/compaction suites **178 tests** passed. Source bytes match the final production source.
+- Unmodified isolated DSH **rc.1 and rc.2** both installed the same packed candidate without version exemptions, loaded its profile and passed the runtime checker. Each preserved disabled defaults, prepared models, checked disposal/Reserve logic, exercised ten native-compaction processes across plain/zstd persistence, and ran two synthetic generations/two edits with inherited-access/source/refusal checks. Matrix archive SHA-256: `d7c50c41fc39f024d08c1b45444aec640f1ab1d4107059e0733de213dd0bc1ff`.
+- No real image, selection or Reserve acceptance was performed; separate read-only model source reviews are recorded separately. The first pre-review-fix matrix was stopped and is not claimed as passing.
+
+Machine-readable evidence, source/runtime hashes and package comparison identities: `evidence/issue-271-compatibility.json`. Final evidence/catalog annotations followed the matrix without changing runtime files; exact-head and exact-main CI remain release gates.
+
+## Reproduction and boundaries
+
+On the committed rc.1 development baseline run the frozen install, `pnpm run check`, `pnpm run test:browser`, and `pnpm run check:dsh-matrix`. The matrix reads both exact declared targets. For the additional rc.2 source check, copy the tracked source to a disposable directory, pin its DSH development packages plus `@deepseek-ai/dsh-util-code-language` to rc.2, install with `--ignore-scripts` and a fixture-only regenerated lock, verify exact package versions, then run host/client types and browser tests. Never apply that development fixture procedure to a user's daily profile.
+
+Task orchestration remains hard-paused. No daily profile, account, 3080/3081 service, experimental default, latest promotion or host upgrade is part of this delivery. Full everyday Session/mobile/Windows GUI and live account quality remain outside the scoped evidence. Historical compatibility entries remain intact; older active npm channel trackers remain open instead of being falsely marked supported.

package/docs/experiments/evidence/alpha-449-publication.json

@@ -0,0 +1,26 @@
+{
+  "recordedAt": "2026-09-26T02:57:04.224411+00:00",
+  "version": "0.1.0-alpha.4.49",
+  "alpha": "0.1.0-alpha.4.49",
+  "latest": "0.1.0-alpha.4.47",
+  "tagSHA": "7dce08912296680a0bce6633bd78be5827d00dc3",
+  "release": {
+    "isDraft": false,
+    "isPrerelease": true,
+    "publishedAt": "2026-09-26T02:56:29Z",
+    "tagName": "v0.1.0-alpha.4.49",
+    "targetCommitish": "7dce08912296680a0bce6633bd78be5827d00dc3",
+    "url": "https://github.com/franksong2702/dsh-codex-connect/releases/tag/v0.1.0-alpha.4.49"
+  },
+  "originalPublishRun": 36212860716,
+  "originalPublishConclusion": "failure at public readback after npm publish succeeded",
+  "recoveryRun": {
+    "conclusion": "success",
+    "headSha": "7dce08912296680a0bce6633bd78be5827d00dc3",
+    "status": "completed",
+    "url": "https://github.com/franksong2702/dsh-codex-connect/actions/runs/36213209903"
+  },
+  "recoveryArchiveSHA256": "ca7fc17ff4f5ba6a3d266c3655447420a6ee9b7b3df983cc42d347708fab5e26",
+  "npmRepublished": false,
+  "latestPromoted": false
+}