dsh-vision-router 3.2.0 → 3.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -6
- package/README.zh.md +21 -6
- package/THIRD_PARTY_NOTICES.md +167 -0
- package/assets/licenses/apache-2.0.txt +202 -0
- package/assets/licenses/llvm-mingw-LICENSE.txt +279 -0
- package/assets/licenses/mingw-w64-runtime-COPYING.txt +265 -0
- package/assets/licenses/moxcms-BSD-3-Clause.txt +26 -0
- package/assets/licenses/ncnn-LICENSE.txt +86 -0
- package/assets/licenses/roots-BSD-2-Clause.txt +24 -0
- package/assets/licenses/unicode-ident-Unicode-3.0.txt +39 -0
- package/assets/licenses/vtracer-MIT.txt +25 -0
- package/assets/licenses/zlib-rs-Zlib.txt +19 -0
- package/docs/architecture/dsh-support-window.md +25 -6
- package/docs/compatibility/dsh-0.2.2-rc2-audit.md +40 -0
- package/docs/compatibility/dsh-0.2.2-rc3-audit.md +131 -0
- package/docs/compliance/vtracer-alpha4-provenance.md +47 -0
- package/docs/compliance/vtracer-alpha4-reconstructed-Cargo.lock +567 -0
- package/docs/compliance/vtracer-alpha4-rust-inventory.json +421 -0
- package/docs/compliance/vtracer-alpha4-rust-license-texts.md +13018 -0
- package/docs/releases/v3.2.1.md +21 -0
- package/docs/releases/v3.2.2.md +25 -0
- package/docs/releases/v3.3.0.md +34 -0
- package/docs/remote-settings.md +83 -8
- package/index.js +280 -169
- package/lib/client.js +17 -17
- package/lib/core-primitives.js +155 -214
- package/lib/dsh-support-window.js +6 -3
- package/lib/native-ocr-annotation-risk.js +33 -0
- package/lib/native-ocr-canary.js +156 -0
- package/lib/native-ocr-chemistry-review.js +37 -0
- package/lib/native-ocr-document.js +243 -0
- package/lib/native-ocr-installation.js +17 -0
- package/lib/native-ocr-integrity.js +93 -0
- package/lib/native-ocr-question-labels.js +167 -0
- package/lib/native-ocr-supervisor.js +268 -0
- package/lib/remote-settings-bridge.js +93 -57
- package/lib/remote-settings-risk-client-boundary.js +2 -2
- package/lib/runtime-reliability.js +7 -0
- package/lib/session-query-readers.js +8 -2
- package/lib/session-vision-attachment-index.js +61 -14
- package/lib/settings-client-017-compat.js +4 -2
- package/lib/settings-ia-client-prelude.js +26 -10
- package/lib/tesseract-image-preprocess.js +35 -0
- package/lib/trace-vtracer-process-runtime.js +133 -0
- package/lib/trace-vtracer-process.js +43 -0
- package/lib/trace-vtracer-worker.js +163 -0
- package/lib/vision-attachment-handle-runtime.js +11 -2
- package/lib/vision-backend-runtime-policy.js +5 -3
- package/lib/vision-image-input-reader.js +67 -0
- package/lib/vision-image-input-verdict.js +24 -3
- package/lib/vision-tool-runtime-boundary.js +7 -10
- package/lib/vision-tool-stage.js +58 -0
- package/lib/web/dsh-settings-017-root-transport.js +52 -6
- package/lib/web-capability-boundary.js +6 -0
- package/package.json +10 -6
- package/scripts/install-native-ocr.mjs +144 -0
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
# v3.2.1 — Settings recovery, VTracer and RC2 Host qualification / 设置恢复、VTracer 与 RC2 兼容验收
|
|
2
|
+
|
|
3
|
+
**Status / 状态:** This is the curated stable v3.2.1 **release candidate note**. A successful protected Release workflow, GitHub Release, npm `latest` and matching package/provenance are necessary before it may be called published. / 本文是 v3.2.1 正式候选发布说明;实际发布必须以受保护 Release 工作流、GitHub Release、npm `latest` 和一致的包体及来源证明为准。
|
|
4
|
+
|
|
5
|
+
## Since v3.2.0 / 相对 v3.2.0 的变化
|
|
6
|
+
|
|
7
|
+
- **Settings bridge recovery (#823, #828):** Unify the opt-in local/authorized remote configuration path, eliminate conflicting compatibility-script ordering, and mount the native provider settings bridge through the correct Host lifecycle. Reinforce authentication, redaction, permission boundaries and Settings save/readback/reload regression coverage. / 统一本地及经授权的远程设置通道,修复兼容脚本加载顺序和原生设置服务挂载时序,补齐认证、脱敏、权限和设置保存/回读/重载验证。
|
|
8
|
+
- **SVG trace backend (#829):** Replace `potrace → jimp → @jimp/core` with pinned `@visioncortex/vtracer@1.0.0-alpha.4` WASM in an isolated Worker. Preserve the public `vision_trace` entry point while improving dependency/license provenance checks and image-quality test coverage. The trace renderer changes, so SVG path geometry and output may differ from v3.2.0. / 将 SVG 追踪依赖从 Potrace/Jimp 换为固定版本的 VTracer WASM Worker;保留公开工具入口,强化依赖许可与输出质量测试。生成的 SVG 路径形状可能与旧版不同。
|
|
9
|
+
- **Exact DSH 0.2.2-rc.2 acceptance (#830):** Pin official upstream source SHA and verify Session atomic-batch per-event semantics, route ownership, three-OS Host contracts, Chromium Settings and paste flows, macOS and Windows real Desktop, candidate tarball installation, and separately diagnose immutable published 3.2.0 on the real RC2 CLI/Web Host. / 固定 RC2 上游精确提交,对批量事件、路由、三端、真实浏览器/桌面、候选安装包及历史 npm 包做独立验收。
|
|
10
|
+
- **CI supply-chain maintenance (#824, #825):** Upgrade pinned CodeQL SARIF uploader and pnpm/action-setup; cover all 30 relevant workflows including the new RC2 gate. / 更新 CodeQL 与 pnpm Actions 固定 SHA,覆盖全部相关工作流。
|
|
11
|
+
|
|
12
|
+
## Compatibility and safe upgrade / 兼容边界与安全升级
|
|
13
|
+
|
|
14
|
+
- **No support-floor relaxation:** DSH `>=0.2.1-rc.5 <0.3.0-0` and Node.js `>=24.9.0` remain required. DSH `0.2.1-rc.3` and `0.2.0-rc.2` are **not** compatible with DVR 3.2.x; do not bypass the Host's engine admission checks. / 最低要求不变,较旧 DSH 版本明确不支持,不建议越过安装器的兼容检查。
|
|
15
|
+
- Run the read-only `doctor --upgrade-preflight`, back up your current DSH profile, Settings, attachments and important historical Session records, and preserve a known-good rollback path. DVR does not automatically rewrite or delete Host-owned history. / 升级前只读预检、备份、核验重要会话并保留回滚;插件不自动清理或改写 Host 数据。
|
|
16
|
+
- Official real Host/CLI/Web and macOS/Windows Desktop gates were run on supported exact source lines. **Third-party Dataelem Desktop's generation installer remains a separate path**: removing the Jimp chain addresses the identified dependency closure trigger but is **not evidence of a successful installation of the new npm release in that installer**. Its upstream issue and fix review remain independent. / 官方安装和第三方代际安装器须分开评价;移除 Jimp 是源码层解决已知依赖链,不代表第三方安装路径已获实测认证。
|
|
17
|
+
- No change to the default cloud-vision image egress: the anonymous fallback can transmit image content to a remote provider unless strict local-only mode is selected. / 默认云端视觉链仍可能将图片传给第三方;涉敏内容应启用严格纯本地配置。
|
|
18
|
+
|
|
19
|
+
## Release integrity / 发布完整性
|
|
20
|
+
|
|
21
|
+
The final candidate must pass fresh main-commit CI and the protected workflow's frozen-lockfile install, build, lint, typecheck, tests, reproducible build, exact published file inventory, SHA/signing/provenance and npm `latest` versus GitHub Release cross-check. Never infer publication merely from this document or a Git tag. / 最终提交须重新通过 CI 与受保护发布门禁,对 npm 与 GitHub 的同一包体、哈希和来源证明作交叉核验。
|
|
@@ -0,0 +1,25 @@
|
|
|
1
|
+
# v3.2.2 — Attachment reliability and native trace isolation / 附件可靠性与原生描摹隔离
|
|
2
|
+
|
|
3
|
+
**Status / 状态:** This is a curated **release candidate**, not evidence of publication. Only the protected Release workflow, a matching immutable GitHub Release, npm dist-tag and package provenance establish a published version. / 本文是**待发布候选说明**,并不代表已发布。正式发布以受保护 Release 工作流、GitHub Release、npm 标签与包体来源证明为准。
|
|
4
|
+
|
|
5
|
+
## Changes since v3.2.1 / 相对 v3.2.1 的变化
|
|
6
|
+
|
|
7
|
+
- **Attachment-ID and cold Session recovery (#839–#844, #846, #850–#852):** The full vision task's deadline starts before the Host's cold attachment log lookup, image reads, normalization, and backend capability preflight. Pending Host promises are raced against cancellation, and Host/user abort is passed into backend attempts instead of being mistaken for provider failure. Session-derived attachment authority is checked against the owning Session, with cleanup and privacy-safe stage diagnostics. / 识图总时限从附件恢复前开始计时,覆盖会话日志查询、图像处理及后端预检;即使旧 Host Promise 不响应取消,工具也能按预算退出。取消信号继续传到模型请求,跨 Session 不得借用附件权限,诊断日志不输出原始附件 ID。
|
|
8
|
+
- **Cache authority hardening (#838):** Strengthen attachment/cache access boundaries and regression coverage so a prior content hash or cached answer cannot authorize another Session's attachment. / 加固缓存及附件权限边界,缓存命中不得替代当前会话的有效授权。
|
|
9
|
+
- **Native VTracer fault containment (#847–#848):** Successful WASM workers exit naturally rather than being terminated immediately after posting a message. A bounded child process (3 active, up to 8 queued) isolates remaining native process faults; abort, abnormal exit, forged or oversized SVG results fail closed. The public vision_trace tool remains. The pinned VTracer engine does not change; isolated-process startup adds latency (about 90–100 ms per trace in a small macOS benchmark) and should be considered by performance-sensitive users. / 成功的 Worker 自然退出;原生计算由限流子进程承载,异常退出、取消或不合规 SVG 不会直接破坏主 Host。公开工具不变,新增进程启动开销。
|
|
10
|
+
- **Windows reliability (#845):** Repair Windows-specific package/cache handling and associated image-input verdict checks. / 修复 Windows 打包、缓存和图片输入判断相关兼容问题。
|
|
11
|
+
|
|
12
|
+
**Issue #841 scope:** A genuine source-level deadline/cancellation weakness was fixed, but the reporting user's precise Windows ~120-second stall was **not independently reproduced**. A slow but responsive remote vision model can still legitimately use the configured task budget (default 120 seconds). Do not claim that all possible 120-second backend stalls are eliminated. / 已修复确定存在的超时与取消缺陷,但未独立复现报告者现场;默认 120 秒预算内的慢模型调用仍可能耗时,不能宣传为彻底消除所有长等待。
|
|
13
|
+
|
|
14
|
+
## Verification / 验证
|
|
15
|
+
|
|
16
|
+
- Windows Node 24.21.0: integrated source build and all five underlying test stages — **2,053 passed, 9 skipped, 0 failed**; no orphan native trace children. / Windows 集成测试通过,未留残余子进程。
|
|
17
|
+
- Actual package tarball unpacked and loaded independently: colored and grayscale tracing passed; installed official Electron-as-Node plus real DSH 0.2.2-rc.1 and rc.3 NativeToolExecutor exercised hot/cold uploaded attachments, cross-Session denial and tracing — **8/8** packaged-Host combinations passed. / 以实际 npm 候选包加载并通过官方 Electron 运行时、真实 rc.1/rc.3 Host 的联合测试。
|
|
18
|
+
- The exact release commit must complete the protected full CI and Release workflow; passing a candidate PR is necessary but **not sufficient** for publication. / 仍必须对最终 main 提交执行完整受保护发布门禁。
|
|
19
|
+
|
|
20
|
+
## Compatibility and safe upgrade / 兼容与安全升级
|
|
21
|
+
|
|
22
|
+
- Keep DSH **>=0.2.1-rc.5 <0.3.0-0**, Node.js **>=24.9.0**, and existing Host-owned Session/attachment/Settings authority. No support-floor relaxation or automatic profile migration. / 最低版本与 Host 权限归属不变,不自动升级或迁移 Profile。
|
|
23
|
+
- Before upgrading, back up the DSH profile, relevant attachments and important Session history; run the read-only `doctor --upgrade-preflight`; preserve the v3.2.1 rollback option. / 升级前备份重要资料并只读预检,保留回退到 3.2.1 的办法。
|
|
24
|
+
- Cloud visual inference still sends image content to the selected remote provider unless strict local-only mode is enabled. "Free/no key" does not mean offline. / 云端识图仍会将图像送往供应商;免 Key 不等于离线。
|
|
25
|
+
- Third-party generated Desktop installers remain outside the official cross-platform acceptance evidence. / 第三方代际安装器不包含在官方验收结论中。
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
# v3.3.0 — Native OCR route and resilient visual tools / 原生 OCR 路线与视觉工具稳定性
|
|
2
|
+
|
|
3
|
+
**Publication evidence / 发布状态核实:** This document describes the v3.3.0 release contents; its presence alone never establishes publication. Check the protected Release workflow on the exact merged `main` SHA, immutable GitHub Release/tag, npm `latest` and matching tarball identity/provenance. / 本文记录 3.3.0 的更新内容;是否正式发布须以受保护 Release 工作流、不可变 GitHub Release/tag、npm `latest` 与包体来源证明为准,不能仅凭本文判断。
|
|
4
|
+
|
|
5
|
+
## Why a minor version? / 为什么升为次版本?
|
|
6
|
+
|
|
7
|
+
This release includes a new owner-installed native OCR engine route and a substantial set of security, execution-lifecycle and Host compatibility improvements compared with the last published `v3.2.1`. The previously prepared `v3.2.2` metadata was **never released**; these changes are consolidated into `v3.3.0`, rather than shipping a patch version with an expanded native OCR capability. / 相比已发布的 v3.2.1,增加原生 OCR 路线和较大范围的稳定性/安全增强。未正式发布的 3.2.2 候选不单独上线,统一作为 3.3.0。
|
|
8
|
+
|
|
9
|
+
## Changes since v3.2.1 / 主要变更
|
|
10
|
+
|
|
11
|
+
- **PP-OCRv6 small / ncnn local CPU OCR (#853–#854, #836):** In `vision_ocr(auto)`, prefer a locally **owner-installed and SHA-verified** worker on **macOS ARM64** or **Windows x64**, if the pinned executable and five model assets are actually installed. Otherwise the existing Tesseract compatibility path remains available. Explicit `engine=tesseract` / `engine=vision` still overrides auto. Uncertain but nonempty ncnn text can now request an existing consent- and deadline-controlled vision review; under strict local-only or failed review, the local transcript is returned with uncertainty preserved. / 已安装并校验的本地 ncnn 优先;未安装时仍走兼容路线;显式引擎选择不变;低置信度核查严格受权限、熔断与共同超时限制。
|
|
12
|
+
- **Tesseract compatibility for subtitle text (#853):** Add PSM 7 single-line analysis and bounded grayscale, inversion/scale retry for hard light-on-dark captions, without presenting Tesseract as the primary native OCR target. / 兼容路径支持单行模式与适度反色、放大重试。
|
|
13
|
+
- **Attachment/Session safety and whole-task deadlines (#852, integrating #838–#846, #850–#851):** Unify `attachmentIds` and file paths through Session-authorized image processing, remove cross-Session cache bypasses, start the shared deadline before cold Host lookups, abort noncooperative operations on deadline, and propagate cancellation through provider attempts. Preserve privacy-safe phase diagnostics. / 统一附件读取、修复跨会话缓存授权风险、提前启动统一时限并正确传递取消信号,不泄露完整附件 ID。
|
|
14
|
+
- **Native VTracer containment (#852, incorporating #847–#848):** Move the native/WASM trace job into a bounded child process; accept SVG only after a clean child exit, and fail closed on abnormal exit, timeout, forged/oversized output. This changes process overhead, not the tool API. / VTracer 由受限子进程隔离,避免原生错误直接终止 Host;会有一定启动开销。
|
|
15
|
+
- **Windows reliability (#852, incorporating #845):** Address atomic cache rename and portable tarball identity/test behavior. / 修复 Windows 文件锁、缓存写入与打包回归测试问题。
|
|
16
|
+
- **Release gate repair (3.3.0):** Run the newly introduced native-OCR `node --test` suite as actual tests (not arguments to `license:check`); require both dependency and native-asset notice/license checks in the protected Release metadata gate. Add immutable tests to catch this divergence. / 恢复此前误漏跑的原生 OCR 回归入口,同时保持原生许可证检查不可绕过。
|
|
17
|
+
|
|
18
|
+
## Evidence and known limits / 验证与未覆盖边界
|
|
19
|
+
|
|
20
|
+
- #852 integrated head passed **15/15** GitHub Actions workflows; #853 and #854 each have independent CI evidence. Mac ARM64 real installed PP-OCRv6/ncnn `vision_ocr(auto)` recognized generated Chinese-caption PNG fixtures with both dark-on-light and light-on-dark text correctly. This does **not** represent the original Issue #836 reporter files; the exact reporter's images were not available.
|
|
21
|
+
- Earlier Windows x64 native-worker builds and real Host `vision_ocr(auto)` tests were documented, but a freshly installed Windows worker was not available in the later isolated acceptance session. Actual current 3.3.0 final CI and Release gates must pass; **do not describe this candidate as publicly released before then**.
|
|
22
|
+
- Some legacy Tesseract inputs still misread stylized captions; the engine remains a compatibility fallback, not the native first choice. The previous Issue #841 reporter's specific 120-second environment was not independently reproduced, despite correcting demonstrable deadline/cancellation weaknesses.
|
|
23
|
+
- **Native OCR redistribution is a separate gate:** The npm package includes JavaScript, installer, license texts and integrity metadata, but **does not bundle PP-OCRv6 model weights or native executables**. The lab audit `quality/native-ocr-license-audit-LAB.md` explicitly marks native archive redistribution as **not yet cleared** (clean CI, final notices/SBOM, hosting and platform verification pending). Do **not** attach lab worker/model archives to this GitHub Release or advertise an automatic public download until those gates pass. / npm 仅分发源码相关 JS、安装器和许可文本;原生可执行文件和模型不随 npm 发布,离线包尚未获公开分发放行。
|
|
24
|
+
|
|
25
|
+
## Compatibility and privacy / 兼容与隐私
|
|
26
|
+
|
|
27
|
+
- **DSH:** `>=0.2.1-rc.5 <0.3.0-0`. **Node.js:** `>=24.9.0`. The exact recommended reviewed Host is DSH `0.2.2-rc.1`; rc.2/rc.3 have separate exact-source acceptance evidence. Older rc.2/rc.3 *from the 0.2.1 line* are below the current floor and must not be forced into loading the plugin.
|
|
28
|
+
- **No automatic profile migration**, no change to Host-owned Session/attachment trust boundaries. Back up the DSH profile, Settings, attachments and important Session history; run read-only `doctor --upgrade-preflight`; keep a known-good `v3.2.1` rollback.
|
|
29
|
+
- **Privacy:** Fresh installs still enable an anonymous cloud vision fallback. Images and related request metadata may leave the machine unless strict local-only mode is enabled. Installing a verified native worker does **not** imply the entire vision chain is offline.
|
|
30
|
+
- Third-party generated Desktop installers are not independently qualified merely by the official Host gate. / 第三方打包安装器需要单独验收。
|
|
31
|
+
|
|
32
|
+
## Publication acceptance / 最终发布门禁
|
|
33
|
+
|
|
34
|
+
The reviewed 3.3.0 candidate must pass all CI checks (Node 24.9/24.21 and exact DSH Host matrix), frozen-lockfile install, source/runtime build verification, reproducible package, complete native OCR regression suite, native+VTracer license checks, publication channel `latest`, pre-tag npm registry identity check, immutable main-target tag, npm trusted publishing/provenance, and a post-release npm/GitHub package hash check. No partial pass or green former PR alone authorizes publication. / 最终版本必须以完整 CI、受保护发布流水线和 npm/GitHub 包体哈希一致为准。
|
package/docs/remote-settings.md
CHANGED
|
@@ -1,15 +1,90 @@
|
|
|
1
|
-
#
|
|
1
|
+
# Vision Router settings: one configuration, two Host transports
|
|
2
2
|
|
|
3
|
-
Vision Router
|
|
3
|
+
Vision Router has **one** Host-owned `vision-router` configuration namespace and
|
|
4
|
+
one schema, revision check and persistence authority. It needs two transport
|
|
5
|
+
adapters for historical DSH browser APIs, **not two different sets of editable
|
|
6
|
+
configuration fields**:
|
|
4
7
|
|
|
5
|
-
|
|
8
|
+
- **Local Web / official Desktop:** `settingsScope` when supported, otherwise
|
|
9
|
+
the local ConfigEditor-backed `/_dsh/vision-router/local-settings` bridge.
|
|
10
|
+
The latter is strictly local-only and checks both transport provenance and
|
|
11
|
+
the Host's authenticated browser-session rejection result before any read or
|
|
12
|
+
write. No user-facing remote risk prompt is needed.
|
|
13
|
+
- **Remote Web:** `/vision-router-settings/*` over DSH Connection RPC.
|
|
14
|
+
The authenticated Host carrier is mandatory, and the first disabled
|
|
15
|
+
`describe` triggers the user's explicit risk notice. Accepting persists
|
|
16
|
+
`allowRemoteSettings=true` in the Host profile and immediately refreshes
|
|
17
|
+
the settings. Once enabled, ordinary DVR configuration fields have the same
|
|
18
|
+
editability as on the local page.
|
|
6
19
|
|
|
7
|
-
|
|
20
|
+
The remote transport does **not** maintain a separate capability allow-list for
|
|
21
|
+
ordinary configuration. Network and proxy overrides, local Ollama / LM Studio
|
|
22
|
+
definitions, HTTP provider settings, route names, desktop screenshot preference
|
|
23
|
+
and the `localOnlyVision` privacy switch use the same Host schema and
|
|
24
|
+
authoritative revisioned mutation path after the acknowledgement. The local-only
|
|
25
|
+
privacy switch is visible remotely, so take special care when changing it:
|
|
26
|
+
disabling it can permit image traffic to cloud vision providers. A remote change
|
|
27
|
+
does not itself grant operating-system screen-recording permission.
|
|
8
28
|
|
|
9
|
-
|
|
29
|
+
`allowRemoteSettings` itself is **not** an ordinary remote mutation: it is
|
|
30
|
+
enabled by the risk-confirmation flow and can be revoked from the local settings
|
|
31
|
+
page. It remains opt-in and off by default. Revocation takes effect on the
|
|
32
|
+
next RPC request; it does not erase the prior acknowledgement from history.
|
|
33
|
+
The acknowledgement is a UX safeguard, **not authentication or proof of local
|
|
34
|
+
presence**. DSH `trustedHosts` alone is likewise *not* authentication.
|
|
35
|
+
Browser-session authentication, Host/Origin policy, and the Connection RPC
|
|
36
|
+
contract are the actual access controls.
|
|
10
37
|
|
|
11
|
-
|
|
38
|
+
## Sensitive information and remaining local capabilities
|
|
12
39
|
|
|
13
|
-
|
|
40
|
+
Settings descriptions are requested from DSH with
|
|
41
|
+
`describe({ redactSecrets: true })`. The remote view additionally masks
|
|
42
|
+
secret-shaped properties and URL username/password and secret query parameters
|
|
43
|
+
(e.g., in a proxy URL). API-key environment names such as `apiKeyEnv` are
|
|
44
|
+
references, not actual credential values. A just-submitted secret-bearing field
|
|
45
|
+
may be echoed **only** in that caller's successful, exact-value write response
|
|
46
|
+
to support readback; subsequent reads remain redacted. If editing a URL
|
|
47
|
+
containing masked username/password or secret query parameters, re-enter
|
|
48
|
+
those values first: the server rejects saving a redaction placeholder rather
|
|
49
|
+
than silently replacing the real credential. Never treat the complete
|
|
50
|
+
settings view as a credential-export endpoint.
|
|
14
51
|
|
|
15
|
-
|
|
52
|
+
A full settings editor **does not** grant access to separate Host capabilities
|
|
53
|
+
such as reading/opening log files, plugin self-update, local connection probes,
|
|
54
|
+
local diagnostic mutation endpoints, local file access, or OS permission
|
|
55
|
+
prompts. Those routes retain independent server-side local-only restrictions.
|
|
56
|
+
The `/_dsh/vision-router/local-settings` compatibility endpoint is not an
|
|
57
|
+
alternate remote route and must never be forwarded for external use.
|
|
58
|
+
|
|
59
|
+
## DSH transport compatibility and proxy security
|
|
60
|
+
|
|
61
|
+
Legacy DSH Connection RPC requires the explicit
|
|
62
|
+
`{ authority: 'trusted-host' }` registration option; modern DSH uses
|
|
63
|
+
`connection.requestRejection()` and Host-owned BrowserAuth/Origin checks with
|
|
64
|
+
a two-argument `rpc.handle()`. DVR feature-detects this semantic contract.
|
|
65
|
+
Neither case exposes unauthenticated remote configuration.
|
|
66
|
+
|
|
67
|
+
If using Nginx/Caddy, forward `/vision-router-settings/*` to the same DSH origin
|
|
68
|
+
as the rest of the app. A 404 on this channel means the proxy or plugin runtime
|
|
69
|
+
has not registered/forwarded that route, **not** that the risk prompt needs to be
|
|
70
|
+
clicked again.
|
|
71
|
+
|
|
72
|
+
Follow the [official DSH reverse proxy deployment contract](https://github.com/deepseek-ai/deepseek-harness/blob/d743267388641bc76f17c45ce8b4c231aed1d32c/docs/user/guide/public-deployments.md):
|
|
73
|
+
preserve the browser-facing `Host`, explicitly configure trusted hosts, and
|
|
74
|
+
use HTTPS. The Host's signed browser session authenticates accepted requests
|
|
75
|
+
but cannot prove a user is physically present at the machine. A reverse proxy
|
|
76
|
+
that changes the Host to localhost and removes all forwarding provenance can
|
|
77
|
+
defeat software-only local-presence inference; do not expose that topology.
|
|
78
|
+
See [Issue #680](https://github.com/ysr666/dsh-vision-router/issues/680).
|
|
79
|
+
|
|
80
|
+
## Regression coverage
|
|
81
|
+
|
|
82
|
+
The settings contract tests cover both compatibility-wrapper load orders
|
|
83
|
+
(Issue #822), local ConfigEditor read/write/reconciliation, request-origin and
|
|
84
|
+
BrowserAuth rejection, remote permission-disabled and consented flows, live
|
|
85
|
+
permission revocation, full configuration admission, prototype/resource guards,
|
|
86
|
+
secret redaction, and independent local-only system operations.
|
|
87
|
+
|
|
88
|
+
Historical release and architecture notes describing a remote field allow-list
|
|
89
|
+
document the behavior **at the time of those releases**; this document describes
|
|
90
|
+
the updated behavior after the unified-settings change.
|