@foggy-projects/deepseek-harness-plugin 0.4.2-rc.3 → 0.4.4-rc.1

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 (52) hide show
  1. package/README.md +222 -173
  2. package/THIRD-PARTY-RUNTIME-NOTICES.md +16 -16
  3. package/cordis.patch.yml +6 -6
  4. package/docs/COMMUNITY-MARKETPLACES.md +64 -64
  5. package/docs/PUBLIC-BETA-READINESS.md +109 -109
  6. package/docs/RELEASE-CANDIDATE-0.4.0-RC.2.md +38 -38
  7. package/docs/RELEASE-CANDIDATE-0.4.0-RC.3.md +18 -18
  8. package/docs/RELEASE-CANDIDATE-0.4.1-DSH-0.1.5-RC.1.md +60 -60
  9. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.1.md +62 -62
  10. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.2.md +50 -50
  11. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.3.md +34 -34
  12. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.4.md +32 -0
  13. package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.5.md +27 -0
  14. package/docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md +96 -0
  15. package/docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md +135 -0
  16. package/docs/WINDOWS-BETA-ACCEPTANCE.md +113 -113
  17. package/experience/linux/README.md +53 -53
  18. package/experience/linux/prepare.sh +2 -2
  19. package/lib/atomic-json.js +41 -41
  20. package/lib/client.js +1222 -906
  21. package/lib/component-manager.js +164 -0
  22. package/lib/component-releases.js +363 -0
  23. package/lib/diagnostics.js +86 -86
  24. package/lib/index.js +764 -698
  25. package/lib/operation-lock.js +139 -0
  26. package/lib/python-runtime.js +339 -339
  27. package/lib/query-tool.js +134 -104
  28. package/lib/remote-descriptor.js +74 -59
  29. package/lib/remote.js +8 -8
  30. package/lib/runtime-settings.js +89 -89
  31. package/lib/skill-provider.js +116 -116
  32. package/lib/typert.js +9 -9
  33. package/lib/version.js +20 -20
  34. package/lib/viewer-preview.js +44 -27
  35. package/package.json +25 -15
  36. package/skills/foggy-deepseek-onboarding/SKILL.md +149 -143
  37. package/skills/foggy-deepseek-onboarding/assets/connection.schema.json +48 -48
  38. package/skills/foggy-deepseek-onboarding/assets/datasource.example.json +14 -14
  39. package/skills/foggy-deepseek-onboarding/assets/env.example +14 -14
  40. package/skills/foggy-deepseek-onboarding/assets/onboarding-state.schema.json +71 -71
  41. package/skills/foggy-deepseek-onboarding/assets/semantic-plan.example.json +8 -8
  42. package/skills/foggy-deepseek-onboarding/assets/semantic-plan.schema.json +21 -21
  43. package/skills/foggy-deepseek-onboarding/assets/versions.json +23 -23
  44. package/skills/foggy-deepseek-onboarding/references/onboarding-workflow.md +168 -168
  45. package/skills/foggy-deepseek-onboarding/scripts/doctor.ps1 +4 -4
  46. package/skills/foggy-deepseek-onboarding/scripts/install.ps1 +4 -4
  47. package/skills/foggy-deepseek-onboarding/scripts/invoke-onboarding.ps1 +32 -32
  48. package/skills/foggy-deepseek-onboarding/scripts/onboard.ps1 +4 -4
  49. package/skills/foggy-deepseek-onboarding/scripts/onboarding.py +3721 -3681
  50. package/skills/foggy-deepseek-onboarding/scripts/runtime-start.ps1 +4 -4
  51. package/skills/foggy-deepseek-onboarding/scripts/runtime-stop.ps1 +4 -4
  52. package/skills/foggy-deepseek-onboarding/scripts/uninstall.ps1 +4 -4
@@ -1,109 +1,109 @@
1
- # Public beta readiness: 0.4.0-rc.2
2
-
3
- Assessment date: 2026-09-05
4
-
5
- ## Verdict
6
-
7
- `0.4.0-rc.2` is suitable for a scoped public beta on Windows 10/11 x64 and
8
- Linux/WSL2 x64. It is not a general-availability release.
9
-
10
- The plugin package stays small and downloads large components only during
11
- initialization. Node.js and Java remain system prerequisites. Python 3.12.13 is
12
- installed privately below Foggy's component directory and does not change the
13
- system PATH, registry, or a user's existing Python installation.
14
-
15
- ## Verified behavior
16
-
17
- - The npm tarball is about 83 KB compressed and contains no Python or Java
18
- runtime binary.
19
- - Managed CPython assets are pinned by URL, byte size, and SHA256 for Windows,
20
- Linux, and macOS on x64 and arm64.
21
- - The component installer code is unchanged from beta.9, whose Windows x64 run
22
- completed a cold Python download, checksum verification, extraction,
23
- initialization, forced Python repair, and doctor run.
24
- - DeepSeek Harness `0.1.2-rc.1` loaded the beta.12 candidate Bundle, web client,
25
- remote status service, and native Skill provider on both Windows and WSL2.
26
- - WSL2 reported the existing managed Python, CLI, Launcher, and analysis Skill
27
- as ready; an isolated Windows profile correctly reported its fresh component
28
- state and rejected the host's Java 12 as below the Java 17 prerequisite.
29
- - Onboarding is development-first: a direct password or Agent environment
30
- variable is submitted to the public datasource API of an already-running
31
- Runtime. The password is excluded from onboarding state and evidence, and
32
- datasource setup does not trigger Runtime restart. Opaque profiles remain an
33
- optional advanced path.
34
- - A real Launcher 0.1.21 smoke on Java 17 accepted a synthetic inline-password
35
- datasource through the public Runtime API while retaining the same Java PID.
36
- The isolated registry confirmed the documented local-development plaintext
37
- persistence boundary; the test datasource was then removed and the temporary
38
- Runtime stopped.
39
- - A full isolated `onboard-datasource-run` then created, tested, bound, and
40
- inspected a SQLite datasource containing one table. Runtime retained the same
41
- PID, while the persisted onboarding state and command evidence contained no
42
- copy of the synthetic password.
43
- - The package and settings contract report Python 3.12.13 as `Foggy private`,
44
- CLI 0.1.23, Launcher 0.1.21, analysis/query Skills 0.1.18, and onboarding Skill
45
- 0.4.0-rc.2; the same component display was accepted in the preceding
46
- native Windows beta run.
47
- - Runtime startup now reports the current phase, elapsed/timeout seconds, and a
48
- bounded progress value. A real Windows launch with Temurin 17 reached readiness
49
- and passed capabilities in 18.9 seconds. A controlled post-launch Java exit was
50
- detected after about 1 second instead of waiting for the 180-second deadline;
51
- a restored healthy launch then passed again in 15.9 seconds.
52
- - Diagnostic export success remains visible alongside a prior Runtime startup
53
- error, including the generated local JSON path. Exported failures include
54
- bounded sanitized Runtime log tails and reject log paths outside the managed
55
- Runtime directory.
56
- - Runtime port configuration is persisted below the private Foggy data root and
57
- defaults to `18166`. The settings UI validates `1024–65535`, prevents changes
58
- while Runtime is active, and shows port conflicts as an assertive, red bordered
59
- alert. Preflight now checks `0.0.0.0` with exclusive Windows binding semantics,
60
- matching the Java server closely enough to detect address-specific `portproxy`
61
- conflicts that a loopback-only probe missed.
62
- - Interrupted downloads resume with HTTP Range when the server supports it;
63
- downloaded artifacts are not trusted until the complete SHA256 matches.
64
- - Windows progress writes tolerate transient sharing violations without losing
65
- the previous valid progress document or leaving temporary files behind.
66
- - Current automated regression passes 20 Node tests and 29 Python tests. The
67
- new datasource tests cover secret-free persisted state, direct Runtime API
68
- submission, CLI bypass for inline development credentials, stable inline
69
- credential resumption, bounded transient connection retry, and output redaction.
70
- - A real Java 17 / Launcher 0.1.21 regression resumed the same completed inline
71
- datasource composite twice, retained the Runtime PID, and emitted a complete
72
- `01` through `06` workspace evidence sequence without falling back to granular
73
- commands.
74
- - A separate recovery regression completed a SQLite onboarding composite,
75
- removed the managed datasource outside the wrapper, and reran the same
76
- composite. The wrapper detected the missing live datasource, reset only the
77
- three dependent checkpoints, recreated and tested the datasource, rebound the
78
- namespace, and rediscovered the selected table successfully.
79
- - The full release rehearsal converted an inspected 126-column TMS order table
80
- into versioned TM/QM source, passed eight development question-bank cases,
81
- deployed the exact Git-tagged source to a separate Ubuntu host, published the
82
- bundle, and passed the same question bank before and after a Runtime restart.
83
- The remote Runtime retained its datasource binding, active bundle, query
84
- model, and 11-tool MCP surface after restart.
85
-
86
- ## Beta boundaries
87
-
88
- - Supported public-beta targets: Windows 10/11 x64 and Linux/WSL2 x64.
89
- - Windows users must install a supported system Node.js line (`^22.19.0` or
90
- `>=24.0.0`) and Java 17 or later. They do not need to install Python.
91
- - macOS and arm64 assets are pinned and integrity-checked but have not received
92
- the same end-to-end host validation; treat those targets as experimental.
93
- - DeepSeek Harness itself is consumed at `0.1.2-rc.1`. Its authenticated Web UI
94
- launch URL, plugin installation, and supply-chain policy behavior may change
95
- before a stable Harness release.
96
- - Runtime production authentication is outside this beta's default local
97
- onboarding mode. The UI and doctor continue to report `productionReady=false`
98
- for the development-only no-auth mode.
99
- - Direct development passwords are stored by the current Runtime in its private
100
- local datasource registry. Production publication is a separate manual or
101
- future dedicated deployment workflow and should use the target environment's
102
- credential controls.
103
-
104
- ## Release gate after publication
105
-
106
- Before broad announcement, complete the native Windows fresh-machine checklist
107
- in [WINDOWS-BETA-ACCEPTANCE.md](./WINDOWS-BETA-ACCEPTANCE.md). Record the exact
108
- Node, Java, DeepSeek Harness, and plugin versions and confirm that initialization
109
- works without a system Python executable.
1
+ # Public beta readiness: 0.4.0-rc.2
2
+
3
+ Assessment date: 2026-09-05
4
+
5
+ ## Verdict
6
+
7
+ `0.4.0-rc.2` is suitable for a scoped public beta on Windows 10/11 x64 and
8
+ Linux/WSL2 x64. It is not a general-availability release.
9
+
10
+ The plugin package stays small and downloads large components only during
11
+ initialization. Node.js and Java remain system prerequisites. Python 3.12.13 is
12
+ installed privately below Foggy's component directory and does not change the
13
+ system PATH, registry, or a user's existing Python installation.
14
+
15
+ ## Verified behavior
16
+
17
+ - The npm tarball is about 83 KB compressed and contains no Python or Java
18
+ runtime binary.
19
+ - Managed CPython assets are pinned by URL, byte size, and SHA256 for Windows,
20
+ Linux, and macOS on x64 and arm64.
21
+ - The component installer code is unchanged from beta.9, whose Windows x64 run
22
+ completed a cold Python download, checksum verification, extraction,
23
+ initialization, forced Python repair, and doctor run.
24
+ - DeepSeek Harness `0.1.2-rc.1` loaded the beta.12 candidate Bundle, web client,
25
+ remote status service, and native Skill provider on both Windows and WSL2.
26
+ - WSL2 reported the existing managed Python, CLI, Launcher, and analysis Skill
27
+ as ready; an isolated Windows profile correctly reported its fresh component
28
+ state and rejected the host's Java 12 as below the Java 17 prerequisite.
29
+ - Onboarding is development-first: a direct password or Agent environment
30
+ variable is submitted to the public datasource API of an already-running
31
+ Runtime. The password is excluded from onboarding state and evidence, and
32
+ datasource setup does not trigger Runtime restart. Opaque profiles remain an
33
+ optional advanced path.
34
+ - A real Launcher 0.1.21 smoke on Java 17 accepted a synthetic inline-password
35
+ datasource through the public Runtime API while retaining the same Java PID.
36
+ The isolated registry confirmed the documented local-development plaintext
37
+ persistence boundary; the test datasource was then removed and the temporary
38
+ Runtime stopped.
39
+ - A full isolated `onboard-datasource-run` then created, tested, bound, and
40
+ inspected a SQLite datasource containing one table. Runtime retained the same
41
+ PID, while the persisted onboarding state and command evidence contained no
42
+ copy of the synthetic password.
43
+ - The package and settings contract report Python 3.12.13 as `Foggy private`,
44
+ CLI 0.1.23, Launcher 0.1.21, analysis/query Skills 0.1.18, and onboarding Skill
45
+ 0.4.0-rc.2; the same component display was accepted in the preceding
46
+ native Windows beta run.
47
+ - Runtime startup now reports the current phase, elapsed/timeout seconds, and a
48
+ bounded progress value. A real Windows launch with Temurin 17 reached readiness
49
+ and passed capabilities in 18.9 seconds. A controlled post-launch Java exit was
50
+ detected after about 1 second instead of waiting for the 180-second deadline;
51
+ a restored healthy launch then passed again in 15.9 seconds.
52
+ - Diagnostic export success remains visible alongside a prior Runtime startup
53
+ error, including the generated local JSON path. Exported failures include
54
+ bounded sanitized Runtime log tails and reject log paths outside the managed
55
+ Runtime directory.
56
+ - Runtime port configuration is persisted below the private Foggy data root and
57
+ defaults to `18166`. The settings UI validates `1024–65535`, prevents changes
58
+ while Runtime is active, and shows port conflicts as an assertive, red bordered
59
+ alert. Preflight now checks `0.0.0.0` with exclusive Windows binding semantics,
60
+ matching the Java server closely enough to detect address-specific `portproxy`
61
+ conflicts that a loopback-only probe missed.
62
+ - Interrupted downloads resume with HTTP Range when the server supports it;
63
+ downloaded artifacts are not trusted until the complete SHA256 matches.
64
+ - Windows progress writes tolerate transient sharing violations without losing
65
+ the previous valid progress document or leaving temporary files behind.
66
+ - Current automated regression passes 20 Node tests and 29 Python tests. The
67
+ new datasource tests cover secret-free persisted state, direct Runtime API
68
+ submission, CLI bypass for inline development credentials, stable inline
69
+ credential resumption, bounded transient connection retry, and output redaction.
70
+ - A real Java 17 / Launcher 0.1.21 regression resumed the same completed inline
71
+ datasource composite twice, retained the Runtime PID, and emitted a complete
72
+ `01` through `06` workspace evidence sequence without falling back to granular
73
+ commands.
74
+ - A separate recovery regression completed a SQLite onboarding composite,
75
+ removed the managed datasource outside the wrapper, and reran the same
76
+ composite. The wrapper detected the missing live datasource, reset only the
77
+ three dependent checkpoints, recreated and tested the datasource, rebound the
78
+ namespace, and rediscovered the selected table successfully.
79
+ - The full release rehearsal converted an inspected 126-column TMS order table
80
+ into versioned TM/QM source, passed eight development question-bank cases,
81
+ deployed the exact Git-tagged source to a separate Ubuntu host, published the
82
+ bundle, and passed the same question bank before and after a Runtime restart.
83
+ The remote Runtime retained its datasource binding, active bundle, query
84
+ model, and 11-tool MCP surface after restart.
85
+
86
+ ## Beta boundaries
87
+
88
+ - Supported public-beta targets: Windows 10/11 x64 and Linux/WSL2 x64.
89
+ - Windows users must install a supported system Node.js line (`^22.19.0` or
90
+ `>=24.0.0`) and Java 17 or later. They do not need to install Python.
91
+ - macOS and arm64 assets are pinned and integrity-checked but have not received
92
+ the same end-to-end host validation; treat those targets as experimental.
93
+ - DeepSeek Harness itself is consumed at `0.1.2-rc.1`. Its authenticated Web UI
94
+ launch URL, plugin installation, and supply-chain policy behavior may change
95
+ before a stable Harness release.
96
+ - Runtime production authentication is outside this beta's default local
97
+ onboarding mode. The UI and doctor continue to report `productionReady=false`
98
+ for the development-only no-auth mode.
99
+ - Direct development passwords are stored by the current Runtime in its private
100
+ local datasource registry. Production publication is a separate manual or
101
+ future dedicated deployment workflow and should use the target environment's
102
+ credential controls.
103
+
104
+ ## Release gate after publication
105
+
106
+ Before broad announcement, complete the native Windows fresh-machine checklist
107
+ in [WINDOWS-BETA-ACCEPTANCE.md](./WINDOWS-BETA-ACCEPTANCE.md). Record the exact
108
+ Node, Java, DeepSeek Harness, and plugin versions and confirm that initialization
109
+ works without a system Python executable.
@@ -1,38 +1,38 @@
1
- # Foggy DeepSeek Harness plugin 0.4.0-rc.2 release candidate
2
-
3
- Assessment date: 2026-09-06
4
-
5
- ## Decision
6
-
7
- This build is a public preview for Windows 10/11 x64 and Linux/WSL2 x64. It
8
- remains a development and evaluation plugin; the bundled Runtime defaults are
9
- not a production security profile.
10
-
11
- No Java engine or `foggy-runtime-cli` source was changed for this candidate.
12
- The plugin consumes the independently accepted CLI 0.1.23, Runtime Launcher
13
- 0.1.21, foggy-ai-analysis Skill 0.1.18, and foggy-semantic-query Skill 0.1.18
14
- public releases.
15
-
16
- ## Delta from rc.1
17
-
18
- - Upgrade Runtime Launcher from 0.1.20 to 0.1.21.
19
- - Upgrade foggy-ai-analysis from 0.1.17 to 0.1.18.
20
- - Install and register foggy-semantic-query 0.1.18 as a second managed Skill.
21
- - Keep DeepSeek Harness 0.1.2-rc.1, managed Python 3.12.13, CLI 0.1.23, and the
22
- default Runtime port 18166 unchanged.
23
-
24
- The new public assets and their nested Skill manifests were independently
25
- checksum-verified. Runtime acceptance covered automatic static-dictionary
26
- captions, label-to-code filtering, dictionary member enumeration, self-date
27
- dimensions, and the `$year`, `$month`, and `$yearMonth` describe/query path.
28
-
29
- ## Publication gate
30
-
31
- The plugin's existing automated tests and npm tarball inspection must pass.
32
- The Runtime functional matrix is not repeated because the exact public
33
- Launcher and Skill assets were accepted independently before this pin update.
34
-
35
- DeepSeek Harness minimum-release-age policy can reject a recently published
36
- version still present in a profile lockfile. Users should inspect and rebuild
37
- the profile lockfile or wait for the policy window rather than weakening
38
- plugin integrity checks.
1
+ # Foggy DeepSeek Harness plugin 0.4.0-rc.2 release candidate
2
+
3
+ Assessment date: 2026-09-06
4
+
5
+ ## Decision
6
+
7
+ This build is a public preview for Windows 10/11 x64 and Linux/WSL2 x64. It
8
+ remains a development and evaluation plugin; the bundled Runtime defaults are
9
+ not a production security profile.
10
+
11
+ No Java engine or `foggy-runtime-cli` source was changed for this candidate.
12
+ The plugin consumes the independently accepted CLI 0.1.23, Runtime Launcher
13
+ 0.1.21, foggy-ai-analysis Skill 0.1.18, and foggy-semantic-query Skill 0.1.18
14
+ public releases.
15
+
16
+ ## Delta from rc.1
17
+
18
+ - Upgrade Runtime Launcher from 0.1.20 to 0.1.21.
19
+ - Upgrade foggy-ai-analysis from 0.1.17 to 0.1.18.
20
+ - Install and register foggy-semantic-query 0.1.18 as a second managed Skill.
21
+ - Keep DeepSeek Harness 0.1.2-rc.1, managed Python 3.12.13, CLI 0.1.23, and the
22
+ default Runtime port 18166 unchanged.
23
+
24
+ The new public assets and their nested Skill manifests were independently
25
+ checksum-verified. Runtime acceptance covered automatic static-dictionary
26
+ captions, label-to-code filtering, dictionary member enumeration, self-date
27
+ dimensions, and the `$year`, `$month`, and `$yearMonth` describe/query path.
28
+
29
+ ## Publication gate
30
+
31
+ The plugin's existing automated tests and npm tarball inspection must pass.
32
+ The Runtime functional matrix is not repeated because the exact public
33
+ Launcher and Skill assets were accepted independently before this pin update.
34
+
35
+ DeepSeek Harness minimum-release-age policy can reject a recently published
36
+ version still present in a profile lockfile. Users should inspect and rebuild
37
+ the profile lockfile or wait for the policy window rather than weakening
38
+ plugin integrity checks.
@@ -1,18 +1,18 @@
1
- # Foggy DeepSeek Harness plugin 0.4.0-rc.3 release candidate
2
-
3
- Assessment date: 2026-09-06
4
-
5
- ## Delta from rc.2
6
-
7
- - Add a single **Initialize and start** action for first use.
8
- - Add **Update components** and **Update and start** actions for managed CLI,
9
- Launcher, and Skill assets after a plugin-package upgrade.
10
- - Show current versus target component versions and an explicit update banner.
11
- - Block component update/repair while Runtime is running; the active Launcher
12
- process must not diverge from the persisted next-launcher version.
13
- - Keep Refresh, diagnostics, and component-specific repair actions in the
14
- secondary/advanced action areas.
15
- - Add public documentation, plugin repository, release, and Runtime project
16
- links to the settings page.
17
-
18
- No Java engine or `foggy-runtime-cli` source was changed.
1
+ # Foggy DeepSeek Harness plugin 0.4.0-rc.3 release candidate
2
+
3
+ Assessment date: 2026-09-06
4
+
5
+ ## Delta from rc.2
6
+
7
+ - Add a single **Initialize and start** action for first use.
8
+ - Add **Update components** and **Update and start** actions for managed CLI,
9
+ Launcher, and Skill assets after a plugin-package upgrade.
10
+ - Show current versus target component versions and an explicit update banner.
11
+ - Block component update/repair while Runtime is running; the active Launcher
12
+ process must not diverge from the persisted next-launcher version.
13
+ - Keep Refresh, diagnostics, and component-specific repair actions in the
14
+ secondary/advanced action areas.
15
+ - Add public documentation, plugin repository, release, and Runtime project
16
+ links to the settings page.
17
+
18
+ No Java engine or `foggy-runtime-cli` source was changed.
@@ -1,60 +1,60 @@
1
- # Foggy DeepSeek Harness plugin 0.4.1-rc.1
2
-
3
- This release candidate is the compatibility line for DeepSeek Harness
4
- `0.1.5-rc.2`. It is published as a separate pre-release so the existing
5
- `0.4.0-rc.3`/`beta` installation path remains unchanged while the new Harness
6
- client is evaluated.
7
-
8
- ## Compatibility changes
9
-
10
- - Align DSH peer packages with `0.1.5-rc.2` and Cordis `4.0.2`.
11
- - Remove the obsolete `@deepseek-ai/dsh-client-runtime` injection. DSH
12
- `0.1.5-rc.2` does not ship that package and the plugin does not use its API.
13
- - Require Node.js `>=24.0.0`. DSH 0.1.5 uses modern ESM entry-point behavior;
14
- the plugin fails early with a visible prerequisite error on older Node lines.
15
- - Pin the onboarding manifest to DSH `0.1.5-rc.2` and keep the Foggy CLI,
16
- Launcher, and Skills pins unchanged.
17
-
18
- The plugin's remote service, native Skill provider, locale registration, and
19
- Settings → Plugins tab continue to use the same public APIs. The DSH 0.1.5
20
- web client adds file/sidebar features, but none of those changes are required
21
- by Foggy's integration.
22
-
23
- ## Installation
24
-
25
- Use Node.js 24 or newer and install the exact candidate in a separate profile:
26
-
27
- ```powershell
28
- dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.1-rc.1
29
- dsh web
30
- ```
31
-
32
- The npm `dsh015` dist-tag points to this candidate. Existing users of the
33
- stable `beta` tag are not moved automatically.
34
-
35
- ## Verification gate
36
-
37
- The candidate must pass all of the following before it replaces the stable
38
- baseline:
39
-
40
- 1. npm package shape and Node syntax checks;
41
- 2. the repository onboarding/unit test suite;
42
- 3. a clean DSH `0.1.5-rc.2` profile can add the package without an impossible
43
- `dsh-client-runtime` peer resolution;
44
- 4. `dsh --version` reports `0.1.5-rc.2` and `dsh web --no-open` starts under
45
- Node 24;
46
- 5. the web Settings → Plugins page loads Foggy's tab, native Skills are
47
- discoverable, and the plugin status remote responds;
48
- 6. Foggy initialization remains development-only and does not restart a
49
- healthy Runtime during datasource/model onboarding.
50
-
51
- The candidate does not change Foggy Runtime/Launcher binaries or production
52
- deployment policy. If a DSH profile reports
53
- `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION`, rebuild only that profile's lockfile
54
- and retry the exact add command; do not disable pnpm's policy globally.
55
-
56
- ## Upstream references
57
-
58
- - [DeepSeek Harness v0.1.5-rc.2 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.5-rc.2)
59
- - [DeepSeek Harness release history](https://github.com/deepseek-ai/deepseek-harness/releases)
60
- - [Node entry-point compatibility discussion](https://github.com/deepseek-ai/deepseek-harness/discussions/6124)
1
+ # Foggy DeepSeek Harness plugin 0.4.1-rc.1
2
+
3
+ This release candidate is the compatibility line for DeepSeek Harness
4
+ `0.1.5-rc.2`. It is published as a separate pre-release so the existing
5
+ `0.4.0-rc.3`/`beta` installation path remains unchanged while the new Harness
6
+ client is evaluated.
7
+
8
+ ## Compatibility changes
9
+
10
+ - Align DSH peer packages with `0.1.5-rc.2` and Cordis `4.0.2`.
11
+ - Remove the obsolete `@deepseek-ai/dsh-client-runtime` injection. DSH
12
+ `0.1.5-rc.2` does not ship that package and the plugin does not use its API.
13
+ - Require Node.js `>=24.0.0`. DSH 0.1.5 uses modern ESM entry-point behavior;
14
+ the plugin fails early with a visible prerequisite error on older Node lines.
15
+ - Pin the onboarding manifest to DSH `0.1.5-rc.2` and keep the Foggy CLI,
16
+ Launcher, and Skills pins unchanged.
17
+
18
+ The plugin's remote service, native Skill provider, locale registration, and
19
+ Settings → Plugins tab continue to use the same public APIs. The DSH 0.1.5
20
+ web client adds file/sidebar features, but none of those changes are required
21
+ by Foggy's integration.
22
+
23
+ ## Installation
24
+
25
+ Use Node.js 24 or newer and install the exact candidate in a separate profile:
26
+
27
+ ```powershell
28
+ dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.1-rc.1
29
+ dsh web
30
+ ```
31
+
32
+ The npm `dsh015` dist-tag points to this candidate. Existing users of the
33
+ stable `beta` tag are not moved automatically.
34
+
35
+ ## Verification gate
36
+
37
+ The candidate must pass all of the following before it replaces the stable
38
+ baseline:
39
+
40
+ 1. npm package shape and Node syntax checks;
41
+ 2. the repository onboarding/unit test suite;
42
+ 3. a clean DSH `0.1.5-rc.2` profile can add the package without an impossible
43
+ `dsh-client-runtime` peer resolution;
44
+ 4. `dsh --version` reports `0.1.5-rc.2` and `dsh web --no-open` starts under
45
+ Node 24;
46
+ 5. the web Settings → Plugins page loads Foggy's tab, native Skills are
47
+ discoverable, and the plugin status remote responds;
48
+ 6. Foggy initialization remains development-only and does not restart a
49
+ healthy Runtime during datasource/model onboarding.
50
+
51
+ The candidate does not change Foggy Runtime/Launcher binaries or production
52
+ deployment policy. If a DSH profile reports
53
+ `ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION`, rebuild only that profile's lockfile
54
+ and retry the exact add command; do not disable pnpm's policy globally.
55
+
56
+ ## Upstream references
57
+
58
+ - [DeepSeek Harness v0.1.5-rc.2 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.5-rc.2)
59
+ - [DeepSeek Harness release history](https://github.com/deepseek-ai/deepseek-harness/releases)
60
+ - [Node entry-point compatibility discussion](https://github.com/deepseek-ai/deepseek-harness/discussions/6124)
@@ -1,62 +1,62 @@
1
- # Foggy DeepSeek Harness plugin 0.4.2-rc.1
2
-
3
- This isolated compatibility candidate targets DeepSeek Harness `0.1.7-rc.2`.
4
- It requires system Node.js `>=24.0.0`. It is deliberately published under a
5
- dedicated npm dist-tag so the existing `beta`, `rc`, and `dsh015` installation
6
- channels remain unchanged.
7
-
8
- ## Compatibility changes
9
-
10
- - Adapt strict Typert codecs to the `create()` schema factory required by DSH
11
- `0.1.7`, while retaining the `schema` property used by the earlier `0.1.5`
12
- loader.
13
- - Align DeepSeek Harness peer-package ranges and the onboarding manifest with
14
- `0.1.7-rc.2`.
15
- - Keep Foggy CLI, Launcher, Skills, Runtime behavior, and the development-only
16
- product boundary unchanged.
17
-
18
- ## Installation
19
-
20
- Use Node.js 24 or newer and a separate Harness profile:
21
-
22
- ```powershell
23
- dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.1
24
- dsh web
25
- ```
26
-
27
- The same candidate is available through the dedicated `dsh017` npm dist-tag.
28
- Do not use this candidate to replace a stable `beta` installation unless the
29
- profile is intended to run DSH `0.1.7-rc.2`.
30
-
31
- ## Compatibility acceptance (2026-09-25)
32
-
33
- - `npm run check`, all 23 Node tests, and all 29 Python tests passed on Node
34
- `24.19.0`.
35
- - Packed and installed this exact candidate into a fresh temporary DSH Web
36
- profile running `0.1.7-rc.2`. The package manager completed installation;
37
- DSH emitted no plugin/Typert registration error at startup.
38
- - The authenticated Web boot graph included the Foggy client bundle. Fetching
39
- the served bundle returned HTTP 200 and confirmed the `settings.plugins.tab`
40
- contribution is present.
41
- - Invoked Foggy `status` and `plan` through DSH's Remote HTTP transport. Both
42
- returned successful structured results with package version `0.4.2-rc.1`.
43
- - Created a temporary session and called DSH's native `skills/list` Remote. It
44
- returned `foggy-deepseek-onboarding` from the installed plugin package and
45
- `modelInvocable: true`. The host also exposes separately installed user-level
46
- Foggy skills; the package-provided onboarding Skill remained individually
47
- discoverable.
48
- - Used Plugin Manager to disable and re-enable the bundle. Both changes
49
- reported `application: applied`; while disabled, the Foggy strict Remote
50
- correctly returned `gateway/definition-unavailable`, and after re-enabling
51
- `status` succeeded again. The final bundle state is enabled and installed.
52
- - No Runtime was started, no component update/repair was requested, and no
53
- database connection or query was made. The status read observed the host's
54
- existing Foggy component state; it did not change it. Full component
55
- installation and Runtime behavior remain outside this DSH protocol smoke
56
- test.
57
-
58
- ## Upstream references
59
-
60
- - [DeepSeek Harness v0.1.7-rc.2 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.7-rc.2)
61
- - [DeepSeek Harness v0.1.7-rc.1 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.7-rc.1)
62
- - [DeepSeek Harness release history](https://github.com/deepseek-ai/deepseek-harness/releases)
1
+ # Foggy DeepSeek Harness plugin 0.4.2-rc.1
2
+
3
+ This isolated compatibility candidate targets DeepSeek Harness `0.1.7-rc.2`.
4
+ It requires system Node.js `>=24.0.0`. It is deliberately published under a
5
+ dedicated npm dist-tag so the existing `beta`, `rc`, and `dsh015` installation
6
+ channels remain unchanged.
7
+
8
+ ## Compatibility changes
9
+
10
+ - Adapt strict Typert codecs to the `create()` schema factory required by DSH
11
+ `0.1.7`, while retaining the `schema` property used by the earlier `0.1.5`
12
+ loader.
13
+ - Align DeepSeek Harness peer-package ranges and the onboarding manifest with
14
+ `0.1.7-rc.2`.
15
+ - Keep Foggy CLI, Launcher, Skills, Runtime behavior, and the development-only
16
+ product boundary unchanged.
17
+
18
+ ## Installation
19
+
20
+ Use Node.js 24 or newer and a separate Harness profile:
21
+
22
+ ```powershell
23
+ dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.1
24
+ dsh web
25
+ ```
26
+
27
+ The same candidate is available through the dedicated `dsh017` npm dist-tag.
28
+ Do not use this candidate to replace a stable `beta` installation unless the
29
+ profile is intended to run DSH `0.1.7-rc.2`.
30
+
31
+ ## Compatibility acceptance (2026-09-25)
32
+
33
+ - `npm run check`, all 23 Node tests, and all 29 Python tests passed on Node
34
+ `24.19.0`.
35
+ - Packed and installed this exact candidate into a fresh temporary DSH Web
36
+ profile running `0.1.7-rc.2`. The package manager completed installation;
37
+ DSH emitted no plugin/Typert registration error at startup.
38
+ - The authenticated Web boot graph included the Foggy client bundle. Fetching
39
+ the served bundle returned HTTP 200 and confirmed the `settings.plugins.tab`
40
+ contribution is present.
41
+ - Invoked Foggy `status` and `plan` through DSH's Remote HTTP transport. Both
42
+ returned successful structured results with package version `0.4.2-rc.1`.
43
+ - Created a temporary session and called DSH's native `skills/list` Remote. It
44
+ returned `foggy-deepseek-onboarding` from the installed plugin package and
45
+ `modelInvocable: true`. The host also exposes separately installed user-level
46
+ Foggy skills; the package-provided onboarding Skill remained individually
47
+ discoverable.
48
+ - Used Plugin Manager to disable and re-enable the bundle. Both changes
49
+ reported `application: applied`; while disabled, the Foggy strict Remote
50
+ correctly returned `gateway/definition-unavailable`, and after re-enabling
51
+ `status` succeeded again. The final bundle state is enabled and installed.
52
+ - No Runtime was started, no component update/repair was requested, and no
53
+ database connection or query was made. The status read observed the host's
54
+ existing Foggy component state; it did not change it. Full component
55
+ installation and Runtime behavior remain outside this DSH protocol smoke
56
+ test.
57
+
58
+ ## Upstream references
59
+
60
+ - [DeepSeek Harness v0.1.7-rc.2 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.7-rc.2)
61
+ - [DeepSeek Harness v0.1.7-rc.1 release](https://github.com/deepseek-ai/deepseek-harness/releases/tag/dsh-v0.1.7-rc.1)
62
+ - [DeepSeek Harness release history](https://github.com/deepseek-ai/deepseek-harness/releases)