@foggy-projects/deepseek-harness-plugin 0.4.0-beta.10
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/LICENSE +201 -0
- package/README.md +81 -0
- package/THIRD-PARTY-RUNTIME-NOTICES.md +16 -0
- package/cordis.patch.yml +6 -0
- package/docs/PUBLIC-BETA-READINESS.md +57 -0
- package/docs/WINDOWS-BETA-ACCEPTANCE.md +75 -0
- package/experience/linux/README.md +53 -0
- package/experience/linux/prepare.sh +188 -0
- package/lib/atomic-json.js +41 -0
- package/lib/client.js +453 -0
- package/lib/index.js +467 -0
- package/lib/python-runtime.js +339 -0
- package/lib/remote-descriptor.js +30 -0
- package/lib/remote.js +8 -0
- package/lib/skill-provider.js +111 -0
- package/lib/typert.js +9 -0
- package/lib/version.js +20 -0
- package/package.json +63 -0
- package/skills/foggy-deepseek-onboarding/SKILL.md +137 -0
- package/skills/foggy-deepseek-onboarding/assets/connection.schema.json +50 -0
- package/skills/foggy-deepseek-onboarding/assets/datasource.example.json +13 -0
- package/skills/foggy-deepseek-onboarding/assets/env.example +14 -0
- package/skills/foggy-deepseek-onboarding/assets/onboarding-state.schema.json +42 -0
- package/skills/foggy-deepseek-onboarding/assets/semantic-plan.example.json +8 -0
- package/skills/foggy-deepseek-onboarding/assets/semantic-plan.schema.json +21 -0
- package/skills/foggy-deepseek-onboarding/assets/versions.json +137 -0
- package/skills/foggy-deepseek-onboarding/references/onboarding-workflow.md +156 -0
- package/skills/foggy-deepseek-onboarding/scripts/doctor.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/doctor.sh +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/install.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/install.sh +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/invoke-onboarding.ps1 +30 -0
- package/skills/foggy-deepseek-onboarding/scripts/invoke-onboarding.sh +24 -0
- package/skills/foggy-deepseek-onboarding/scripts/onboard.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/onboard.sh +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/onboarding.py +3027 -0
- package/skills/foggy-deepseek-onboarding/scripts/runtime-start.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/runtime-start.sh +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/runtime-stop.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/runtime-stop.sh +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/uninstall.ps1 +4 -0
- package/skills/foggy-deepseek-onboarding/scripts/uninstall.sh +4 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,81 @@
|
|
|
1
|
+
# Foggy for DeepSeek Harness (Beta)
|
|
2
|
+
|
|
3
|
+
This package is the lightweight DeepSeek Harness Bundle for Foggy's Java data
|
|
4
|
+
analysis engine. Installing the Bundle adds a native Foggy tab under **Settings
|
|
5
|
+
→ Plugins**. The private Python runtime, Launcher, and isolated CLI environment
|
|
6
|
+
are downloaded only when the user selects **Initialize Foggy**.
|
|
7
|
+
|
|
8
|
+
DeepSeek Harness uses a system Node.js (`^22.19.0 || >=24.0.0`) and Foggy's Java
|
|
9
|
+
Launcher uses a system Java 17+. Foggy manages its own pinned Python 3.12 runtime
|
|
10
|
+
inside the per-user component directory; it does not require a system Python,
|
|
11
|
+
modify `PATH`, or register Python globally. Advanced users may explicitly set
|
|
12
|
+
`FOGGY_PYTHON` to a compatible Python 3.11+ executable.
|
|
13
|
+
|
|
14
|
+
## Local beta installation
|
|
15
|
+
|
|
16
|
+
```powershell
|
|
17
|
+
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.0-beta.10.tgz
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Restart `dsh web`, use the browser it opens (or the complete printed URL,
|
|
21
|
+
including `?token=...`), open Settings → Plugins → Foggy Data Analysis, and
|
|
22
|
+
initialize the components from there. Do not share the launch-token URL.
|
|
23
|
+
|
|
24
|
+
After npm beta publication, the corresponding one-line install is:
|
|
25
|
+
|
|
26
|
+
```powershell
|
|
27
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@beta
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
For development, `FOGGY_ASSET_CACHE_DIRS` can contain platform-delimited verified
|
|
31
|
+
asset-cache directories. It is not required for a normal install.
|
|
32
|
+
|
|
33
|
+
Database credentials remain outside the ordinary DSH settings document. The
|
|
34
|
+
bundled onboarding Skill drives datasource discovery, semantic drafting,
|
|
35
|
+
checkpointed publication, and bounded read-only query verification.
|
|
36
|
+
|
|
37
|
+
## Native Skill and workspace contract
|
|
38
|
+
|
|
39
|
+
The Bundle registers `foggy-deepseek-onboarding` and the downloaded
|
|
40
|
+
`foggy-ai-analysis` through DeepSeek Harness's native Skill provider API. Skills
|
|
41
|
+
are available in every DSH workspace without copying or symlinking `.agents`.
|
|
42
|
+
The current session `cwd` remains the workspace boundary for semantic drafts and
|
|
43
|
+
evidence.
|
|
44
|
+
|
|
45
|
+
Opaque CLI profiles default to the private persistent
|
|
46
|
+
`<dataRoot>/cli-profiles` directory. Composite onboarding commands are
|
|
47
|
+
idempotent: unchanged completed phases are resumed rather than re-adding a
|
|
48
|
+
datasource or re-registering a published bundle. Settings detects legacy
|
|
49
|
+
temporary profiles and offers an explicit, validated migration into the
|
|
50
|
+
persistent store. A completed profile can also be bound non-destructively to an
|
|
51
|
+
additional DSH workspace when its reviewed connection contract and published
|
|
52
|
+
semantic digest are unchanged.
|
|
53
|
+
|
|
54
|
+
Private Python, CLI, Launcher, the analysis Skill, install state, and Runtime
|
|
55
|
+
state live in the user-level Foggy component directories. The managed CLI is intentionally isolated
|
|
56
|
+
and does not need to be on `PATH`. **Re-download / Repair** verifies the global
|
|
57
|
+
analysis Skill, backs up modified or outdated managed content, restores it, and
|
|
58
|
+
invalidates DSH's Skill catalog. The onboarding Skill is bundled with the plugin
|
|
59
|
+
and is restored by reinstalling or upgrading the plugin package.
|
|
60
|
+
|
|
61
|
+
The Foggy settings tab shows the persisted database/semantic onboarding stages,
|
|
62
|
+
offers pinned checks and repair for CLI, Launcher, and the managed analysis
|
|
63
|
+
Skill, private Python, and exports a private redacted diagnostics report. Runtime start is
|
|
64
|
+
idempotent: an already-recorded process is verified with `wait-ready` and
|
|
65
|
+
`capabilities` instead of being treated as a failed second start.
|
|
66
|
+
|
|
67
|
+
This beta remains a local dev/test integration. The bundled Runtime reports
|
|
68
|
+
`securityMode=none-dev-test-only` and must not be exposed to a network or used as
|
|
69
|
+
a production service.
|
|
70
|
+
|
|
71
|
+
See [`docs/PUBLIC-BETA-READINESS.md`](./docs/PUBLIC-BETA-READINESS.md) for the
|
|
72
|
+
tested public Beta scope, release gates, and stable-release blockers.
|
|
73
|
+
Native Windows acceptance instructions are in
|
|
74
|
+
[`docs/WINDOWS-BETA-ACCEPTANCE.md`](./docs/WINDOWS-BETA-ACCEPTANCE.md); database
|
|
75
|
+
credentials intentionally remain outside the public repository.
|
|
76
|
+
|
|
77
|
+
## Linux and WSL2 experience
|
|
78
|
+
|
|
79
|
+
Ubuntu and WSL2 users can use the checked-in preflighted installer under
|
|
80
|
+
[`experience/linux`](./experience/linux/README.md). It keeps DSH, its profile,
|
|
81
|
+
the project workspace, and Foggy data on the Linux-native filesystem.
|
|
@@ -0,0 +1,16 @@
|
|
|
1
|
+
# Third-party runtime notices
|
|
2
|
+
|
|
3
|
+
Foggy for DeepSeek Harness downloads a pinned CPython runtime on first
|
|
4
|
+
initialization. The runtime is not included in the npm package and is installed
|
|
5
|
+
only inside Foggy's per-user component directory.
|
|
6
|
+
|
|
7
|
+
- CPython is provided under the Python Software Foundation License Version 2.
|
|
8
|
+
- Portable distributions are produced by
|
|
9
|
+
[astral-sh/python-build-standalone](https://github.com/astral-sh/python-build-standalone),
|
|
10
|
+
whose build tooling is provided under MPL-2.0.
|
|
11
|
+
- The downloaded distribution contains its own license and attribution files.
|
|
12
|
+
|
|
13
|
+
The exact build release, platform assets, sizes, URLs, and SHA256 digests are
|
|
14
|
+
recorded in `skills/foggy-deepseek-onboarding/assets/versions.json`. Foggy
|
|
15
|
+
verifies the selected digest before extraction and does not add the interpreter
|
|
16
|
+
to `PATH` or register it as a system Python installation.
|
package/cordis.patch.yml
ADDED
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
# Foggy host service and its browser-side Settings contribution share one
|
|
2
|
+
# dual-face package. dsh-client-modules discovers the client declaration in
|
|
3
|
+
# package.json after this Host row becomes active.
|
|
4
|
+
- insert:
|
|
5
|
+
- id: foggy-data-analysis
|
|
6
|
+
name: '@foggy-projects/deepseek-harness-plugin'
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
# Public beta readiness: 0.4.0-beta.10
|
|
2
|
+
|
|
3
|
+
Assessment date: 2026-09-04
|
|
4
|
+
|
|
5
|
+
## Verdict
|
|
6
|
+
|
|
7
|
+
`0.4.0-beta.10` 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 67 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.10 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
|
+
- The UI reported Python 3.12.13 as `Foggy private`, and CLI 0.1.23, Launcher
|
|
30
|
+
0.1.18, analysis Skill 0.1.17, and onboarding Skill 0.4.0-beta.10 as installed.
|
|
31
|
+
- Interrupted downloads resume with HTTP Range when the server supports it;
|
|
32
|
+
downloaded artifacts are not trusted until the complete SHA256 matches.
|
|
33
|
+
- Windows progress writes tolerate transient sharing violations without losing
|
|
34
|
+
the previous valid progress document or leaving temporary files behind.
|
|
35
|
+
- Automated regression passed on Windows and Linux/WSL2: 17 Node tests and 10
|
|
36
|
+
Python tests on each platform, plus shell and PowerShell syntax checks.
|
|
37
|
+
|
|
38
|
+
## Beta boundaries
|
|
39
|
+
|
|
40
|
+
- Supported public-beta targets: Windows 10/11 x64 and Linux/WSL2 x64.
|
|
41
|
+
- Windows users must install a supported system Node.js line (`^22.19.0` or
|
|
42
|
+
`>=24.0.0`) and Java 17 or later. They do not need to install Python.
|
|
43
|
+
- macOS and arm64 assets are pinned and integrity-checked but have not received
|
|
44
|
+
the same end-to-end host validation; treat those targets as experimental.
|
|
45
|
+
- DeepSeek Harness itself is consumed at `0.1.2-rc.1`. Its authenticated Web UI
|
|
46
|
+
launch URL, plugin installation, and supply-chain policy behavior may change
|
|
47
|
+
before a stable Harness release.
|
|
48
|
+
- Runtime production authentication is outside this beta's default local
|
|
49
|
+
onboarding mode. The UI and doctor continue to report `productionReady=false`
|
|
50
|
+
for the development-only no-auth mode.
|
|
51
|
+
|
|
52
|
+
## Release gate after publication
|
|
53
|
+
|
|
54
|
+
Before broad announcement, complete the native Windows fresh-machine checklist
|
|
55
|
+
in [WINDOWS-BETA-ACCEPTANCE.md](./WINDOWS-BETA-ACCEPTANCE.md). Record the exact
|
|
56
|
+
Node, Java, DeepSeek Harness, and plugin versions and confirm that initialization
|
|
57
|
+
works without a system Python executable.
|
|
@@ -0,0 +1,75 @@
|
|
|
1
|
+
# Native Windows Beta acceptance
|
|
2
|
+
|
|
3
|
+
This runbook validates DeepSeek Harness `0.1.2-rc.1` with Foggy plugin
|
|
4
|
+
`0.4.0-beta.10` on a clean 64-bit Windows 10 or Windows 11 machine. Use a local
|
|
5
|
+
directory that is not synchronized by OneDrive.
|
|
6
|
+
|
|
7
|
+
## Prerequisites
|
|
8
|
+
|
|
9
|
+
Install a system Node.js matching `^22.19.0 || >=24.0.0` and a system Java 17+
|
|
10
|
+
JRE/JDK. Windows must also provide `tar` (included in supported Windows 10/11
|
|
11
|
+
versions). A system Python is neither required nor used by default.
|
|
12
|
+
|
|
13
|
+
```powershell
|
|
14
|
+
node --version
|
|
15
|
+
npm --version
|
|
16
|
+
java -version
|
|
17
|
+
tar --version
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
Foggy downloads a pinned private CPython 3.12.13 runtime during initialization.
|
|
21
|
+
It remains below `%LOCALAPPDATA%\Foggy\DeepSeekHarness`, is not added to `PATH`,
|
|
22
|
+
and is not registered as a system Python.
|
|
23
|
+
|
|
24
|
+
## Install and start
|
|
25
|
+
|
|
26
|
+
```powershell
|
|
27
|
+
New-Item -ItemType Directory -Force C:\FoggyAcceptance | Out-Null
|
|
28
|
+
Set-Location C:\FoggyAcceptance
|
|
29
|
+
|
|
30
|
+
npx --yes --package=@deepseek-ai/dsh@0.1.2-rc.1 --package=pnpm@11.7.0 `
|
|
31
|
+
dsh plugin --profile web add --workspace-root `
|
|
32
|
+
"@foggy-projects/deepseek-harness-plugin@beta"
|
|
33
|
+
|
|
34
|
+
npx --yes --package=@deepseek-ai/dsh@0.1.2-rc.1 --package=pnpm@11.7.0 dsh web
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
Let DSH open the browser automatically. If it does not, copy the complete URL
|
|
38
|
+
printed by `dsh web`, including its `?token=...` query, into the browser. A new
|
|
39
|
+
browser session cannot use the bare `http://127.0.0.1:3080/` URL until that
|
|
40
|
+
token has established its local authentication cookie. Treat the launch URL as
|
|
41
|
+
temporary local access material and do not paste it into chat or diagnostics.
|
|
42
|
+
|
|
43
|
+
Configure an LLM provider, select the `C:\FoggyAcceptance` workspace, then open
|
|
44
|
+
**Settings → Plugins → Foggy Data Analysis** and choose **Initialize Foggy**.
|
|
45
|
+
|
|
46
|
+
Expected component state:
|
|
47
|
+
|
|
48
|
+
- Python 3.12.13, source `Foggy private`;
|
|
49
|
+
- CLI 0.1.23;
|
|
50
|
+
- Launcher 0.1.18;
|
|
51
|
+
- analysis Skill 0.1.17;
|
|
52
|
+
- onboarding Skill 0.4.0-beta.10;
|
|
53
|
+
- Java 17+ available;
|
|
54
|
+
- native DSH Skill registration available.
|
|
55
|
+
|
|
56
|
+
## Database and semantic-layer acceptance
|
|
57
|
+
|
|
58
|
+
Keep database credentials out of this public repository. Create a private CLI
|
|
59
|
+
profile outside the DSH conversation, pass only its opaque profile ID and
|
|
60
|
+
revision to the onboarding workflow, and use a test-only database account with
|
|
61
|
+
read-only permissions.
|
|
62
|
+
|
|
63
|
+
Use a natural prompt such as:
|
|
64
|
+
|
|
65
|
+
```text
|
|
66
|
+
请帮我用 Foggy 分析这个测试数据库。我已经按验收手册创建了私有连接
|
|
67
|
+
profile。请先确认连接和表结构,再围绕订单数据创建一个简单的语义层,
|
|
68
|
+
包含订单数量、状态和开单时间,最后执行一个不超过 20 行的只读查询。
|
|
69
|
+
不要修改数据库,也不要在对话或验收文件中输出密码。
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
Pass only when Runtime readiness and capabilities succeed, datasource metadata
|
|
73
|
+
can be discovered, TM/QM models validate and publish, the bounded read-only
|
|
74
|
+
query succeeds, diagnostics contain no credentials, and stopping Runtime frees
|
|
75
|
+
port 18066.
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
# Linux and WSL2 experience
|
|
2
|
+
|
|
3
|
+
This entry prepares a clean, user-owned DeepSeek Harness web profile with the public Foggy Bundle.
|
|
4
|
+
It has been designed for Ubuntu 22.04/24.04 x86_64 and WSL2.
|
|
5
|
+
|
|
6
|
+
## Prerequisites
|
|
7
|
+
|
|
8
|
+
- Node.js `^22.19.0` or `>=24.0.0`
|
|
9
|
+
- Java 17 or newer
|
|
10
|
+
- Git, npm, and `tar`
|
|
11
|
+
- At least 4 GiB free disk space and 2 GiB available memory; 4 GiB memory is recommended
|
|
12
|
+
|
|
13
|
+
Keep the experience root on the Linux-native filesystem, such as under `$HOME`. In WSL2, do not
|
|
14
|
+
put DSH, `node_modules`, Foggy's private Python environment, or Foggy data under `/mnt/c` or `/mnt/d`.
|
|
15
|
+
|
|
16
|
+
## Prepare
|
|
17
|
+
|
|
18
|
+
```bash
|
|
19
|
+
git clone https://github.com/foggy-projects/foggy-deepseek-harness-plugin.git
|
|
20
|
+
cd foggy-deepseek-harness-plugin
|
|
21
|
+
bash experience/linux/prepare.sh --dry-run
|
|
22
|
+
bash experience/linux/prepare.sh
|
|
23
|
+
```
|
|
24
|
+
|
|
25
|
+
The script installs pinned pnpm and DeepSeek Harness versions inside
|
|
26
|
+
`~/.local/share/foggy-deepseek-harness-experience`, clones and packs the public Foggy Bundle, and
|
|
27
|
+
adds it to a clean DSH web profile. It does not use `sudo`, install operating-system packages, write
|
|
28
|
+
model credentials, initialize Foggy components, or start the web process.
|
|
29
|
+
|
|
30
|
+
Start the prepared profile with:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
~/.local/share/foggy-deepseek-harness-experience/run.sh
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
Open the URL printed by DSH, then choose **Settings → Plugins → Foggy Data Analysis** and select
|
|
37
|
+
**Initialize Foggy**. Private Python, the CLI, Launcher, and analysis Skill are downloaded from their
|
|
38
|
+
pinned public Releases and verified before installation. A system Python is not required.
|
|
39
|
+
|
|
40
|
+
Provider configuration remains a separate DSH setup step. Store API keys in a private environment
|
|
41
|
+
file or secret manager; do not add them to the DSH settings document or the project repository.
|
|
42
|
+
|
|
43
|
+
## Custom roots
|
|
44
|
+
|
|
45
|
+
```bash
|
|
46
|
+
bash experience/linux/prepare.sh \
|
|
47
|
+
--experience-root "$HOME/.local/share/my-foggy-experience" \
|
|
48
|
+
--project-root "$HOME/my-foggy-workspace"
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
The script refuses a non-empty experience root. This prevents an existing profile from being
|
|
52
|
+
silently overwritten. Remove an abandoned test root yourself after confirming that it contains no
|
|
53
|
+
data you need, or choose a new root.
|