@foggy-projects/deepseek-harness-plugin 0.4.2-rc.5 → 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.
- package/README.md +222 -185
- package/THIRD-PARTY-RUNTIME-NOTICES.md +16 -16
- package/cordis.patch.yml +6 -6
- package/docs/COMMUNITY-MARKETPLACES.md +64 -64
- package/docs/PUBLIC-BETA-READINESS.md +109 -109
- package/docs/RELEASE-CANDIDATE-0.4.0-RC.2.md +38 -38
- package/docs/RELEASE-CANDIDATE-0.4.0-RC.3.md +18 -18
- package/docs/RELEASE-CANDIDATE-0.4.1-DSH-0.1.5-RC.1.md +60 -60
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.1.md +62 -62
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.2.md +50 -50
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.3.md +34 -34
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.4.md +32 -32
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.5.md +27 -27
- package/docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md +96 -0
- package/docs/RELEASE-CANDIDATE-0.4.4-DSH-0.2.1-RC.1.md +135 -0
- package/docs/WINDOWS-BETA-ACCEPTANCE.md +113 -113
- package/experience/linux/README.md +53 -53
- package/experience/linux/prepare.sh +2 -2
- package/lib/atomic-json.js +41 -41
- package/lib/client.js +1222 -1031
- package/lib/component-manager.js +164 -0
- package/lib/component-releases.js +363 -0
- package/lib/diagnostics.js +86 -86
- package/lib/index.js +764 -698
- package/lib/operation-lock.js +139 -0
- package/lib/python-runtime.js +339 -339
- package/lib/query-tool.js +134 -131
- package/lib/remote-descriptor.js +74 -59
- package/lib/remote.js +8 -8
- package/lib/runtime-settings.js +89 -89
- package/lib/skill-provider.js +116 -116
- package/lib/typert.js +9 -9
- package/lib/version.js +20 -20
- package/lib/viewer-preview.js +44 -27
- package/package.json +19 -16
- package/skills/foggy-deepseek-onboarding/SKILL.md +149 -143
- package/skills/foggy-deepseek-onboarding/assets/connection.schema.json +48 -48
- package/skills/foggy-deepseek-onboarding/assets/datasource.example.json +14 -14
- package/skills/foggy-deepseek-onboarding/assets/env.example +14 -14
- package/skills/foggy-deepseek-onboarding/assets/onboarding-state.schema.json +71 -71
- package/skills/foggy-deepseek-onboarding/assets/semantic-plan.example.json +8 -8
- package/skills/foggy-deepseek-onboarding/assets/semantic-plan.schema.json +21 -21
- package/skills/foggy-deepseek-onboarding/assets/versions.json +23 -23
- package/skills/foggy-deepseek-onboarding/references/onboarding-workflow.md +168 -168
- package/skills/foggy-deepseek-onboarding/scripts/doctor.ps1 +4 -4
- package/skills/foggy-deepseek-onboarding/scripts/install.ps1 +4 -4
- package/skills/foggy-deepseek-onboarding/scripts/invoke-onboarding.ps1 +32 -32
- package/skills/foggy-deepseek-onboarding/scripts/onboard.ps1 +4 -4
- package/skills/foggy-deepseek-onboarding/scripts/onboarding.py +3721 -3697
- package/skills/foggy-deepseek-onboarding/scripts/runtime-start.ps1 +4 -4
- package/skills/foggy-deepseek-onboarding/scripts/runtime-stop.ps1 +4 -4
- package/skills/foggy-deepseek-onboarding/scripts/uninstall.ps1 +4 -4
package/README.md
CHANGED
|
@@ -1,185 +1,222 @@
|
|
|
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
|
-
→
|
|
6
|
-
are downloaded only when the user selects **Initialize and start** (or the
|
|
7
|
-
equivalent component action). Existing installations are not silently changed
|
|
8
|
-
when the plugin package is upgraded.
|
|
9
|
-
|
|
10
|
-
The
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
85
|
-
|
|
86
|
-
|
|
87
|
-
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
|
|
92
|
-
|
|
93
|
-
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
103
|
-
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
144
|
-
The
|
|
145
|
-
|
|
146
|
-
|
|
147
|
-
|
|
148
|
-
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
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
|
+
→ Built-in plugins**. The private Python runtime, Launcher, and isolated CLI environment
|
|
6
|
+
are downloaded only when the user selects **Initialize and start** (or the
|
|
7
|
+
equivalent component action). Existing installations are not silently changed
|
|
8
|
+
when the plugin package is upgraded.
|
|
9
|
+
|
|
10
|
+
The Foggy settings tab includes a **Tutorial** entry linking to
|
|
11
|
+
[Foggy AI Data tutorials](https://ai-data.qlfloor.com/).
|
|
12
|
+
|
|
13
|
+
The `0.4.4-rc.1` compatibility candidate targets DeepSeek Harness `0.2.1-rc.2`
|
|
14
|
+
and requires a system Node.js `>=24.0.0`. Foggy's Java Launcher uses a system
|
|
15
|
+
Java 17+. Foggy manages its own pinned Python 3.12 runtime
|
|
16
|
+
inside the per-user component directory; it does not require a system Python,
|
|
17
|
+
modify `PATH`, or register Python globally. Advanced users may explicitly set
|
|
18
|
+
`FOGGY_PYTHON` to a compatible Python 3.11+ executable.
|
|
19
|
+
|
|
20
|
+
## Local release-candidate installation
|
|
21
|
+
|
|
22
|
+
```powershell
|
|
23
|
+
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.4-rc.1.tgz
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Restart `dsh web`, use the browser it opens (or the complete printed URL,
|
|
27
|
+
including `?token=...`), open Settings → Built-in plugins → Foggy Data Analysis, and
|
|
28
|
+
initialize the components from there. Do not share the launch-token URL.
|
|
29
|
+
|
|
30
|
+
After the version is available on npm, install the exact DSH 0.2.1-rc.2
|
|
31
|
+
compatibility candidate so the stable `beta` channel is not changed:
|
|
32
|
+
|
|
33
|
+
```powershell
|
|
34
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.4-rc.1
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
DSH 0.2.1 candidates use the `dsh021` npm dist-tag. Check that the tag resolves
|
|
38
|
+
to the version you intend to install before using it. GitHub's published
|
|
39
|
+
tarball can be installed directly when registry publication is still pending:
|
|
40
|
+
|
|
41
|
+
```powershell
|
|
42
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@dsh021
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
The earlier DSH `0.1.7-rc.2` and `0.1.5-rc.2` candidates remain available as
|
|
46
|
+
`@foggy-projects/deepseek-harness-plugin@dsh017` and `@foggy-projects/deepseek-harness-plugin@dsh015`.
|
|
47
|
+
The `dsh021` candidate does not move the existing `beta` or `latest` channels.
|
|
48
|
+
|
|
49
|
+
For the existing stable beta channel, the corresponding one-line install is:
|
|
50
|
+
|
|
51
|
+
```powershell
|
|
52
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@beta
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
The settings page automatically checks official Launcher and CLI releases when
|
|
56
|
+
opened, using a six-hour cache. It shows installed, upstream latest, and
|
|
57
|
+
plugin-validated versions separately, including prerelease labels. Use **Check
|
|
58
|
+
for updates** to refresh the list, then choose a version and select **Download
|
|
59
|
+
and use**. No component is downloaded or switched by an automatic check.
|
|
60
|
+
|
|
61
|
+
Stop Runtime before changing versions. Downloads are verified against official
|
|
62
|
+
SHA256SUMS and release metadata. Launcher and CLI versions are stored in
|
|
63
|
+
separate directories, and previously downloaded versions remain available for
|
|
64
|
+
offline rollback. A selected component version persists across plugin upgrades;
|
|
65
|
+
selecting CLI leaves the installed Launcher version unchanged, and vice versa.
|
|
66
|
+
The bundled validated defaults are Launcher **0.1.46** and CLI **0.1.25**; both
|
|
67
|
+
Foggy Skills remain at **0.1.18**. Components earlier than 0.1.24 are not offered
|
|
68
|
+
for activation in this compatibility line.
|
|
69
|
+
|
|
70
|
+
After upgrading the plugin package, use **Update components** (or **Update and
|
|
71
|
+
start**) to apply its targets to components without a saved user selection.
|
|
72
|
+
The settings page shows current and target versions. Component-specific repair
|
|
73
|
+
actions remain available under **Advanced repair**. Network check failures do
|
|
74
|
+
not block the installed Runtime or erase the cached version list.
|
|
75
|
+
|
|
76
|
+
DeepSeek Harness profiles can apply pnpm's minimum-release-age policy to their
|
|
77
|
+
lockfiles. An upgrade performed shortly after publication can therefore fail
|
|
78
|
+
while naming either the new plugin or a previously installed version. This is
|
|
79
|
+
a DSH profile-policy failure, not a damaged Foggy package. Use the exact profile
|
|
80
|
+
directory printed in the error and rebuild its lockfile, then rerun the same
|
|
81
|
+
`dsh plugin add` command:
|
|
82
|
+
|
|
83
|
+
```powershell
|
|
84
|
+
Set-Location "<the DSH profile directory printed in the error>"
|
|
85
|
+
npx --yes pnpm@11.7.0 clean --lockfile
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
The failed add normally records the requested exact version under
|
|
89
|
+
`minimumReleaseAgeExclude` before returning. If the error repeats, confirm that
|
|
90
|
+
both the installed and requested exact Foggy versions named by the error appear
|
|
91
|
+
under that key in the profile's `pnpm-workspace.yaml`; do not disable the policy
|
|
92
|
+
globally.
|
|
93
|
+
|
|
94
|
+
For development, `FOGGY_ASSET_CACHE_DIRS` can contain platform-delimited verified
|
|
95
|
+
asset-cache directories. It is not required for a normal install.
|
|
96
|
+
|
|
97
|
+
The bundled onboarding Skill is intentionally development-first. Users may
|
|
98
|
+
provide a local datasource password in the conversation, a user-managed
|
|
99
|
+
connection file, an Agent environment variable, or a compatible Runtime
|
|
100
|
+
Console. Direct passwords are submitted to the already-running Runtime without
|
|
101
|
+
being copied into onboarding state or evidence. The Skill then drives schema
|
|
102
|
+
discovery, semantic drafting, local Bundle registration, and bounded query
|
|
103
|
+
verification without restarting Runtime.
|
|
104
|
+
|
|
105
|
+
## Native Skill and workspace contract
|
|
106
|
+
|
|
107
|
+
The Bundle registers `foggy-deepseek-onboarding` and the downloaded
|
|
108
|
+
`foggy-ai-analysis` through DeepSeek Harness's native Skill provider API. Skills
|
|
109
|
+
are available in every DSH workspace without copying or symlinking `.agents`.
|
|
110
|
+
The current session `cwd` remains the workspace boundary for semantic drafts and
|
|
111
|
+
evidence.
|
|
112
|
+
An existing Harness session keeps its original workspace even if another workspace
|
|
113
|
+
becomes the default. Create a new session in the selected workspace when testing
|
|
114
|
+
model-file isolation; an isolated `DSH_HOME` alone does not change a session's
|
|
115
|
+
`cwd`. The `--workspace-root` option in the plugin install command is a pnpm
|
|
116
|
+
installation option, not a Harness workspace selector.
|
|
117
|
+
|
|
118
|
+
Opaque CLI profiles remain available for users who prefer them and default to
|
|
119
|
+
the private persistent `<dataRoot>/cli-profiles` directory, but they are not a
|
|
120
|
+
prerequisite for ordinary development. Composite onboarding commands are
|
|
121
|
+
idempotent: unchanged completed phases are resumed rather than re-adding a
|
|
122
|
+
datasource or re-registering a local Bundle. A resumed datasource checkpoint is
|
|
123
|
+
also reconciled against the live Runtime; if the datasource was removed outside
|
|
124
|
+
the wrapper, only datasource configuration, verification, and schema discovery
|
|
125
|
+
are resumed. Settings detects legacy temporary
|
|
126
|
+
profiles and offers an explicit, validated migration into the persistent store.
|
|
127
|
+
|
|
128
|
+
Private Python, CLI, Launcher, the analysis Skill, install state, and Runtime
|
|
129
|
+
state live in the user-level Foggy component directories. The managed CLI is intentionally isolated
|
|
130
|
+
and does not need to be on `PATH`. **Re-download / Repair** verifies the global
|
|
131
|
+
analysis Skill, backs up modified or outdated managed content, restores it, and
|
|
132
|
+
invalidates DSH's Skill catalog. The onboarding Skill is bundled with the plugin
|
|
133
|
+
and is restored by reinstalling or upgrading the plugin package.
|
|
134
|
+
|
|
135
|
+
The Foggy settings tab shows the persisted database/semantic onboarding stages,
|
|
136
|
+
offers pinned checks and repair for CLI, Launcher, and the managed analysis
|
|
137
|
+
Skill, private Python, and exports a private redacted diagnostics report. The report
|
|
138
|
+
includes bounded, sanitized tails of Runtime logs while refusing to read paths outside
|
|
139
|
+
the managed Runtime directory. Runtime start monitors the Launcher PID during
|
|
140
|
+
`wait-ready`, fails promptly if Java exits, and remains idempotent: an already-recorded
|
|
141
|
+
process is verified with `wait-ready` and `capabilities` instead of being treated as a
|
|
142
|
+
failed second start.
|
|
143
|
+
|
|
144
|
+
The same settings tab owns a persistent local Runtime port. New installations default
|
|
145
|
+
to `18166`; users can choose another port while Runtime is stopped. Startup checks the
|
|
146
|
+
same wildcard binding used by the Java server, so a conflicting application or Windows
|
|
147
|
+
port proxy produces an immediate, high-visibility error instead of a readiness timeout.
|
|
148
|
+
The CLI and Skills resolve the resulting stable Runtime URL from managed state.
|
|
149
|
+
|
|
150
|
+
For a successful standard QueryModel DSL call made through the native
|
|
151
|
+
`foggy_query` tool, Harness shows a compact result card below the completed
|
|
152
|
+
reply, outside the folded tool trace. A visible "Generated by Foggy plugin"
|
|
153
|
+
label distinguishes this programmatic record of executed results from the AI
|
|
154
|
+
reply. The card shows the model, namespace, row count, an optional five-row
|
|
155
|
+
result preview with DSL/SQL details, and **View data**. If a turn has more than six
|
|
156
|
+
successful queries, the first six are shown until the user expands the list.
|
|
157
|
+
The detailed DSL and execution record remains in the tool trace. Clicking
|
|
158
|
+
**View data** calls the configured Foggy MCP connector's `dataset.open_in_viewer`
|
|
159
|
+
tool through Harness's tool policy pipeline. Configure exactly one connector
|
|
160
|
+
that exposes this tool. Its transport retains the configured authorization
|
|
161
|
+
headers; the plugin does not put credentials in the browser contract and does
|
|
162
|
+
not fall back to anonymous HTTP link creation. Asking the assistant to open a
|
|
163
|
+
data view uses the same MCP tool. Grant-authorized links use the host's
|
|
164
|
+
server-managed service identity. The lite launcher's local development route
|
|
165
|
+
is accepted only when it matches the running managed loopback Runtime in
|
|
166
|
+
`none-dev-test-only` mode. That preview does not pass MCP Authorization to the
|
|
167
|
+
browser, and the UI identifies it as a local development preview. Protected
|
|
168
|
+
services must provide grant-authorized links; the plugin does not enable the
|
|
169
|
+
optional identity-provider module automatically.
|
|
170
|
+
The page re-executes the DSL against the current model and data rather than
|
|
171
|
+
freezing the original rows. Viewer persistence defaults to SQLite. On a host
|
|
172
|
+
with grant-authorized viewing, links can be given a TTL or revoked; each
|
|
173
|
+
browser session defaults to one day and has a separately configurable TTL.
|
|
174
|
+
The historical card can request a new link while the transcript, connector,
|
|
175
|
+
Runtime, and model are available. Explicit aggregate `having` conditions are
|
|
176
|
+
retained alongside detail-level `slice` conditions. At least one `slice` filter
|
|
177
|
+
is required for a preview. Unfiltered queries still show their results and a
|
|
178
|
+
filter hint. CTE preview is not included.
|
|
179
|
+
The Harness card retains the complete executed result; the web view displays
|
|
180
|
+
fields supported by the Runtime's model metadata.
|
|
181
|
+
The DataViewer page can export the current filtered and sorted model-backed
|
|
182
|
+
result to CSV (up to 10,000 rows). It refuses larger exports rather than
|
|
183
|
+
silently truncating them.
|
|
184
|
+
|
|
185
|
+
The native `foggy_query` tool uses the managed CLI's separately configured
|
|
186
|
+
Runtime authorization (for example `FOGGY_RUNTIME_AUTHORIZATION`). It does not
|
|
187
|
+
extract the MCP connector's headers. Verify the query tool and its identity
|
|
188
|
+
when demonstrating restricted data. MCP link creation and native CLI queries
|
|
189
|
+
remain separate authorization paths.
|
|
190
|
+
|
|
191
|
+
This beta remains a local dev/test integration. It does not automatically extend
|
|
192
|
+
local credentials or approvals into a formal environment. Production model
|
|
193
|
+
publication should use a separate manual or dedicated deployment workflow with
|
|
194
|
+
an explicit target, model Git commit/tag, credentials, verification, and
|
|
195
|
+
rollback plan.
|
|
196
|
+
|
|
197
|
+
See [`docs/PUBLIC-BETA-READINESS.md`](./docs/PUBLIC-BETA-READINESS.md) for the
|
|
198
|
+
tested public Beta scope, release gates, and stable-release blockers.
|
|
199
|
+
The DSH 0.2.1-rc.2 compatibility candidate is documented in
|
|
200
|
+
[`docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md`](./docs/RELEASE-CANDIDATE-0.4.3-DSH-0.2.0-RC.1.md).
|
|
201
|
+
The previous DSH 0.1.7-rc.2 candidate is documented in
|
|
202
|
+
[`docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.2.md`](./docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.2.md).
|
|
203
|
+
The earlier DSH 0.1.5-rc.2 candidate is documented in
|
|
204
|
+
[`docs/RELEASE-CANDIDATE-0.4.1-DSH-0.1.5-RC.1.md`](./docs/RELEASE-CANDIDATE-0.4.1-DSH-0.1.5-RC.1.md).
|
|
205
|
+
Native Windows acceptance instructions are in
|
|
206
|
+
[`docs/WINDOWS-BETA-ACCEPTANCE.md`](./docs/WINDOWS-BETA-ACCEPTANCE.md); database
|
|
207
|
+
credentials intentionally remain outside the public repository.
|
|
208
|
+
|
|
209
|
+
## Community discovery
|
|
210
|
+
|
|
211
|
+
DeepSeek Harness does not currently publish a first-party plugin marketplace.
|
|
212
|
+
For discoverability, this repository is intended to carry the GitHub
|
|
213
|
+
[`dsh-plugin`](https://github.com/topics/dsh-plugin) topic. Independent community
|
|
214
|
+
directories and their submission rules are tracked in
|
|
215
|
+
[`docs/COMMUNITY-MARKETPLACES.md`](./docs/COMMUNITY-MARKETPLACES.md); inclusion in
|
|
216
|
+
any directory is community curation, not an endorsement by DeepSeek or Foggy.
|
|
217
|
+
|
|
218
|
+
## Linux and WSL2 experience
|
|
219
|
+
|
|
220
|
+
Ubuntu and WSL2 users can use the checked-in preflighted installer under
|
|
221
|
+
[`experience/linux`](./experience/linux/README.md). It keeps DSH, its profile,
|
|
222
|
+
the project workspace, and Foggy data on the Linux-native filesystem.
|
|
@@ -1,16 +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.
|
|
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
CHANGED
|
@@ -1,6 +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'
|
|
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'
|
|
@@ -1,64 +1,64 @@
|
|
|
1
|
-
# DeepSeek Harness 社区插件目录准备
|
|
2
|
-
|
|
3
|
-
状态记录:2026-09-06。DeepSeek Harness 官方页面仍标注为开发者预览版,
|
|
4
|
-
官方公开入口是源码、开发者文档、GitHub `dsh-plugin` Topic 和社区讨论,
|
|
5
|
-
目前没有看到官方一方插件市场或官方审核收录入口。
|
|
6
|
-
|
|
7
|
-
## 推荐顺序
|
|
8
|
-
|
|
9
|
-
### 1. `awesome-dsh-plugin`(优先提交)
|
|
10
|
-
|
|
11
|
-
- 目录仓库:<https://github.com/awesome-dsh-plugin/awesome-dsh-plugin>
|
|
12
|
-
- 提交方式:向该仓库提交 PR,只新增一个
|
|
13
|
-
`data/plugins/foggy-projects__foggy-deepseek-harness-plugin.yml` 文件。
|
|
14
|
-
- 主要要求:真实可用代码、仓库至少存在 1 天、添加 `dsh-plugin` Topic、
|
|
15
|
-
描述准确且不使用夸张营销语句、根包声明 `dsh.bundle`。
|
|
16
|
-
- 可选增强:在 npm 发布包中保留正确的 `repository` 字段;如提供 GitHub
|
|
17
|
-
Release `.tgz`,可在条目中声明固定版本的 `tarball`。
|
|
18
|
-
- 评审说明:CI 检查格式和 manifest,维护者会阅读目标仓库;收录不等于
|
|
19
|
-
安全审计或官方认证。
|
|
20
|
-
|
|
21
|
-
建议条目草稿:
|
|
22
|
-
|
|
23
|
-
```yaml
|
|
24
|
-
url: https://github.com/foggy-projects/foggy-deepseek-harness-plugin
|
|
25
|
-
name: foggy-projects/foggy-deepseek-harness-plugin
|
|
26
|
-
category: tools
|
|
27
|
-
description:
|
|
28
|
-
en: Foggy Java data-analysis integration for DeepSeek Harness with a managed Runtime, CLI, Launcher, onboarding Skills, and semantic-layer workflows.
|
|
29
|
-
zh: 在 DeepSeek Harness 中管理 Foggy Java 数据分析 Runtime、CLI、Launcher 与 onboarding/语义查询 Skill,支持数据库接入和语义层建模。
|
|
30
|
-
```
|
|
31
|
-
|
|
32
|
-
### 2. `dsh-market`(市场应用,目录来自上游)
|
|
33
|
-
|
|
34
|
-
- 项目:<https://github.com/dsh-market/dsh-market>
|
|
35
|
-
- 它是可安装到 DSH 设置页的社区市场应用,本身不是目录数据源。
|
|
36
|
-
- 目录来自 `awesome-dsh-plugin`;其说明要求向上游目录提交 PR,
|
|
37
|
-
市场会自动同步,通常不需要重复提交到 `dsh-market`。
|
|
38
|
-
- 适合验证“一键安装”体验,但它不是 DeepSeek 官方产品。
|
|
39
|
-
|
|
40
|
-
### 3. `DSH-Plugins-Marketplace`(Topic 自动聚合)
|
|
41
|
-
|
|
42
|
-
- 项目:<https://github.com/bradeGithub/DSH-Plugins-Marketplace>
|
|
43
|
-
- 通过 GitHub `dsh-plugin` Topic 自动聚合,项目讨论中说明无需手工 PR,
|
|
44
|
-
Topic 出现后等待索引刷新即可。
|
|
45
|
-
- 它会安装到 DSH Web profile,适合做第二个发现入口;必须标注为第三方市场。
|
|
46
|
-
|
|
47
|
-
### 4. `dshplugin.app`(独立目录与证据页)
|
|
48
|
-
|
|
49
|
-
- 目录:<https://dshplugin.app/>
|
|
50
|
-
- 支持提交公开 GitHub 仓库,随后进行源码、manifest、依赖、安装路径和兼容性
|
|
51
|
-
信号分析。
|
|
52
|
-
- 页面明确声明其为独立社区项目,不隶属于 DeepSeek;“Indexed”不等于安全认证。
|
|
53
|
-
- 适合补充兼容性说明和安全信号展示,但不应把它描述为官方市场。
|
|
54
|
-
|
|
55
|
-
## 当前可执行清单
|
|
56
|
-
|
|
57
|
-
1. 保持当前 npm `rc` 预发布与 GitHub Release,不切换 `latest`。
|
|
58
|
-
2. 给 GitHub 仓库添加 `dsh-plugin` Topic;可同时保留
|
|
59
|
-
`deepseek-harness`、`data-analysis`、`semantic-layer` 等描述性 Topic。
|
|
60
|
-
3. 确认下一次 npm 发布继续携带 `repository`、`homepage`、`bugs` 和
|
|
61
|
-
`dsh-plugin` keywords,便于目录把 npm 包与源码仓库关联。
|
|
62
|
-
4. 优先向 `awesome-dsh-plugin` 提交上面的单文件 PR,再等待 `dsh-market`
|
|
63
|
-
同步;随后向 `dshplugin.app` 提交公开仓库 URL。
|
|
64
|
-
5. 对外文案统一使用“社区目录/第三方市场”,不使用“官方市场/官方认证”。
|
|
1
|
+
# DeepSeek Harness 社区插件目录准备
|
|
2
|
+
|
|
3
|
+
状态记录:2026-09-06。DeepSeek Harness 官方页面仍标注为开发者预览版,
|
|
4
|
+
官方公开入口是源码、开发者文档、GitHub `dsh-plugin` Topic 和社区讨论,
|
|
5
|
+
目前没有看到官方一方插件市场或官方审核收录入口。
|
|
6
|
+
|
|
7
|
+
## 推荐顺序
|
|
8
|
+
|
|
9
|
+
### 1. `awesome-dsh-plugin`(优先提交)
|
|
10
|
+
|
|
11
|
+
- 目录仓库:<https://github.com/awesome-dsh-plugin/awesome-dsh-plugin>
|
|
12
|
+
- 提交方式:向该仓库提交 PR,只新增一个
|
|
13
|
+
`data/plugins/foggy-projects__foggy-deepseek-harness-plugin.yml` 文件。
|
|
14
|
+
- 主要要求:真实可用代码、仓库至少存在 1 天、添加 `dsh-plugin` Topic、
|
|
15
|
+
描述准确且不使用夸张营销语句、根包声明 `dsh.bundle`。
|
|
16
|
+
- 可选增强:在 npm 发布包中保留正确的 `repository` 字段;如提供 GitHub
|
|
17
|
+
Release `.tgz`,可在条目中声明固定版本的 `tarball`。
|
|
18
|
+
- 评审说明:CI 检查格式和 manifest,维护者会阅读目标仓库;收录不等于
|
|
19
|
+
安全审计或官方认证。
|
|
20
|
+
|
|
21
|
+
建议条目草稿:
|
|
22
|
+
|
|
23
|
+
```yaml
|
|
24
|
+
url: https://github.com/foggy-projects/foggy-deepseek-harness-plugin
|
|
25
|
+
name: foggy-projects/foggy-deepseek-harness-plugin
|
|
26
|
+
category: tools
|
|
27
|
+
description:
|
|
28
|
+
en: Foggy Java data-analysis integration for DeepSeek Harness with a managed Runtime, CLI, Launcher, onboarding Skills, and semantic-layer workflows.
|
|
29
|
+
zh: 在 DeepSeek Harness 中管理 Foggy Java 数据分析 Runtime、CLI、Launcher 与 onboarding/语义查询 Skill,支持数据库接入和语义层建模。
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
### 2. `dsh-market`(市场应用,目录来自上游)
|
|
33
|
+
|
|
34
|
+
- 项目:<https://github.com/dsh-market/dsh-market>
|
|
35
|
+
- 它是可安装到 DSH 设置页的社区市场应用,本身不是目录数据源。
|
|
36
|
+
- 目录来自 `awesome-dsh-plugin`;其说明要求向上游目录提交 PR,
|
|
37
|
+
市场会自动同步,通常不需要重复提交到 `dsh-market`。
|
|
38
|
+
- 适合验证“一键安装”体验,但它不是 DeepSeek 官方产品。
|
|
39
|
+
|
|
40
|
+
### 3. `DSH-Plugins-Marketplace`(Topic 自动聚合)
|
|
41
|
+
|
|
42
|
+
- 项目:<https://github.com/bradeGithub/DSH-Plugins-Marketplace>
|
|
43
|
+
- 通过 GitHub `dsh-plugin` Topic 自动聚合,项目讨论中说明无需手工 PR,
|
|
44
|
+
Topic 出现后等待索引刷新即可。
|
|
45
|
+
- 它会安装到 DSH Web profile,适合做第二个发现入口;必须标注为第三方市场。
|
|
46
|
+
|
|
47
|
+
### 4. `dshplugin.app`(独立目录与证据页)
|
|
48
|
+
|
|
49
|
+
- 目录:<https://dshplugin.app/>
|
|
50
|
+
- 支持提交公开 GitHub 仓库,随后进行源码、manifest、依赖、安装路径和兼容性
|
|
51
|
+
信号分析。
|
|
52
|
+
- 页面明确声明其为独立社区项目,不隶属于 DeepSeek;“Indexed”不等于安全认证。
|
|
53
|
+
- 适合补充兼容性说明和安全信号展示,但不应把它描述为官方市场。
|
|
54
|
+
|
|
55
|
+
## 当前可执行清单
|
|
56
|
+
|
|
57
|
+
1. 保持当前 npm `rc` 预发布与 GitHub Release,不切换 `latest`。
|
|
58
|
+
2. 给 GitHub 仓库添加 `dsh-plugin` Topic;可同时保留
|
|
59
|
+
`deepseek-harness`、`data-analysis`、`semantic-layer` 等描述性 Topic。
|
|
60
|
+
3. 确认下一次 npm 发布继续携带 `repository`、`homepage`、`bugs` 和
|
|
61
|
+
`dsh-plugin` keywords,便于目录把 npm 包与源码仓库关联。
|
|
62
|
+
4. 优先向 `awesome-dsh-plugin` 提交上面的单文件 PR,再等待 `dsh-market`
|
|
63
|
+
同步;随后向 `dshplugin.app` 提交公开仓库 URL。
|
|
64
|
+
5. 对外文案统一使用“社区目录/第三方市场”,不使用“官方市场/官方认证”。
|