dsh-vision-router 2.0.0 → 2.1.0

package/README.md

@@ -10,18 +10,28 @@
 
 <p align="center">
   <a href="https://awesome-dsh-plugin.com"><img src="https://awesome-dsh-plugin.com/badge.svg" alt="awesome · DSH plugin" /></a>
-  <a href="https://github.com/zp-home/dsh-recommend"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fzp-home%2Fdsh-recommend%2Fmain%2Fdata%2Fbadges%2Fysr666__dsh-vision-router.certified.json&amp;style=flat-square" alt="dsh-recommend 🏅 精选认证" /></a>
-  <a href="https://github.com/zp-home/dsh-recommend"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fzp-home%2Fdsh-recommend%2Fmain%2Fdata%2Fbadges%2Fysr666__dsh-vision-router.json&amp;style=flat-square" alt="dsh score 0.90" /></a>
-  <a href="https://dshplugin.app/plugins/dsh-vision-router"><img src="https://img.shields.io/badge/DSHPlugin.app-listed-555?style=flat-square" alt="Listed on DSHPlugin.app" /></a>
+  <a href="https://github.com/zp-home/dsh-recommend"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fzp-home%2Fdsh-recommend%2Fmain%2Fdata%2Fbadges%2Fysr666__dsh-vision-router.certified.json&amp;style=flat-square" alt="dsh-recommend 🏅 certified" /></a>
+  <a href="https://www.dshbase.com/plugins/dsh-vision-router/"><img src="https://img.shields.io/badge/dshbase-install--tested-2EA44F?style=flat-square" alt="dshbase install-tested" /></a>
+  <a href="https://github.com/SoberReport-AI/DeepGuard/blob/main/reports/dsh-vision-router/2.0.1/39c8f2b2d69aa398418fd6c8ab40b691a92a1a3d.json"><img src="https://img.shields.io/badge/DeepGuard-audit%20clean-2EA44F?style=flat-square" alt="DeepGuard audit clean" /></a>
+  <a href="https://whyihaveyou.github.io/dsh-suite/"><img src="https://img.shields.io/badge/featured%20on-dsh--suite-4d6bfe?style=flat-square" alt="featured on dsh-suite" /></a>
 </p>
 
 <p align="center">
-  <a href="https://github.com/ysr666/dsh-vision-router/releases/tag/v2.0.0"><img src="https://img.shields.io/badge/release-v2.0.0-5B4CF0?style=flat-square" alt="Release v2.0.0" /></a>
+  <a href="https://github.com/ysr666/dsh-vision-router/releases/tag/v2.1.0"><img src="https://img.shields.io/badge/release-v2.1.0-5B4CF0?style=flat-square" alt="Release v2.1.0" /></a>
   <a href="tests"><img src="https://img.shields.io/badge/verified-Node%2022%20%2B%2024-2EA44F?style=flat-square" alt="Verified: Node 22 + 24" /></a>
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-2EA44F?style=flat-square" alt="License: MIT" /></a>
   <a href="package.json"><img src="https://img.shields.io/badge/Node.js-%3E%3D22-339933?style=flat-square&amp;logo=nodedotjs&amp;logoColor=white" alt="Node.js >=22" /></a>
   <img src="https://img.shields.io/badge/runtime-no%20Python-8A2BE2?style=flat-square" alt="No Python" />
-  <a href="cordis.patch.yml"><img src="https://img.shields.io/badge/DSH-Web%20profile-5B4CF0?style=flat-square" alt="DSH Web profile" /></a>
+</p>
+
+<p align="center">
+  <sub>Ecosystem:</sub>
+  <a href="https://dshplugin.app/plugins/dsh-vision-router">DSHPlugin.app</a> ·
+  <a href="https://github.com/diegosouzapw/awesome-omni-dsh-plugins">Awesome Omni DSH Plugins</a> ·
+  <a href="https://dshpluginhub.ai/plugins/dsh-vision-router">dshpluginhub.ai</a> ·
+  <a href="https://www.dsh.plus/en/plugins/dsh-vision-router/">dsh.plus</a> ·
+  <a href="https://dshplugins.ai/">dshplugins.ai</a> ·
+  <a href="https://dshmarket.com/p/ysr666/dsh-vision-router/">dsh-market</a>
 </p>
 
 <p align="center">English · <a href="README.zh.md">中文</a></p>
@@ -29,9 +39,9 @@
 <p align="center">💬 <strong>QQ community group: 1105463028</strong></p>
 
 > [!WARNING]
-> 📌 **Announcement (v2.0.0)**
+> 📌 **Announcement (v2.1.0)**
 >
-> **v2.0.0:** Capability-aware Auto routing + benchmarks, explicit 👁 Vision, and Settings 2.0. [What’s new →](docs/releases/v2.0.0.md)
+> **v2.1.0:** Native five-card Settings, explicit Vision mode, runtime i18n, hardened capability routing/benchmarks, and the DSH rc.8 support floor. [What’s new →](docs/releases/v2.1.0.md)
 
 <p align="center">
   <img src="assets/vision-demo.gif" width="640" alt="Demo: paste an image, the agent locates the send button with vision_ground / vision_crop / vision_pixel_diff and answers with coordinates" />
@@ -54,7 +64,7 @@
 
 ## Why this exists
 
-Most DSH vision plugins bridge images to DeepSeek as *text descriptions* — lossy, one-shot, and blind to pixels. This plugin keeps the **original pixels on the vision model's side** and DeepSeek on the reasoning side, and makes looking at an image an **ordinary tool call**:
+Most DSH vision plugins bridge images to DeepSeek as *text descriptions* — lossy, one-shot, and blind to pixels. This plugin keeps the **Host-canonical image pixels on the vision model's side** and DeepSeek on the reasoning side, and makes looking at an image an **ordinary tool call**:
 
 - **One command install.** The package ships its own composition patch (`dsh.bundle.patch`): `dsh plugin add` wires the row, the admission wrapper and the attachment limits automatically — zero manual file edits. Taking over the official DeepSeek route is an optional setting (stealth mode, off by default).
 - **Free by default.** Vision tools end with a five-model OVHcloud anonymous fallback: no account, no key, 2 requests/minute per IP per model, roughly 10 RPM in theory across independent buckets. User-provided vision models run first.
@@ -67,11 +77,14 @@ Most DSH vision plugins bridge images to DeepSeek as *text descriptions* — los
 
 **One-line take**: most dsh vision plugins turn images into *text descriptions* for DeepSeek
 (description bridge — lossy); this plugin hands the image turn *straight to a vision model*
-(routing bridge — pixel-faithful), with a built-in keyless free fallback.
+(routing bridge — pixel-level), with a built-in keyless free fallback.
+
+> [!NOTE]
+> On DSH 0.1.2-alpha.1+, attachments remain Host-owned. Vision Router consumes the Host-persisted canonical image: clean single-frame 8-bit sRGB/sRGBA images inside the configured normalization limits can pass through byte-identically, while images that need orientation, color-space, metadata, animation, or size normalization may be re-encoded. Pixel tools therefore promise the Host-canonical raster, not preservation of the uploader's original encoded bytes.
 
 | | Manual model switching | MCP vision bridge | dsh-vision-router |
 |---|---|---|---|
-| Pixel fidelity | ✅ full (when switched) | ❌ text description only | ✅ full, on the image turn |
+| Image pixels | ✅ available (when switched) | ❌ text description only | ✅ Host-canonical raster, on the image turn |
 | Automatic | ❌ | ✅ | ✅ |
 | Daily model untouched | ❌ (whole session swapped) | ✅ | ✅ |
 | Provider failure recovery | ❌ | ❌ | ✅ fallback chains |
@@ -83,7 +96,7 @@ Most DSH vision plugins bridge images to DeepSeek as *text descriptions* — los
 
 | Project | Approach | What this plugin adds |
 |---|---|---|
-| [dsh-vision-sidecar](https://github.com/121103qwq/dsh-vision-sidecar) | Pre-describes images with an external VLM; the description joins the session as a message to DeepSeek; LLM7.io anonymous endpoint by default (OVHcloud listed as a no-key alternative) | Description bridge; this plugin adds raw-image routing, with `vision_describe` covering descriptions on demand |
+| [dsh-vision-sidecar](https://github.com/121103qwq/dsh-vision-sidecar) | Pre-describes images with an external VLM; the description joins the session as a message to DeepSeek; LLM7.io anonymous endpoint by default (OVHcloud listed as a no-key alternative) | Description bridge; this plugin adds image routing, with `vision_describe` covering descriptions on demand |
 | [dsh-vision-proxy](https://github.com/Flyvhidbwo/dsh-vision-proxy) | Wraps a provider route and transcribes images into text in the request stream | Transcription bridge; this plugin wraps no provider — it rewrites routing through `agent/request` waterfalls |
 | [dsh-vision-provider](https://github.com/libinyam/dsh-vision-provider) | Registers `DeepSeek + Vision` combined routes: images are described by the chosen vision model before reaching DeepSeek | Two-model bridge idea; this plugin adds automatic routing, fallback chains and tools on top |
 | [modlens](https://github.com/liustack/modlens) | The first dsh vision plugin; reuses local Claude Code/Codex/OpenCode/Pi logins as vision engines | Engine-reuse idea; this plugin ships its own provider chain and depends on no other local CLI |
@@ -199,7 +212,7 @@ Any of these channels can join the vision chain as an `httpProviders` entry (key
 - **Original pixels, real answers.** The vision chain reads the image at original resolution (auto-downscaled only to protect latency/quota); the agent's question travels with the image, so answers are about *your* question, not a generic description.
 - **Automatic failover with classified errors.** Region blocks, ToS filtering, 402 quota, 429 rate limits, context overflow, network failures — the chain walks providers one by one and only reports after all of them failed, with actionable advice. A 429 immediately advances to the next backend and opens a Retry-After-aware cooldown instead of sleeping inside the request.
 - **Image memory.** Vision answers are cached by attachment content hash; later text turns substitute the recorded description (marked as untrusted evidence), so DeepSeek genuinely remembers earlier images without re-spending vision calls.
-- **A verifiable pixel loop.** Reference → `vision_html_screenshot` → `vision_pixel_diff` (ratio + red heatmap + worst-region ranking) → fix → repeat until the mismatch converges. UI restoration becomes measurable instead of eyeballed.
+- **A verifiable pixel loop.** Reference → `vision_html_screenshot` → `vision_pixel_diff` (ratio + worst 8×8-grid regions) → fix → repeat until the mismatch converges. UI restoration becomes measurable instead of eyeballed.
 - **Stable tool schema.** All fourteen deep tools are registered from session start by default, avoiding a mid-conversation tool-list expansion that can invalidate long-context KV/prefix caches. `progressiveTools: true` remains an advanced boot-time opt-in; only then does `vision_activate` mount the tools on demand. See [`docs/progressive-tools-cache.md`](docs/progressive-tools-cache.md).
 - **Selective proxy.** Only the configured vision provider hosts go through your local proxy; DeepSeek stays direct.
 
@@ -400,6 +413,7 @@ ollama pull qwen2.5vl
 ## Requirements
 
 - DeepSeek Harness Web profile. Normal installs can use `npx @deepseek-ai/dsh ...`; source checkouts use `pnpm dsh ...`. A bare `dsh ...` command only works when the CLI is already on your shell `PATH`.
+- **DSH Host support window:** DVR 2.1.x supports DSH `0.1.0-rc.8` (minimum), `0.1.1-rc.1` (previous released train), and current `0.1.1-rc.2`; DSH `0.1.2-alpha.4` is canary-only evidence. DVR 2.0.x was the final train with public support for rc.6/rc.7. See [DSH Host support window](docs/architecture/dsh-support-window.md).
 - Node ≥ 22 (host side).
 - No API key for the default free chain; a credential reference (`apiKeyEnv`) only for paid `httpProviders`.
 - Chrome / Chromium / Edge is needed only for `vision_html_screenshot`; every other tool works without a browser.
@@ -573,8 +587,11 @@ Manual fallback: in VS Code, use “Save with Encoding” → `UTF-8` (without B
 ## Star History
 
 <p align="center">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/ysr666/dsh-vision-router/star-history/assets/star-history/star-history-dark.svg">
-    <img alt="Star history chart" src="https://raw.githubusercontent.com/ysr666/dsh-vision-router/star-history/assets/star-history/star-history-light.svg" width="100%">
-  </picture>
+  <a href="https://www.star-history.com/?repos=ysr666%2Fdsh-vision-router&type=date&legend=top-left">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&theme=dark&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" />
+      <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" />
+      <img alt="Star History Chart" src="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" width="100%" />
+    </picture>
+  </a>
 </p>

package/README.zh.md

@@ -11,17 +11,27 @@
 <p align="center">
   <a href="https://awesome-dsh-plugin.com"><img src="https://awesome-dsh-plugin.com/badge.svg" alt="awesome · DSH plugin" /></a>
   <a href="https://github.com/zp-home/dsh-recommend"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fzp-home%2Fdsh-recommend%2Fmain%2Fdata%2Fbadges%2Fysr666__dsh-vision-router.certified.json&amp;style=flat-square" alt="dsh-recommend 🏅 精选认证" /></a>
-  <a href="https://github.com/zp-home/dsh-recommend"><img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Fzp-home%2Fdsh-recommend%2Fmain%2Fdata%2Fbadges%2Fysr666__dsh-vision-router.json&amp;style=flat-square" alt="dsh score 0.90" /></a>
-  <a href="https://dshplugin.app/plugins/dsh-vision-router"><img src="https://img.shields.io/badge/DSHPlugin.app-listed-555?style=flat-square" alt="已收录于 DSHPlugin.app" /></a>
+  <a href="https://www.dshbase.com/plugins/dsh-vision-router/"><img src="https://img.shields.io/badge/dshbase-install--tested-2EA44F?style=flat-square" alt="dshbase 实机安装验证" /></a>
+  <a href="https://github.com/SoberReport-AI/DeepGuard/blob/main/reports/dsh-vision-router/2.0.1/39c8f2b2d69aa398418fd6c8ab40b691a92a1a3d.json"><img src="https://img.shields.io/badge/DeepGuard-audit%20clean-2EA44F?style=flat-square" alt="DeepGuard 审计 clean" /></a>
+  <a href="https://whyihaveyou.github.io/dsh-suite/"><img src="https://img.shields.io/badge/featured%20on-dsh--suite-4d6bfe?style=flat-square" alt="dsh-suite 精选收录" /></a>
 </p>
 
 <p align="center">
-  <a href="https://github.com/ysr666/dsh-vision-router/releases/tag/v2.0.0"><img src="https://img.shields.io/badge/release-v2.0.0-5B4CF0?style=flat-square" alt="Release v2.0.0" /></a>
-  <a href="tests"><img src="https://img.shields.io/badge/verified-Node%2022%20%2B%2024-2EA44F?style=flat-square" alt="Verified: Node 22 + 24" /></a>
-  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-2EA44F?style=flat-square" alt="License: MIT" /></a>
+  <a href="https://github.com/ysr666/dsh-vision-router/releases/tag/v2.1.0"><img src="https://img.shields.io/badge/release-v2.1.0-5B4CF0?style=flat-square" alt="Release v2.1.0" /></a>
+  <a href="tests"><img src="https://img.shields.io/badge/verified-Node%2022%20%2B%2024-2EA44F?style=flat-square" alt="已验证 Node 22 + 24" /></a>
+  <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-2EA44F?style=flat-square" alt="MIT 许可证" /></a>
   <a href="package.json"><img src="https://img.shields.io/badge/Node.js-%3E%3D22-339933?style=flat-square&amp;logo=nodedotjs&amp;logoColor=white" alt="Node.js >=22" /></a>
-  <img src="https://img.shields.io/badge/runtime-no%20Python-8A2BE2?style=flat-square" alt="No Python" />
-  <a href="cordis.patch.yml"><img src="https://img.shields.io/badge/DSH-Web%20profile-5B4CF0?style=flat-square" alt="DSH Web profile" /></a>
+  <img src="https://img.shields.io/badge/runtime-no%20Python-8A2BE2?style=flat-square" alt="无需 Python" />
+</p>
+
+<p align="center">
+  <sub>生态收录：</sub>
+  <a href="https://dshplugin.app/plugins/dsh-vision-router">DSHPlugin.app</a> ·
+  <a href="https://github.com/diegosouzapw/awesome-omni-dsh-plugins">Awesome Omni DSH Plugins</a> ·
+  <a href="https://dshpluginhub.ai/plugins/dsh-vision-router">dshpluginhub.ai</a> ·
+  <a href="https://www.dsh.plus/zh/plugins/dsh-vision-router/">dsh.plus</a> ·
+  <a href="https://dshplugins.ai/">dshplugins.ai</a> ·
+  <a href="https://dshmarket.com/p/ysr666/dsh-vision-router/">dsh-market</a>
 </p>
 
 <p align="center"><a href="README.md">English</a> · 中文</p>
@@ -29,9 +39,9 @@
 <p align="center">💬 <strong>QQ 用户交流群：1105463028</strong></p>
 
 > [!WARNING]
-> 📌 **公告（v2.0.0）**
+> 📌 **公告（v2.1.0）**
 >
-> **v2.0.0：Auto 能力路由+测评、输入框识图、设置 2.0。** [查看完整更新 →](docs/releases/v2.0.0.md)
+> **v2.1.0：原生五卡设置、输入框识图、运行时双语、能力路由/测评加固，并正式启用 DSH rc.8 最低支持线。** [查看完整更新 →](docs/releases/v2.1.0.md)
 
 <p align="center">
   <img src="assets/vision-demo.gif" width="640" alt="演示：粘贴图片，Agent 用 vision_ground / vision_crop / vision_pixel_diff 定位发送按钮并给出坐标" />
@@ -54,7 +64,7 @@
 
 ## 为什么做这个
 
-大多数 DSH 视觉插件把图片“翻译”成一段文字描述再喂给 DeepSeek——有损、一次性、看不见像素。本插件把**原图像素留在视觉模型侧**、把推理留在 DeepSeek 侧，并把“看图”变成一次**普通的工具调用**：
+大多数 DSH 视觉插件把图片“翻译”成一段文字描述再喂给 DeepSeek——有损、一次性、看不见像素。本插件把**Host 规范化后的图像像素留在视觉模型侧**、把推理留在 DeepSeek 侧，并把“看图”变成一次**普通的工具调用**：
 
 - **一条命令安装。** 包自带组合补丁（`dsh.bundle.patch`）：`dsh plugin add` 自动完成插件行挂载、准入包装与附件限制放宽——不用手改任何文件。是否接管官方 DeepSeek 路由由「隐身模式」开关决定（默认关）。
 - **默认免费。** 视觉工具最终兜底为 5 个 OVHcloud 匿名视觉模型：免注册、免 Key，每 IP、每模型 2 次/分钟，独立限额理论合计约 10 次/分钟；用户自备视觉模型会优先调用。
@@ -66,11 +76,14 @@
 ## 对比同类插件
 
 **一句话讲清区别**：其他 dsh 视觉插件大多"把图片转成文字描述再喂给 DeepSeek"（描述桥，有信息损耗）；
-本插件主打"**图片轮直接交给视觉模型看原图**"（路由桥，像素保真），同时内置免 Key 免费模型兜底。
+本插件主打"**图片轮直接交给视觉模型看图像像素**"（路由桥，像素级），同时内置免 Key 免费模型兜底。
+
+> [!NOTE]
+> 在 DSH 0.1.2-alpha.1+ 上，附件仍由 Host 单一持有。Vision Router 消费的是 Host 持久化后的 canonical image：落在规范化限制内的单帧 8-bit sRGB/sRGBA 图片可以逐字节直通；需要旋转、色彩空间、元数据、动画或尺寸规范化的图片可能会被重新编码。因此像素工具承诺的是 Host canonical raster，而不是上传源文件编码字节逐字节不变。
 
 | | 手动切换模型 | MCP 视觉桥 | 本插件 |
 |---|---|---|---|
-| 像素保真 | ✅ 完整（切换后） | ❌ 只有文字描述 | ✅ 完整，图片轮内 |
+| 图像像素 | ✅ 可用（切换后） | ❌ 只有文字描述 | ✅ Host 规范化栅格，图片轮内 |
 | 自动化 | ❌ | ✅ | ✅ |
 | 日常模型不受影响 | ❌（整会话被换） | ✅ | ✅ |
 | 供应商失败恢复 | ❌ | ❌ | ✅ 降级链 |
@@ -82,7 +95,7 @@
 
 | 项目 | 思路 | 本插件的差异 |
 |---|---|---|
-| [dsh-vision-sidecar](https://github.com/121103qwq/dsh-vision-sidecar) | 图片先经外部 VLM 做 OCR/描述，描述作为会话消息交给 DeepSeek；默认 LLM7.io 匿名端点（OVHcloud 为无 Key 备选） | 描述桥方案；本插件提供"原图直看"路由，描述能力由 `vision_describe` 按需替代 |
+| [dsh-vision-sidecar](https://github.com/121103qwq/dsh-vision-sidecar) | 图片先经外部 VLM 做 OCR/描述，描述作为会话消息交给 DeepSeek；默认 LLM7.io 匿名端点（OVHcloud 为无 Key 备选） | 描述桥方案；本插件提供"图像直看"路由，描述能力由 `vision_describe` 按需替代 |
 | [dsh-vision-proxy](https://github.com/Flyvhidbwo/dsh-vision-proxy) | 包装 provider 路由，请求流里把图片转译成文本再交给 DeepSeek | 转译桥方案；本插件不包装 provider，通过 `agent/request` 瀑布改写路由 |
 | [dsh-vision-provider](https://github.com/libinyam/dsh-vision-provider) | 注册 `DeepSeek + Vision` 组合路由：图片先经所选视觉模型转成描述，再交给 DeepSeek | 双模型桥思路；本插件在此基础上增加自动路由、降级链与工具 |
 | [modlens](https://github.com/liustack/modlens) | 最早的 dsh 视觉插件；复用本机 Claude Code/Codex/OpenCode/Pi 等登录态作为视觉引擎 | 引擎复用思路；本插件自带供应商链，不依赖本机其他 CLI |
@@ -398,6 +411,7 @@ ollama pull qwen2.5vl
 ## 环境要求
 
 - DeepSeek Harness 的 Web profile。普通安装可用 `npx @deepseek-ai/dsh ...`；从源码仓库运行时用 `pnpm dsh ...`。只有 CLI 已经进入系统 `PATH` 时才能直接写 `dsh ...`。
+- **DSH Host 支持窗口：** DVR 2.1.x 支持 DSH `0.1.0-rc.8`（最低）、`0.1.1-rc.1`（上一正式支持线）以及当前 `0.1.1-rc.2`；DSH `0.1.2-alpha.4` 仅作为 canary 兼容证据。DVR 2.0.x 是最后公开支持 rc.6/rc.7 的版本线。详见 [DSH Host 支持窗口](docs/architecture/dsh-support-window.md)。
 - Node ≥ 22（宿主侧）。
 - 默认免费链路无需 API Key；付费 `httpProviders` 只需一个凭据引用（`apiKeyEnv`）。
 - 只有 `vision_html_screenshot` 需要 Chrome / Chromium / Edge；其余工具无浏览器也能用。
@@ -569,8 +583,11 @@ npx dsh-vision-router doctor --profile web
 ## Star 趋势
 
 <p align="center">
-  <picture>
-    <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/ysr666/dsh-vision-router/star-history/assets/star-history/star-history-dark.svg">
-    <img alt="Star 历史趋势图" src="https://raw.githubusercontent.com/ysr666/dsh-vision-router/star-history/assets/star-history/star-history-light.svg" width="100%">
-  </picture>
+  <a href="https://www.star-history.com/?repos=ysr666%2Fdsh-vision-router&type=date&legend=top-left">
+    <picture>
+      <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&theme=dark&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" />
+      <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" />
+      <img alt="Star 历史趋势图" src="https://api.star-history.com/chart?repos=ysr666/dsh-vision-router&type=date&legend=top-left&sealed_token=bl3whaniTB54-d4wMda4a454thk48mT71wkNh8VrSD8OhCKWdBOOQpVKGUXzoEq4kx0_0jhQzEimHIqKAaGftFVV48sqgJ1niBfGy51AX5k_soGw_e7-5Nea6ZY5To0iz7jY9ORc5a_P5N6Qlfm32G2pdHf8_5dZeuHMn5NOZCyTgFcmq2eK1Jwg8ILe" width="100%" />
+    </picture>
+  </a>
 </p>

package/cordis.patch.yml

@@ -18,13 +18,20 @@
       config:
         progressiveTools: false
 
-# Vision Router 的附件产品契约：Host attachment store 负责保存用户提交的
-# durable 原件，具体视觉后端负责本次推理所需的 resize/tile/request budget。
-# 因此存储准入保持 20MiB / 1 亿像素，同时在 DSH rc.8 新增的单边限制上
-# 显式选择 10000px：覆盖 4K/手机原图和常见长截图，但不把 Host 的全局
-# 极端长边安全闸无限放开。该值作用于整个 attachment-local（包括原生视觉
-# provider），所以这里刻意不用 32768/无限；更大的部署需求仍可由后续
-# profile/--patch 层按实际 provider 能力覆盖。
+# Vision Router 的附件产品契约：Host attachment store 是 durable 图片的唯一
+# owner，视觉工具只读取 Host 已持久化、校验后的 canonical pixels。DSH rc.8
+# 以前 Host 会把已准入的源编码直接持久化；0.1.2-alpha.1 开始又增加独立的
+# provider-independent normalization stage。若沿用 alpha.1 的 4.2MP / 4MiB
+# 默认值，DVR 的 crop / grounding / OCR / pixel-diff 会在用户毫不知情时换到
+# 一个更小的像素坐标系。因此这里把 normalization policy 同步到 DVR 既有的
+# 20MiB / 1 亿像素 / 10000px 准入边界：普通 8-bit sRGB 图片继续 pass-through，
+# 不扩大 DVR 在 rc.8 时已经允许的 durable 存储上限，同时仍让 Host 独占
+# normalization、完整性校验和对象身份。
+#
+# 注意：alpha.1 对 EXIF/色彩空间/GIF/超限编码等输入仍可能规范化或重编码。
+# DVR 不另存第二份 raw attachment，也不声称能从 canonical object 恢复源字节；
+# 像素工具的合同因此以 Host canonical pixels 为准。ImageAttachmentRef 的
+# originalDimensions 仅用于说明 Host 曾缩放，不能被当作可读取的原图。
 #
 # DSH 的 patch 是“整段 config 替换”而非深度合并。旧版 Vision Router 曾在
 # profile 自己的 cordis.patch.yml 写入同一行的 20MiB/100MP 两个字段；这层
@@ -34,11 +41,14 @@
 # 这样升级旧 profile 不要求用户手工清理配置，同时后续 profile/--patch 的
 # 明确部署策略仍保持最终所有权。
 #
-# rc.6/rc.7 没有 maxImageDimension；发布合同 CI 会用真实旧包验证额外配置键
-# 不会破坏最低支持 Host。若旧 Host 开始严格拒绝未知键，此处必须改为按能力
+# rc.6/rc.7/rc.8 没有 normalizedImage*；发布合同 CI 会用真实旧包验证额外
+# 配置键仍被安全忽略。若旧 Host 开始严格拒绝未知键，此处必须改为按能力
 # 生成配置，而不是靠版本字符串分支。
 - id: attachment-local
   config:
     maxImageBytes: 20971520
     maxImagePixels: 100000000
     maxImageDimension: 10000
+    normalizedImageMaxBytes: 20971520
+    normalizedImageMaxPixels: 100000000
+    normalizedImageMaxDimension: 10000

package/docs/architecture/2x-contract-ledger.md

@@ -0,0 +1,165 @@
+# 2.x Architecture Closure Contract Ledger
+
+Status: **normative for Post-P3 closure**
+
+Baseline main: `1f78443a75e76a8fbba5d90a305e8c53db93bb7f`
+
+This ledger freezes the externally observable and cross-boundary contracts that the 2.x Architecture Closure is not allowed to change while ownership is being simplified.
+
+The closure is a structural migration, not a product feature release. A cleaner dependency graph is not a valid reason to change user-visible behavior, Host persistence, routing semantics, authority, provider order, failure policy, or compatibility support.
+
+## Closure method
+
+Every semantic-owner migration follows the same order:
+
+1. **Characterize** the existing behavior and public/Host contract.
+2. **Add** the new internal path without deleting the old path.
+3. **Compare** old and new decisions in tests; the old path remains the parity oracle.
+4. **Switch** production ownership only after parity is complete.
+5. **Delete** the old implementation and rerun the same gates after deletion.
+6. **Merge**, then rerun the relevant gates on `main`.
+
+A green test run while the old path can still silently rescue the new path is not deletion proof.
+
+## External contract — frozen during Closure
+
+| Surface | Frozen contract |
+|---|---|
+| package entry | package root continues to resolve through `lib/public-entry.js` |
+| plugin identity | `vision-router` remains the plugin name |
+| settings namespace | `vision-router` remains the Host settings namespace |
+| settings contract revision | existing 2.0.x field meanings/defaults remain unchanged unless a separate product change is approved |
+| routing mode | `ordered` remains the safe default; `auto` requires live authority |
+| routing preference | `balanced`, `quality`, `speed`, `local` retain their existing meaning |
+| background measurement | `off`, `local-free`, `all` remain separate authority states; absence does not grant work |
+| route identity | existing wrapper/chain/provider route names and aliases remain compatible |
+| tools | existing tool names, argument schemas, result shapes and error classes remain compatible |
+| native multimodal | native image ownership remains non-intervention for automatic Router orchestration; explicit Router tools are not disabled merely because a model is native multimodal |
+| fallback | execution may reorder only already-eligible candidates; it may not invent a provider or delete a configured/local/discovered fallback |
+| session persistence | no new Host Session event type or durable index format is introduced by Closure |
+| session surface repair | existing `surfaceOp: { op: 'replace' }` and `sourceEventSeqs` semantics remain compatible |
+| attachment identity | durable attachment ids remain Host/session identities; no cross-session lookup is introduced |
+| artifact publication | existing public derived-artifact paths/return values remain compatible; managed run cleanup remains confined to Router-owned provenance/namespaces |
+| proxy setting | existing proxy/proxyHosts behavior remains compatible; Router-owned HTTP stays independent of process-global fetch mutation |
+| Doctor | Closure does not turn advisory architecture/support diagnostics into new failure exit codes |
+| support window | DVR 2.0.x continues to support the published minimum/previous/current DSH window; rc.6 support is not removed by a patch-level closure |
+| runtime platforms | Node 22/24 and the existing Ubuntu/macOS/Windows host-sharp contract remain supported |
+
+## Internal ownership target
+
+Closure may change implementation only toward this dependency direction:
+
+```text
+Authority -> Evidence -> Planner -> Execution
+                    \-> Host product projection -> Presentation
+
+SessionVisionRuntime
+  |- SessionVisionStateStore   (bounded process-local state)
+  `- SessionVisionIndex        (durable-log indexing/recovery/surface repair)
+
+VisionArtifactStore            (derived artifact ownership)
+VisionProviderTransport        (Router-owned provider HTTP)
+Compat                         (only supported Host/provider gaps with exit criteria)
+```
+
+### Single-owner rules
+
+The final closure must make these statements true:
+
+- routing authority has one production owner;
+- planner output is data, never a disguised Settings object;
+- session durable-log indexing/targeted recovery/surface repair has one production implementation;
+- a Session store is not discovered through an implicit process-global "current" owner;
+- browser code renders Host product decisions instead of re-deriving routing/background authority or eligibility;
+- Router-owned provider HTTP has one transport boundary;
+- compatibility shims translate supported gaps but do not own product policy.
+
+## C1 — Session/Core policy convergence contract
+
+Allowed changes:
+
+- add one narrow internal SessionVisionRuntime dependency to core composition;
+- make SessionVisionIndex the sole owner of event-log scan, targeted attachment recovery and surface repair;
+- replace SessionSurfacePolicy -> fake Settings projection with explicit derived runtime flags;
+- remove obsolete current-store/service-locator and store monkey-patching after parity proof.
+
+Forbidden changes:
+
+- cache size/TTL changes;
+- attachment-id semantics;
+- Session event format changes;
+- new persistence files;
+- route/provider/tool policy changes;
+- native-image ownership changes;
+- timeout/retry/budget changes.
+
+**Stop condition:** if the migration starts requiring provider/routing/artifact redesign or broad public/core API churn beyond one narrow optional runtime dependency, stop and redesign rather than pursuing DI purity.
+
+## C2 — Presentation convergence contract
+
+Host owns decisions; browser owns presentation and user interaction.
+
+The stable presentation DTO should be additive and versioned. It may expose decisions such as:
+
+- `canBenchmark` / `benchmarkReason`;
+- `capabilityState`;
+- `healthClass`;
+- `backgroundEligible` / `backgroundReason`;
+- routing/authority summaries safe for presentation.
+
+The DTO must not expose credentials, credential references, raw endpoints/fingerprints solely for internal execution, mutable breaker internals, or evidence objects that require the browser to reinterpret validity.
+
+Prefer extending an existing benchmark/runtime snapshot over creating another long-lived polling surface. Existing 2.0.x routes are removed only under the normal compatibility/version policy.
+
+## C3 — Bounded cleanup contract
+
+Mandatory low-risk cleanup:
+
+- retire obsolete capability-shadow naming/shim once no production consumer remains;
+- remove stale migration comments whose stated deletion phase has passed;
+- ensure every retained compatibility seam has Reason, Host gap, Feature detection, Removal condition and Tests.
+
+Conditional cleanup:
+
+- remove the VisionProviderTransport module registry only if explicit injection has a small, local change radius and does not broaden public/core signatures materially;
+- otherwise document a concrete later removal trigger and retain the working boundary.
+
+Not a closure target:
+
+- deleting legitimate rc.6/rc.8 compatibility merely to reduce file count;
+- deleting `vision-chain`;
+- rewriting the mature core for LOC reduction;
+- migrating the scheduler to `ctx.jobs` without the already-defined GO criteria;
+- changing artifact layout again.
+
+## Mandatory validation after each semantic switch
+
+At minimum, the affected slice must retain coverage for:
+
+- Ordered exact behavior;
+- Auto exact behavior and live authority revoke/recheck;
+- fallback preservation and stale-plan filtering;
+- native multimodal non-intervention;
+- text-only/plugin-owned/unknown image ownership;
+- Session restart/cold resume;
+- bounded-cache target recovery;
+- same-session and cross-session concurrency;
+- cancellation/no ALS leak;
+- artifact retention and unknown-entry preservation;
+- Router-owned HTTP independence from the global fetch patch;
+- remote/local settings behavior;
+- Node 22 and Node 24;
+- minimum/previous/current DSH contract;
+- platform/resource gates relevant to the changed boundary.
+
+## Closure completion rule
+
+The architecture is not declared CLOSED merely because C1/C2/C3 PRs merge. After deletion of the old paths, run one final adversarial audit on the resulting `main` and prove:
+
+1. one semantic owner per boundary;
+2. no duplicate production algorithm can still rescue the replacement;
+3. every remaining compatibility seam has a currently reachable supported case or an explicit removal trigger;
+4. adding a new modality (PDF/video/1+x) does not require a new Settings impersonation layer, process-global runtime locator, duplicate Session cache/index, or browser-owned authority algorithm;
+5. the full regression/contract/stress/security matrix is green on merged `main`.
+
+Only then mark **2.x architecture convergence: CLOSED**.

package/docs/architecture/compat-inventory.md

@@ -0,0 +1,121 @@
+# Compatibility seam inventory
+
+P0 records why each major compatibility seam exists and the condition that permits its removal. This inventory is normative for 2.x convergence: a shim without an exit criterion is architectural debt that cannot silently become permanent.
+
+## `lib/dsh-contract-compat.js`
+
+- **Reason:** preserve released attachment/settings/provider-ownership behavior across the supported DSH window.
+- **Host gap:** rc.6 has the single-attachment contract; later Hosts add batch save, max-dimension policy and newer settings/provider lifecycle behavior.
+- **First needed for:** minimum rc.6 support and the subsequent rc.7/rc.8 attachment migration.
+- **Feature detection:** `attachments.saveImages`, attachment `imageLimits`, settings registration/scope functions, and LLM registration methods. No version-string branch.
+- **Removal condition:** minimum supported DSH natively exposes the required attachment/settings/provider seams and legacy profile overlays are outside support.
+- **Tests:** `rc6-rc7-compat`, `rc6-real-settings-persistence`, `attachment-admission-policy`, `dsh-host-capabilities`, minimum/legacy/current contract CI.
+
+## `lib/adapter-update-coalescer.js`
+
+- **Reason:** keep Vision Router-owned duck-typed adapters compatible with Host `prepareCall` dispatch and prevent synchronous adapter-topology events from recursively reconciling forever.
+- **Host gap:** older plugin adapters do not inherit the Host adapter base class; supported Host generations can emit adapter updates synchronously during registration.
+- **First needed for:** DSH 0.1.1 `prepareCall` and atomic registration behavior.
+- **Feature detection:** adapter-local `prepareCall` presence; actual `llm/adapters-updated` event path. No version inference.
+- **Removal condition:** every supported Vision Router adapter directly satisfies the Host adapter contract and supported Host event semantics no longer require the bounded coalescer.
+- **Tests:** `adapter-prepare-call-compat`, `runtime-boundary-fixes`, current-contract Host smoke.
+
+## `lib/android-attachment-compat.js`
+
+- **Reason:** allow the minimum Host path to survive Termux/Android attachment persistence permission boundaries without taking ownership on batch-capable Hosts.
+- **Host gap:** file-backed attachment storage can fail with `EACCES`/`EPERM` in Android/Termux environments on the legacy path.
+- **First needed for:** Android/Termux support while rc.6 remains minimum.
+- **Feature detection:** Android/Termux environment, permission-boundary error and absence of the batch attachment contract.
+- **Removal condition:** minimum supported DSH owns a working Android attachment implementation for the same path and the fallback is no longer reachable.
+- **Tests:** `android-attachment-compat`, image-resource/resource-retention tests.
+
+## `lib/replay-envelope-v2-compat.js`
+
+- **Reason:** preserve delegated replay identity when producer provider/model moved into durable pi-ai replay envelope v2.
+- **Host gap:** older Vision Router replay code expected producer identity at the top level.
+- **First needed for:** rc.7 replay-envelope v2 histories.
+- **Feature detection:** exact durable producer proof: `response.kind === 'pi-ai'`, `response.version === 2`, provider and model match.
+- **Removal condition:** the supported runtime/history window no longer includes envelopes requiring source rebinding, or the Host exposes an equivalent native replay identity seam consumed directly by Vision Router.
+- **Tests:** `replay-delegation`, session/cold-resume regression coverage.
+
+## `lib/pi-ai-bridge-wire-compat.js`
+
+- **Reason:** make the legacy direct image bridge transport-equivalent to pi-ai declared wire compatibility without reading credentials or changing provider priority.
+- **Host gap:** the direct bridge predates route/model wire metadata such as max-token fields and route-owned headers.
+- **First needed for:** DSH 0.1.1 pi-ai declared provider/wire compatibility.
+- **Feature detection:** exact non-streaming OpenAI-compatible image bridge fingerprint plus resolved route/model facts; normal streaming Host traffic does not match.
+- **Removal condition:** the direct bridge is removed or every supported Host executes this image path through the native pi-ai wire seam.
+- **Tests:** `pi-ai-bridge-wire-compat`, native process-restart/cold-resume contract.
+
+## `lib/settings-client-rc8-lifecycle.js`
+
+- **Reason:** keep browser settings lifecycle coherent across legacy and current Host client generations.
+- **Host gap:** settings client attachment/replacement lifecycle is not identical across the support window.
+- **First needed for:** rc.8-era settings UI coexistence.
+- **Feature detection:** actual client/runtime lifecycle surfaces; never the Host version label.
+- **Removal condition:** supported Hosts expose one stable settings client lifecycle and the compatibility branch is proven unreachable by contract tests.
+- **Tests:** settings IA, client lifecycle, remote-settings and Web acceptance regressions.
+
+## `lib/http-compat.js`
+
+- **Reason:** isolate evidenced provider/model wire quirks from generic visual HTTP execution.
+- **Host gap:** this is provider compatibility rather than a DSH Host gap; some OpenAI-compatible endpoints reject otherwise valid generic payload shapes.
+- **First needed for:** model-family quirks such as GLM-4V-Flash output limits and image-only message handling.
+- **Feature detection:** provider/model/url rule predicates backed by known wire behavior.
+- **Removal condition:** upstream endpoint behavior becomes generic-compatible for a rule and regression evidence confirms the preset is no longer needed.
+- **Tests:** `http-compat`, provider HTTP regression tests.
+
+## `lib/vision-provider-transport.js` process/profile registry
+
+- **Reason:** carry the Router-owned provider transport into compatibility callers whose mature function signatures still accept only a raw `fetch` or use an internal direct HTTP call, while keeping Router traffic off the process-global fetch patch.
+- **Host gap:** this is an internal composition gap rather than a DSH version persona: `fetchWithOpenAICompatibility(...)` and the Anthropic catalog-correction path do not yet receive a `VisionProviderTransport` parameter explicitly.
+- **First needed for:** provider-scoped transport ownership and proxy narrowing without rewriting the mature compatibility call signatures in the same migration.
+- **Feature detection:** explicit transport-aware callers bypass the registry; only compatibility paths that call `currentVisionProviderTransport()` consume the currently installed process/profile transport. The registry never patches `globalThis.fetch`.
+- **Removal condition:** every Router-owned compatibility caller receives `VisionProviderTransport` explicitly, production has zero reads of `currentVisionProviderTransport()`, and the install/release registry can be removed without changing proxy, credential, bounded-body or cancellation behavior.
+- **Tests:** `vision-provider-transport`, `http-compat`, `catalog-corrections`, P2 Data Boundary provider-transport Node 22/24, Host pack/install smoke.
+
+## `lib/legacy-global-proxy-boundary.js`
+
+- **Reason:** retain the process-global proxy patch only for Host-owned/raw-fetch visual providers that still lack a provider-scoped proxy seam. Router-owned `vision-http` and direct protocol-correction traffic already uses `VisionProviderTransport` with an explicit dispatcher.
+- **Host gap:** the supported Host window does not yet guarantee one provider-scoped/shared HTTP proxy seam that third-party Host-owned adapters can consume without a process-global fetch wrapper.
+- **First needed for:** legacy/custom Host-owned visual provider compatibility when users configure Vision Router proxy routing.
+- **Feature detection:** live visual-chain ownership. Router-owned routes bypass the legacy patch; any unknown/Host-owned provider conservatively keeps it available. This is capability/ownership detection, not a Host-version persona.
+- **Removal condition:** **the minimum supported DSH provides a provider-scoped/shared HTTP proxy seam** that covers the remaining Host-owned/raw-fetch provider compatibility requirement.
+- **Tests:** `legacy-global-proxy-boundary`, `vision-provider-transport`, `adversarial-hardening`, P2 Data Boundary Node 22/24.
+
+## `lib/legacy-core-vision-policy-bridge.js`
+
+- **Reason:** preserve the two remaining pre-step compatibility behaviors after Core policy ownership moved to explicit session/Core surfaces: reuse the exact `SessionMemoryView` for text-only image-history rewrite, and expose exact current-turn durable attachment IDs as read-only model context for Vision Router-owned wrappers.
+- **Host gap:** the supported Host pre-step path does not natively provide both an exact session-scoped visual-memory rewrite seam for text-only fallback and a model-readable durable attachment-reference seam for Router-owned image turns.
+- **First needed for:** the Core/session ownership migration that removed Settings/config impersonation while retaining these two real pre-step behaviors.
+- **Feature detection:** live `SessionSurfacePolicy` (`rewriteCurrentImages` and ownership), exact known session visual memory, and actual current-turn image attachment IDs. No Host version-string branch and no Settings/config projection.
+- **Removal condition:** the minimum supported Host exposes native pre-step/session-memory and durable attachment-reference capabilities that make both behaviors redundant, and contract/parity tests prove the bridge can be removed without reintroducing Settings impersonation or degrading text-only/native image turns.
+- **Tests:** `settings-impersonation-closure`, `session-surface-policy`, session/runtime parity and native cold-resume coverage.
+
+## `lib/tesseract-exec-compat.js`
+
+- **Reason:** own the single process-wide `promisify(execFile)` compatibility boundary for the two narrow child-process cases Vision Router still needs: materializing Tesseract stdin image bytes, and replacing only Core's exact legacy Windows `VirtualScreen`/`CopyFromScreen` desktop-capture command with a per-monitor-DPI-safe equivalent. One owner prevents cleanup-order bugs from independently stacked `execFile` wrappers.
+- **Host gap:** these are runtime/platform gaps rather than DSH semantic ownership: Node's async `execFile` path does not consume the historical OCR `options.input`, while non-DPI-aware Windows PowerShell virtualizes desktop metrics and can disagree with physical screen-copy coordinates on scaled/mixed-DPI displays.
+- **First needed for:** Node 24/local Tesseract process execution reliability; Windows scaled/mixed-DPI `vision_screenshot` correctness (#340).
+- **Feature detection:** exact executable/call fingerprints only. Tesseract handling requires `tesseract[.exe]` + stdin input; Windows screenshot handling requires `win32`, `powershell[.exe]`, `-Command`, and the exact legacy `SystemInformation.VirtualScreen` + `Graphics.CopyFromScreen` script shape. No Host/Node version persona and unrelated child processes delegate unchanged.
+- **Removal condition:** local OCR no longer needs an `execFile` stdin shim **and** Core/Host exposes a native DPI-correct desktop-capture seam (or the legacy PowerShell command is removed), with Node 22/24 and Windows platform matrices proving the shared wrapper is unreachable before deletion.
+- **Tests:** `tesseract-node24-boot`, `qa-screenshot-runtime` (PMv2/PMv1 ordering, context restoration, exact-match passthrough, Windows PowerShell compile smoke), cross-platform Host tests.
+
+## `lib/abort-signal-compat.js`
+
+- **Reason:** keep Vision Router cancellation/deadline composition working when a supported DSH Host or bridge exposes `AbortSignal`/`AbortController` but omits the standard static `AbortSignal.any()` or `AbortSignal.timeout()` helpers used by the Router's runtime boundaries.
+- **Host gap:** some real Host/bridge environments can surface a partial AbortSignal runtime even though the declared Node support window normally provides both helpers, producing `AbortSignal.any is not a function` inside visual work.
+- **First needed for:** partial Host/bridge AbortSignal runtimes observed during Vision Router image execution and exact capability checks.
+- **Feature detection:** only the actual static helper presence is inspected. Existing native `AbortSignal.any` and `AbortSignal.timeout` functions are never replaced; only a missing helper is installed. No Node or DSH version persona is inferred.
+- **Removal condition:** every supported Host/runtime contract guarantees both static helpers in the actual realm used by plugin execution, and a cross-Host regression proves no supported bridge can present the partial runtime anymore.
+- **Tests:** `qa-turn-budget-cancellation` legacy-realm fallback/validation/non-intervention coverage plus Node 22/24 and DSH contract CI.
+
+## Removal protocol
+
+A compatibility seam may be deleted only when all of the following are true:
+
+1. its **Removal condition** is satisfied by the declared support window;
+2. the relevant capability is proved by a gating Host contract fixture or direct feature test;
+3. deleting the seam leaves Node 22/24, minimum/legacy/current Host contracts and relevant platform tests green;
+4. no Authority, Session, Storage or native-multimodal invariant changes as a side effect;
+5. the deletion is a focused change, not bundled into an unrelated routing/data-boundary refactor.