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.
Files changed (56) hide show
  1. package/README.md +6 -6
  2. package/README.zh.md +21 -6
  3. package/THIRD_PARTY_NOTICES.md +167 -0
  4. package/assets/licenses/apache-2.0.txt +202 -0
  5. package/assets/licenses/llvm-mingw-LICENSE.txt +279 -0
  6. package/assets/licenses/mingw-w64-runtime-COPYING.txt +265 -0
  7. package/assets/licenses/moxcms-BSD-3-Clause.txt +26 -0
  8. package/assets/licenses/ncnn-LICENSE.txt +86 -0
  9. package/assets/licenses/roots-BSD-2-Clause.txt +24 -0
  10. package/assets/licenses/unicode-ident-Unicode-3.0.txt +39 -0
  11. package/assets/licenses/vtracer-MIT.txt +25 -0
  12. package/assets/licenses/zlib-rs-Zlib.txt +19 -0
  13. package/docs/architecture/dsh-support-window.md +25 -6
  14. package/docs/compatibility/dsh-0.2.2-rc2-audit.md +40 -0
  15. package/docs/compatibility/dsh-0.2.2-rc3-audit.md +131 -0
  16. package/docs/compliance/vtracer-alpha4-provenance.md +47 -0
  17. package/docs/compliance/vtracer-alpha4-reconstructed-Cargo.lock +567 -0
  18. package/docs/compliance/vtracer-alpha4-rust-inventory.json +421 -0
  19. package/docs/compliance/vtracer-alpha4-rust-license-texts.md +13018 -0
  20. package/docs/releases/v3.2.1.md +21 -0
  21. package/docs/releases/v3.2.2.md +25 -0
  22. package/docs/releases/v3.3.0.md +34 -0
  23. package/docs/remote-settings.md +83 -8
  24. package/index.js +280 -169
  25. package/lib/client.js +17 -17
  26. package/lib/core-primitives.js +155 -214
  27. package/lib/dsh-support-window.js +6 -3
  28. package/lib/native-ocr-annotation-risk.js +33 -0
  29. package/lib/native-ocr-canary.js +156 -0
  30. package/lib/native-ocr-chemistry-review.js +37 -0
  31. package/lib/native-ocr-document.js +243 -0
  32. package/lib/native-ocr-installation.js +17 -0
  33. package/lib/native-ocr-integrity.js +93 -0
  34. package/lib/native-ocr-question-labels.js +167 -0
  35. package/lib/native-ocr-supervisor.js +268 -0
  36. package/lib/remote-settings-bridge.js +93 -57
  37. package/lib/remote-settings-risk-client-boundary.js +2 -2
  38. package/lib/runtime-reliability.js +7 -0
  39. package/lib/session-query-readers.js +8 -2
  40. package/lib/session-vision-attachment-index.js +61 -14
  41. package/lib/settings-client-017-compat.js +4 -2
  42. package/lib/settings-ia-client-prelude.js +26 -10
  43. package/lib/tesseract-image-preprocess.js +35 -0
  44. package/lib/trace-vtracer-process-runtime.js +133 -0
  45. package/lib/trace-vtracer-process.js +43 -0
  46. package/lib/trace-vtracer-worker.js +163 -0
  47. package/lib/vision-attachment-handle-runtime.js +11 -2
  48. package/lib/vision-backend-runtime-policy.js +5 -3
  49. package/lib/vision-image-input-reader.js +67 -0
  50. package/lib/vision-image-input-verdict.js +24 -3
  51. package/lib/vision-tool-runtime-boundary.js +7 -10
  52. package/lib/vision-tool-stage.js +58 -0
  53. package/lib/web/dsh-settings-017-root-transport.js +52 -6
  54. package/lib/web-capability-boundary.js +6 -0
  55. package/package.json +10 -6
  56. package/scripts/install-native-ocr.mjs +144 -0
@@ -0,0 +1,24 @@
1
+ Copyright (c) 2015, Mikhail Vorotilov
2
+ All rights reserved.
3
+
4
+ Redistribution and use in source and binary forms, with or without
5
+ modification, are permitted provided that the following conditions are met:
6
+
7
+ * Redistributions of source code must retain the above copyright notice, this
8
+ list of conditions and the following disclaimer.
9
+
10
+ * Redistributions in binary form must reproduce the above copyright notice,
11
+ this list of conditions and the following disclaimer in the documentation
12
+ and/or other materials provided with the distribution.
13
+
14
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
15
+ AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
17
+ DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
18
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
20
+ SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
21
+ CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
22
+ OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
23
+ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
24
+
@@ -0,0 +1,39 @@
1
+ UNICODE LICENSE V3
2
+
3
+ COPYRIGHT AND PERMISSION NOTICE
4
+
5
+ Copyright © 1991-2023 Unicode, Inc.
6
+
7
+ NOTICE TO USER: Carefully read the following legal agreement. BY
8
+ DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING DATA FILES, AND/OR
9
+ SOFTWARE, YOU UNEQUIVOCALLY ACCEPT, AND AGREE TO BE BOUND BY, ALL OF THE
10
+ TERMS AND CONDITIONS OF THIS AGREEMENT. IF YOU DO NOT AGREE, DO NOT
11
+ DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA FILES OR SOFTWARE.
12
+
13
+ Permission is hereby granted, free of charge, to any person obtaining a
14
+ copy of data files and any associated documentation (the "Data Files") or
15
+ software and any associated documentation (the "Software") to deal in the
16
+ Data Files or Software without restriction, including without limitation
17
+ the rights to use, copy, modify, merge, publish, distribute, and/or sell
18
+ copies of the Data Files or Software, and to permit persons to whom the
19
+ Data Files or Software are furnished to do so, provided that either (a)
20
+ this copyright and permission notice appear with all copies of the Data
21
+ Files or Software, or (b) this copyright and permission notice appear in
22
+ associated Documentation.
23
+
24
+ THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
25
+ KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
26
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF
27
+ THIRD PARTY RIGHTS.
28
+
29
+ IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE
30
+ BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES,
31
+ OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
32
+ WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
33
+ ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA
34
+ FILES OR SOFTWARE.
35
+
36
+ Except as contained in this notice, the name of a copyright holder shall
37
+ not be used in advertising or otherwise to promote the sale, use or other
38
+ dealings in these Data Files or Software without prior written
39
+ authorization of the copyright holder.
@@ -0,0 +1,25 @@
1
+ Copyright (c) 2024 TSANG, Hao Fung
2
+
3
+ Permission is hereby granted, free of charge, to any
4
+ person obtaining a copy of this software and associated
5
+ documentation files (the "Software"), to deal in the
6
+ Software without restriction, including without
7
+ limitation the rights to use, copy, modify, merge,
8
+ publish, distribute, sublicense, and/or sell copies of
9
+ the Software, and to permit persons to whom the Software
10
+ is furnished to do so, subject to the following
11
+ conditions:
12
+
13
+ The above copyright notice and this permission notice
14
+ shall be included in all copies or substantial portions
15
+ of the Software.
16
+
17
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF
18
+ ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED
19
+ TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
20
+ PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
21
+ SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
22
+ CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
23
+ OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR
24
+ IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
25
+ DEALINGS IN THE SOFTWARE.
@@ -0,0 +1,19 @@
1
+ (C) 2024 Trifecta Tech Foundation
2
+
3
+ This software is provided 'as-is', without any express or implied
4
+ warranty. In no event will the authors be held liable for any damages
5
+ arising from the use of this software.
6
+
7
+ Permission is granted to anyone to use this software for any purpose,
8
+ including commercial applications, and to alter it and redistribute it
9
+ freely, subject to the following restrictions:
10
+
11
+ 1. The origin of this software must not be misrepresented; you must not
12
+ claim that you wrote the original software. If you use this software
13
+ in a product, an acknowledgment in the product documentation would be
14
+ appreciated but is not required.
15
+
16
+ 2. Altered source versions must be plainly marked as such, and must not be
17
+ misrepresented as being the original software.
18
+
19
+ 3. This notice may not be removed or altered from any source distribution.
@@ -1,6 +1,6 @@
1
1
  # DVR 3.2 DSH Host support window
2
2
 
3
- **Status: 3.2.0-rc.0 development branch; NOT released.** The previous DVR 3.1.x support policy remains available in [historical support window](dsh-support-window-3.1-historical.md).
3
+ **Status: DVR 3.2.x support policy; this document is not a release or npm publication assertion.** The previous DVR 3.1.x support policy remains available in [historical support window](dsh-support-window-3.1-historical.md).
4
4
 
5
5
  | Policy | DVR 3.2 candidate |
6
6
  |---|---|
@@ -14,15 +14,34 @@ The prior DVR 3.1.4 release retains its historic support contract. The new suppo
14
14
 
15
15
  The published `engines.dsh` train allows later 0.2.x releases, including
16
16
  prereleases, as a compatibility *admission policy*; it cannot guarantee their
17
- runtime behavior. Doctor now distinguishes exact-release approval
18
- (0.2.1-rc.5 and 0.2.2-rc.1 on Node 24) from merely being in that range:
19
- future/unpinned 0.2.x Hosts and Node 25+ are marked `unknown`, not `ok`,
20
- until separately validated. This does not rewrite the Host admission range
17
+ runtime behavior. Doctor distinguishes **admitted**, **exact-release verified** and **recommended** Hosts.
18
+ The exact-source/real-Host gates have verified `0.2.1-rc.5`, `0.2.2-rc.1`,
19
+ `0.2.2-rc.2` and `0.2.2-rc.3` on the exercised Node 24 matrix. The conservative
20
+ **recommended** Host remains `0.2.2-rc.1`: verification of a newer prerelease
21
+ is not, by itself, a recommendation to upgrade. Future/unpinned 0.2.x Hosts
22
+ and Node 25+ are marked `unknown`, not `ok`, until separately validated. This does not rewrite the Host admission range
21
23
  or block a user whose separately reviewed deployment works.
22
24
 
25
+ The active compatibility CI is organized by responsibility: the **minimum Host**
26
+ (`0.2.1-rc.5`), the **recommended Host** (`0.2.2-rc.1`) and the **latest
27
+ qualified RC** (`0.2.2-rc.3`) retain normal automated gates. The RC2 full
28
+ matrix is preserved for explicit `workflow_dispatch` replay, with its prior
29
+ immutable verification recorded; it no longer duplicates every PR/main run.
30
+ All three Host gates now run as reusable workflows inside the branch-protected
31
+ `CI` for **Host-impacting changes**: minimum RC5, recommended RC1, and latest RC3.
32
+ Both mandatory `contract` checks wait for their aggregate results and explicitly
33
+ reject failure, cancellation, skipped Host verification, or failed classification.
34
+ A reviewed trusted-base classifier alone can exempt Markdown-only documentation
35
+ or a version-only package change, and in that case all three heavy gates must be
36
+ skipped, never faked as passed. An unexpected/unknown path fails closed to heavy.
37
+ The RC1/RC3 concurrency groups are distinct from CI to prevent self-cancellation.
38
+ This is a CI scheduling policy, not a withdrawal of RC2 compatibility evidence.
39
+ When the recommendation or latest RC advances, move the active lane instead
40
+ of permanently adding another full automatic historical matrix.
41
+
23
42
  ## Core Host ownership
24
43
 
25
- Both DSH 0.2.1-rc.5 and DSH 0.2.2-rc.1 own webStartup trustedHosts and all Connection authorization. DVR 3.2 retires the cross-generation Connection config override and private readiness provider. However, a real Windows six-order foreign-plugin test caught HTTP 405 from generic connection.rpc.handle() when the Connection provider Fiber omitted a webServer injection. Thus DVR retains one **minimal ordering-only patch**: Connection inject: [webStartup, webServer], with **no config/trustedHosts override**. DSH still exclusively owns cookies, /api, WebSocket, trust authority and all other Connection config. Never extend, guess or bypass the official trust list.
44
+ The verified DSH 0.2.1-rc.5 and DSH 0.2.2 release candidates own webStartup trustedHosts and all Connection authorization. DVR 3.2 retires the cross-generation Connection config override and private readiness provider. However, a real Windows six-order foreign-plugin test caught HTTP 405 from generic connection.rpc.handle() when the Connection provider Fiber omitted a webServer injection. Thus DVR retains one **minimal ordering-only patch**: Connection inject: [webStartup, webServer], with **no config/trustedHosts override**. DSH still exclusively owns cookies, /api, WebSocket, trust authority and all other Connection config. Never extend, guess or bypass the official trust list.
26
45
 
27
46
  Keep the independent modules/webServer activation dependency and DVR disabled:false recompose guard until each replacement is independently proven; their root causes are not fixed merely by raising the Host floor.
28
47
 
@@ -0,0 +1,40 @@
1
+ # DSH 0.2.2-rc.2 exact-source compatibility audit
2
+
3
+ ## Immutable basis
4
+
5
+ - Host: `deepseek-ai/deepseek-harness@ddac96760b6edf8fa0fe17cbdcf0b512f4c12b2c` (`dsh-v0.2.2-rc.2`, published 2026-11-11 11:33:06 UTC).
6
+ - DVR baseline: `300ec9828d7769fabd0ae423a4b3331f6b79d462` (`3.2.0`).
7
+ - Prior RC1 Host: `66491b05e3f05ad35bcdd4f6cd7ed26041d9e3db` (`dsh-v0.2.2-rc.1`).
8
+ - This audit is an acceptance candidate, **not** a compatibility certification or release.
9
+
10
+ ## RC2 surface deltas and DVR risks
11
+
12
+ 1. Session gained atomic batch `append([...])`. Its public `session/event(session,event)` contract remains per-event after the entire batch commits. DVR's feed-based vision index, surface repair and model-selection ownership depend on observing each event exactly once; test upstream batch acceptance/observer behavior on the exact release, then test DVR actual Host lifecycles.
13
+ 2. Agent model selection still occurs before `tools.resolve` and `agent/pre-step`. Keep DVR's early inbox-based model selection and verify real image->text route recovery. Never reinstate model changes at `agent/request`.
14
+ 3. Host changes include plugin startup failure handling, tool-error categories, dynamic MCP and LLM retry settings. Verify plugin mount/disposal, tool error propagation, Settings revisioned save/readback and native/Desktop route behavior instead of treating this release note as proof of parity.
15
+ 4. Web/desktop overlay and Settings compatibility shims remain subject to the exact-source contract, authenticated browser lifecycle, cold image/tool activation, mixed attachments and multi-plugin ordering. Do not delete overlays without an upstream-specific red/green proof.
16
+
17
+ ## Exit gates
18
+
19
+ - RC2 pin and workflow static tests; `pnpm build`, `pnpm build:check` and standard DVR tests.
20
+ - RC2 upstream Session append `append.spec.ts` (including atomic rollback, reentry and post-commit observer timing).
21
+ - Three-OS exact Host source and peer/proxy contracts on Node 24.9; no shared untrusted build caches.
22
+ - Real Chromium: cold Vision ON/OFF, mixed paste, Settings/save/reload, bundle recompose, Desktop Host wiring.
23
+ - Real macOS/Windows Desktop model route and reverse-text flow, Windows default tool-only path, multi-plugin ordering on Node 24.9/24.21.
24
+ - Follow-up triage for any failure using first failing product assertion versus infrastructure/bootstrap failure. Until all gates pass, keep the PR draft; no merge, tag or publish.
25
+
26
+ ## Actual acceptance evidence
27
+
28
+ - The previous fully reviewed PR head `fa58884352a5dbc9b0a67d6672262b5e787d98d4` completed [61 checks (59 success, 2 skipped, zero failure)](https://github.com/ysr666/dsh-vision-router/pull/830/checks) and the exact [RC2 Host Gate (six jobs successful)](https://github.com/ysr666/dsh-vision-router/actions/runs/43123077322). This is **historical SHA-specific evidence**, never a waiver for a changed head.
29
+ - On actual RC2 `SessionStore`, the DVR observer/index repaired 272 guards committed in **one** atomic append, with **16** precise overflow reads, **0** whole-log reads, exactly-once surface repair, isolated attachment indices and no dirty state after a failed batch. The upstream Session 14-test batch suite also passed.
30
+ - The current-PR candidate `.tgz` was built and inspected with `verify-packed-public-api.mjs`, then actually installed through the official RC2 CLI Host, with 3 successful bundle recompositions. A source-directory install alone is not the evidence.
31
+ - Real RC2 macOS Desktop, Windows Desktop (Node 24.9 and 24.21), browser cold Vision toggling, Settings save/reload, mixed attachment handling and multi-plugin ordering passed at that SHA.
32
+ - This validates **the PR checkout after later commits**. The published immutable `v3.2.0@676c6d7a` is **not** the audited main baseline `300ec982`: main includes Settings patches #823/#828 and VTracer migration #829 after the tag. A new **advisory-only** step runs the actual published `dsh-vision-router@3.2.0` from npm with an isolated RC2 Host and probes the local Settings transport. Its outcome must be examined separately; it cannot retroactively repair npm 3.2.0 and must not be counted as candidate certification.
33
+ - Issue [#826](https://github.com/ysr666/dsh-vision-router/issues/826) concerns the **Dataelem third-party Desktop generation installer**, not the official DeepSeek Harness Desktop or CLI installer. Its upstream bug [dataelement/dsh-desktop#563](https://github.com/dataelement/dsh-desktop/issues/563) and proposed fix [#565](https://github.com/dataelement/dsh-desktop/pull/565) remain open as of 2026-11-12. We have not tested the reporter's actual installed third-party Desktop; no success claim or issue closure is authorized.
34
+
35
+ ## Status
36
+
37
+ **RC2 current-checkout capability evidence: green at the prior tested head.** Any later commit must pass the full exact RC2 Host Gate again. The immutable npm 3.2.0 historical diagnostic and third-party generation installation are distinct evidence boundaries.
38
+
39
+ **No merge, release, or issue-state changes** follow automatically from this audit. A clean current-head CI matrix and an explicit owner decision remain required.
40
+
@@ -0,0 +1,131 @@
1
+ # DSH 0.2.2-rc.3 immutable-source compatibility audit
2
+
3
+ ## Release identity
4
+
5
+ - Official prerelease: [dsh-v0.2.2-rc.3](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.2.2-rc.3), published **2026-11-13 07:56:55 UTC**.
6
+ - Immutable Git tag target: `38a6a5c965aa99ab525161efb7cc5cf1fe62fced`; RC2 predecessor `ddac96760b6edf8fa0fe17cbdcf0b512f4c12b2c`.
7
+ - DVR candidate baseline: `33429bd39d7302daec1ceb842f3fca145cbea96b` (v3.2.1). This document and PR do **not** authorize merge or publication.
8
+
9
+ ## Audited RC2 → RC3 changes
10
+
11
+ The six upstream commits include an experimental DeepSeek website chat-export importer (new Host route, Session persistence, attachments, authenticated Web upload, client sidebar slot), Windows desktop update restart working-directory fix, CI bubblewrap archive cache changes, and version bumps. This is **not** evidence that the pre-existing DVR Session/Settings/Host contracts remain compatible.
12
+
13
+ - **Host/service injection:** the importer registers its own Remote/connection route, scoped services and bundle. Confirm it neither shadows DVR local Settings routes nor changes plugin mount/dispose ordering.
14
+ - **Session and attachment:** imported sessions and images use upstream-owned persistence. DVR must not take ownership of pending files, import archives, Session binding or attachment binaries. Verify existing event index/guard repair with the exact RC3 SessionStore and no cross-session attachment leakage.
15
+ - **Web/client:** upstream adds `sidebar.session.action` HOC and a third directory-picker flow slot. Verify DVR's composer Vision ON/OFF, sidebar and Settings injection do not interfere with those owners. Imported Session continuation is an upstream feature, not a DVR-owned migration.
16
+ - **Desktop/OS:** Windows installer restart-status fix changes the child process working directory. Run Windows 24.9/24.21 and macOS Desktop smoke; do not extrapolate from the Windows installer fix to runtime correctness.
17
+ - **Security:** do not inherit upstream CI caches or run untrusted fork code; all DSH source checkouts are pinned to the tag target, read-only and credential-free.
18
+
19
+ ## Candidate verification
20
+
21
+ The `dsh-022-rc3-host-gate.yml` reusable workflow is called by branch-protected `CI` for every PR (and separately allows manual replay) with immutable RC3 source on Linux/macOS/Windows, Node 24.9/24.21, source/host-sharp contracts, upstream Session batch tests, DVR event/attachment integration, Agent selection order, peer admission, proxy egress, real Chromium cold Vision/mixed attachments/Settings save-reload-readback, bundle recomposition, packed candidate CLI installation, Desktop Host injection and multi-plugin ordering. The legacy Host floor lanes remain independent; RC3 requires Node >=24.9, and DVR 3.2 does not advertise Node 22 support.
22
+
23
+ Historical published npm `dsh-vision-router@3.2.1` is a separate **advisory-only** diagnostic. The historical package allowlist was amended to admit immutable 3.2.1; an early harness failure must never be misreported as a tested incompatibility. A successful candidate tarball install does not certify third-party Desktop generation installation, and no source CI result can rewrite a published artifact.
24
+
25
+ **Status: the initial RC3 head `5b994d6` passed all six exact-Host jobs; each later PR head must pass its own normal CI before final acceptance.** Do not call RC3 compatible until the real Host, Desktop, Chromium, adversarial and contract jobs pass. Investigate first failing product assertions before considering a code fix. No release or merge is authorized.
26
+
27
+ ## Maintainable qualification policy
28
+
29
+ Normal CI retains the supported minimum Host, conservative recommended RC1,
30
+ and latest qualified RC3 as distinct evidence boundaries. The validated RC2
31
+ workflow remains available through explicit manual replay, not every main push
32
+ or ordinary PR. This avoids retiring RC2's evidence while preventing each
33
+ upstream prerelease from permanently adding another six-job automatic matrix.
34
+ Doctor reports RC1/RC2/RC3 as exact-version verified only when runtime
35
+ attachment capabilities are confirmed on Node 24; recommending an upgrade
36
+ remains a separate policy decision, with RC1 still recommended. New DSH
37
+ versions do not become verified solely by satisfying `engines.dsh`.
38
+
39
+ ## Required fail-closed acceptance
40
+ The latest exact RC is invoked as a reusable workflow by the existing `CI` workflow.
41
+ Both branch-protected `contract (24.9.0)` and `contract (24.21.0)`
42
+ checks depend on the complete six-job Host gate, explicitly failing if it
43
+ fails, is cancelled, or is skipped. They cannot silently succeed because a
44
+ separate optional Host workflow failed or was never triggered. The reusable
45
+ workflow has an isolated concurrency group to avoid canceling its CI caller.
46
+ This preserves existing required check names without repository ruleset edits.
47
+
48
+ This previously invoked the latest Host for documentation-only PRs. The
49
+ three-tier convergence below adds a trusted-base impact classifier: only
50
+ non-runtime Markdown and version-only package metadata can skip the heavy
51
+ Host matrices. An unknown, failed or inconsistent classifier fails closed.
52
+
53
+ ## Required coverage of minimum, recommended, and latest
54
+
55
+ The follow-up CI convergence on the same draft PR removes the older
56
+ standalone automatic RC5/RC1 gates, retaining their full immutable reusable
57
+ workflows and manual replay. Protected `CI` now qualifies all three named
58
+ Host contracts for runtime or unclassified changes. The two protected
59
+ `contract` statuses require all three successful results; a failed or missing
60
+ trusted-base impact classification fails closed. Only reviewed Markdown-only
61
+ documentation and version-only package metadata can bypass these expensive
62
+ matrices. The decision is made using the classifier at the PR's protected base
63
+ commit, not modifiable PR-head code. Non-host changes still run the protected
64
+ Node 24 `test` and `contract` checks.
65
+
66
+ The change deliberately avoids doubling the Host job count: it moves the
67
+ previous separate minimum/recommended matrices under the existing required
68
+ CI rather than running new copies. Exact qualification and original run URLs
69
+ remain preserved by immutable refs in this audit/PR history.
70
+
71
+ ## Durable acceptance evidence ledger
72
+
73
+ This source-controlled summary remains in the Git history after hosted
74
+ Actions logs expire. It preserves verified commit and source identities,
75
+ verification scope, official run links and outcome; it is not a substitute
76
+ for permanently archived full logs or a guarantee for untested workflows.
77
+
78
+ | Verified DVR candidate | Immutable Host identity | Real verification | Recorded outcome |
79
+ | --- | --- | --- | --- |
80
+ | [4dfba17fadfbe21305083054a44dcbbc773212ef](https://github.com/ysr666/dsh-vision-router/commit/4dfba17fadfbe21305083054a44dcbbc773212ef) | DSH 0.2.2-rc.3 @ 38a6a5c965aa99ab525161efb7cc5cf1fe62fced | [Protected CI run #43416019566](https://github.com/ysr666/dsh-vision-router/actions/runs/43416019566): six exact RC3 Host jobs (Linux/macOS/Windows, real Chromium, Windows Node 24.9/24.21), core/contract checks | 16 of 16 workflows succeeded |
81
+ | [4dfba17fadfbe21305083054a44dcbbc773212ef](https://github.com/ysr666/dsh-vision-router/commit/4dfba17fadfbe21305083054a44dcbbc773212ef) | DSH 0.2.1-rc.5 @ b830ec950faba0a46dda564be3e2d854afed94f1 | [Minimum Host run #43416019215](https://github.com/ysr666/dsh-vision-router/actions/runs/43416019215) | Success |
82
+ | [4dfba17fadfbe21305083054a44dcbbc773212ef](https://github.com/ysr666/dsh-vision-router/commit/4dfba17fadfbe21305083054a44dcbbc773212ef) | DSH 0.2.2-rc.1 @ 66491b05e3f05ad35bcdd4f6cd7ed26041d9e3db | [Recommended Host run #43416019244](https://github.com/ysr666/dsh-vision-router/actions/runs/43416019244) | Success |
83
+ | [d4ea0f973a9daeb8376fcc6abcad9af9396a1fd6](https://github.com/ysr666/dsh-vision-router/commit/d4ea0f973a9daeb8376fcc6abcad9af9396a1fd6) | DSH 0.2.2-rc.3 | [Chromium job #131828321004](https://github.com/ysr666/dsh-vision-router/actions/runs/43408342770/job/131828321004): published npm 3.2.1, packed candidate, source, three recompositions each | All three install forms succeeded |
84
+
85
+ **Evidence boundary:** the new three-tier protected CI changes postdate the
86
+ above successfully verified heads and must independently pass on their final
87
+ commit. These immutable prior successes do not pre-certify a newer PR head.
88
+
89
+ ## Required process for the next upstream Host RC
90
+
91
+ 1. Pin the *official immutable* upstream tag target and review Host ABI,
92
+ Session, Web, model selection, image ownership, and security changes.
93
+ 2. Promote the new latest exact workflow through protected CI. Keep the old
94
+ latest source pin and run references available for manual replay, but do
95
+ not permanently duplicate its full automatic matrix.
96
+ 3. Preserve both minimum and recommended exact Host obligations until an
97
+ explicit supported-window policy change is approved.
98
+ 4. Run real three-OS, Chromium and Windows Node 24.9/24.21 Desktop gates,
99
+ with fail-closed trusted-base classification and required contract checks.
100
+ 5. Update Doctor's exact verified-version evidence only after a successful
101
+ immutable real-Host gate; update the recommended version separately.
102
+ 6. Record the **tested DVR SHA**, **DSH SHA**, **CI run/job IDs**, supported
103
+ scope, limitations and findings in this ledger and in the PR description.
104
+ A passing semver range or a source-only pin is never runtime proof.
105
+
106
+
107
+ ## No-worktree trust-boundary hardening (CodeQL follow-up)
108
+
109
+ The protected `CI` impact classifier no longer uses `actions/checkout` at
110
+ all. In a fresh empty Git repository it fetches only the trusted base SHA
111
+ and the official base-repository `refs/pull/<number>/head`, verifies that
112
+ ref is **exactly** the event's pinned PR head SHA, and fails closed if the
113
+ PR moved. It extracts the classifier script from the immutable base Git tree,
114
+ while the untrusted head supplies only `package.json` data and path diffs.
115
+ No worktree, PR action or installation script from the head is executed.
116
+ No credentials or privileged GitHub token are needed for this public repo.
117
+ The source-controlled security contract tests assert the absence of checkout
118
+ and the SHA fence. The new commit must separately pass its own GitHub Actions
119
+ and CodeQL annotations; prior green checks are not proof the alert is closed.
120
+
121
+ ## API-only Host impact classification (CodeQL follow-up)
122
+
123
+ The CodeQL medium rule models PR-head Git fetch as well as `actions/checkout`.
124
+ The protected CI classifier no longer fetches PR Git refs or checks out a
125
+ worktree. Instead its read-only token (`contents: read` and `pull-requests:
126
+ read`) retrieves pinned contents and complete changed-path metadata from
127
+ GitHub API. It checks the PR base/head SHAs both before and after reading the
128
+ files, refuses missing/incomplete results, treats every rename/copy/unknown
129
+ status and PRs above 100 files as **heavy**, and only executes the classifier
130
+ from the immutable trusted base. SHA races/API failures fail protected CI
131
+ closed. New head CI and CodeQL alert adjudication are separate obligations.
@@ -0,0 +1,47 @@
1
+ # VTracer 1.0.0-alpha.4: pinned artifact and compliance record
2
+
3
+ Verified 2026-11-11 on Windows Node 24.21.0 and macOS arm64 Node 24.5.0.
4
+
5
+ ## Release coordinates
6
+
7
+ - npm package: @visioncortex/vtracer@1.0.0-alpha.4
8
+ - npm published timestamp: 2026-08-29T00:08:36.284Z
9
+ - npm gitHead and upstream tag 1.0.0-alpha.4 commit: 2500df76b5aea0ac22d15296b22722442f825c5b
10
+ - npm package integrity (sha512): Hhi+vfG4ealLH1m9alrWo1lM00cWFfur4zeLEcNtzrYUjeEYTgukLNfvOXmuaGe2adugu+jl9o9IUzqHuqFO9g==
11
+ - npm package unpacked: 8 files / 692673 bytes, includes pkg/vtracer_wasm_bg.wasm
12
+ - wasm file size: 668378 bytes
13
+ - wasm SHA-256: 63716b70497b7468ef97545b50f5f34b8bbb7acde2d7b00deb4eb40781446d45
14
+ - Windows and macOS installed WASM hashes match exactly.
15
+ - The source commit and release are aligned through npm gitHead, not by an independent byte-identical source reproduction.
16
+
17
+ ## Rust dependency audit
18
+
19
+ - Source checkout pinned to the exact npm commit and tag, not the repository default branch.
20
+ - Node/WASM subproject: nodejs/Cargo.toml, platform wasm32-unknown-unknown.
21
+ - An independently resolved Cargo dependency graph contains 66 reachable normal/build nodes, all with SPDX license metadata and no declared GPL/LGPL/AGPL.
22
+ - Inventory: vtracer-alpha4-rust-inventory.json.
23
+ - Resolved lock: vtracer-alpha4-reconstructed-Cargo.lock.
24
+ - Explicit Unicode-3.0 conjunctive license: unicode-ident@1.0.27.
25
+ - The exact tagged source **does not track nodejs/Cargo.lock**. The included reconstructed lock is a reproducible *new resolution*, not an assertion about the versions used to produce the historical npm prebuilt WASM.
26
+
27
+ ## Distribution notices and controls
28
+
29
+ - Upstream source tag has MIT text (root LICENSE). Original npm tarball has **no LICENSE/NOTICE**.
30
+ - DVR carries the upstream MIT text and additional relevant Rust license texts in assets/licenses/; THIRD_PARTY_NOTICES.md is in the npm package files list.
31
+ - pnpm license:check enforces the known npm integrity, installed WASM hash, no Potrace/Jimp closure, allowed SPDX license tokens and required notices.
32
+
33
+ ## Independently rebuilt WASM (2026-11-11)
34
+
35
+ - On macOS Apple Silicon, Rust 1.97.1 successfully compiled the exact source tag for wasm32-unknown-unknown in release mode using the reconstructed pinned Cargo.lock.
36
+ - Raw compiler WASM SHA-256: 9812bfa008e7f54d59cd4e9823db44acfa1fbc1921e0b03f5494dfd5efd4840f.
37
+ - wasm-bindgen CLI 0.2.130 generated loadable Node bindings from the reconstructed Rust WASM.
38
+ - Rebuilt wasm-bindgen processed WASM SHA-256: aed7bba50a05cd773aa2d9a16f1d6521e695e4473b630ac2800a0c405da346ca.
39
+ - The rebuilt WASM exports vectorize_bytes and vectorize_rgba and can be loaded by Node.
40
+ - A 96x64 RGBA synthetic image passed an identical SVG output comparison between source-rebuilt and npm-distributed VTracer (matching SHA-256 prefix 6a68ed1e9946ce85).
41
+ - The rebuilt WASM is not byte-identical to the npm binary (different file sizes and hashes), so this is a source-build and functional-equivalence check, not historical reproducibility proof.
42
+
43
+ ## Scope and remaining provenance limitation
44
+
45
+ The original npm-provided WASM cannot be claimed as reproducibly built from the historical Rust graph without the publisher's build receipt/toolchain/lock or a byte-identical rebuild. Pinning the package, source commit, integrity and WASM hash makes the exact redistributed artifact auditable, but does not eliminate that provenance limitation.
46
+
47
+ Before release: run the new package's true clean-install tests across Windows/macOS/Linux and verify supported official Host; test Dataelem's separate generation installer when accessible. Do not treat a normal npm/pnpm install as proof of that separate installer.