@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.
- package/README.md +222 -173
- 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 -0
- package/docs/RELEASE-CANDIDATE-0.4.2-DSH-0.1.7-RC.5.md +27 -0
- 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 -906
- 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 -104
- 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 +25 -15
- 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 -3681
- 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
|
@@ -1,50 +1,50 @@
|
|
|
1
|
-
# Foggy DeepSeek Harness plugin 0.4.2-rc.2
|
|
2
|
-
|
|
3
|
-
This pre-release targets DeepSeek Harness `0.1.7-rc.2` with system Node.js
|
|
4
|
-
`>=24.0.0` and Java 17+. It stays on the dedicated `dsh017` npm channel;
|
|
5
|
-
the existing `beta`, `rc`, and `dsh015` channels are unchanged.
|
|
6
|
-
|
|
7
|
-
## Changes since 0.4.2-rc.1
|
|
8
|
-
|
|
9
|
-
- Publish each polled operation state to the settings UI so initialization and
|
|
10
|
-
Runtime startup progress remain visible while the operation runs. Known
|
|
11
|
-
progress phases now use the selected UI language instead of raw English
|
|
12
|
-
backend messages.
|
|
13
|
-
- Use the managed CLI's `wait-ready` response as Doctor's Runtime health check.
|
|
14
|
-
Process inspection remains diagnostic context, so an unavailable Windows
|
|
15
|
-
process query does not incorrectly label a healthy Runtime as stale.
|
|
16
|
-
- Clarify workspace behavior: an existing DSH session retains its original
|
|
17
|
-
`cwd` when the default workspace changes. Create a new session in the chosen
|
|
18
|
-
workspace to isolate new semantic-model files.
|
|
19
|
-
|
|
20
|
-
## Acceptance
|
|
21
|
-
|
|
22
|
-
- On a fresh Windows component/data root, the settings page visibly showed
|
|
23
|
-
initialization progress during the private Python download (23%, step 2/7).
|
|
24
|
-
CLI `0.1.23`, Launcher `0.1.21`, and analysis/query Skills `0.1.18` installed.
|
|
25
|
-
- The default Runtime port `18166` was occupied by an earlier acceptance
|
|
26
|
-
Runtime. The new profile failed promptly at port preflight and displayed an
|
|
27
|
-
explicit red port-conflict alert. Saving port `18167` in the isolated data
|
|
28
|
-
root and starting the managed Launcher succeeded. Strict Doctor passed all
|
|
29
|
-
eight checks; CLI `wait-ready` and `capabilities` reported a healthy Java
|
|
30
|
-
Runtime at `http://127.0.0.1:18167`.
|
|
31
|
-
- A Harness chat created a separate TM/QM and a bounded 2024 monthly paid
|
|
32
|
-
amount query against the local demo `fact_order` table. Runtime model
|
|
33
|
-
describe, query validate, and query execute agreed with the four rows shown
|
|
34
|
-
in the chat. This remains development/test data, not production deployment.
|
|
35
|
-
- The candidate tarball was installed over the local `0.4.2-rc.1` test profile.
|
|
36
|
-
pnpm's lockfile policy passed; the installed client matched the packed source,
|
|
37
|
-
DSH Web restarted without plugin activation errors, and its authenticated
|
|
38
|
-
page returned HTTP 200. The existing component install state remained intact,
|
|
39
|
-
with Runtime still healthy on port `18167` and strict Doctor again passing
|
|
40
|
-
all eight checks.
|
|
41
|
-
|
|
42
|
-
Install the exact version with:
|
|
43
|
-
|
|
44
|
-
```powershell
|
|
45
|
-
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.2
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
Publish this pre-release under the `dsh017` dist-tag only, leaving other npm
|
|
49
|
-
channels unchanged. The Linux `experience/linux/prepare.sh` entry is pinned to
|
|
50
|
-
the matching Git tag and becomes usable once that tag is published.
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.2-rc.2
|
|
2
|
+
|
|
3
|
+
This pre-release targets DeepSeek Harness `0.1.7-rc.2` with system Node.js
|
|
4
|
+
`>=24.0.0` and Java 17+. It stays on the dedicated `dsh017` npm channel;
|
|
5
|
+
the existing `beta`, `rc`, and `dsh015` channels are unchanged.
|
|
6
|
+
|
|
7
|
+
## Changes since 0.4.2-rc.1
|
|
8
|
+
|
|
9
|
+
- Publish each polled operation state to the settings UI so initialization and
|
|
10
|
+
Runtime startup progress remain visible while the operation runs. Known
|
|
11
|
+
progress phases now use the selected UI language instead of raw English
|
|
12
|
+
backend messages.
|
|
13
|
+
- Use the managed CLI's `wait-ready` response as Doctor's Runtime health check.
|
|
14
|
+
Process inspection remains diagnostic context, so an unavailable Windows
|
|
15
|
+
process query does not incorrectly label a healthy Runtime as stale.
|
|
16
|
+
- Clarify workspace behavior: an existing DSH session retains its original
|
|
17
|
+
`cwd` when the default workspace changes. Create a new session in the chosen
|
|
18
|
+
workspace to isolate new semantic-model files.
|
|
19
|
+
|
|
20
|
+
## Acceptance
|
|
21
|
+
|
|
22
|
+
- On a fresh Windows component/data root, the settings page visibly showed
|
|
23
|
+
initialization progress during the private Python download (23%, step 2/7).
|
|
24
|
+
CLI `0.1.23`, Launcher `0.1.21`, and analysis/query Skills `0.1.18` installed.
|
|
25
|
+
- The default Runtime port `18166` was occupied by an earlier acceptance
|
|
26
|
+
Runtime. The new profile failed promptly at port preflight and displayed an
|
|
27
|
+
explicit red port-conflict alert. Saving port `18167` in the isolated data
|
|
28
|
+
root and starting the managed Launcher succeeded. Strict Doctor passed all
|
|
29
|
+
eight checks; CLI `wait-ready` and `capabilities` reported a healthy Java
|
|
30
|
+
Runtime at `http://127.0.0.1:18167`.
|
|
31
|
+
- A Harness chat created a separate TM/QM and a bounded 2024 monthly paid
|
|
32
|
+
amount query against the local demo `fact_order` table. Runtime model
|
|
33
|
+
describe, query validate, and query execute agreed with the four rows shown
|
|
34
|
+
in the chat. This remains development/test data, not production deployment.
|
|
35
|
+
- The candidate tarball was installed over the local `0.4.2-rc.1` test profile.
|
|
36
|
+
pnpm's lockfile policy passed; the installed client matched the packed source,
|
|
37
|
+
DSH Web restarted without plugin activation errors, and its authenticated
|
|
38
|
+
page returned HTTP 200. The existing component install state remained intact,
|
|
39
|
+
with Runtime still healthy on port `18167` and strict Doctor again passing
|
|
40
|
+
all eight checks.
|
|
41
|
+
|
|
42
|
+
Install the exact version with:
|
|
43
|
+
|
|
44
|
+
```powershell
|
|
45
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.2
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Publish this pre-release under the `dsh017` dist-tag only, leaving other npm
|
|
49
|
+
channels unchanged. The Linux `experience/linux/prepare.sh` entry is pinned to
|
|
50
|
+
the matching Git tag and becomes usable once that tag is published.
|
|
@@ -1,34 +1,34 @@
|
|
|
1
|
-
# Foggy DeepSeek Harness plugin 0.4.2-rc.3
|
|
2
|
-
|
|
3
|
-
This pre-release targets DeepSeek Harness `0.1.7-rc.2` on the `dsh017` npm
|
|
4
|
-
channel. It keeps the `beta`, `rc`, and `dsh015` channels unchanged.
|
|
5
|
-
|
|
6
|
-
## Changes since 0.4.2-rc.2
|
|
7
|
-
|
|
8
|
-
- Add a native `foggy_query` tool for bounded, read-only standard QueryModel DSL
|
|
9
|
-
validation and execution. Successful calls render a Harness card with the
|
|
10
|
-
model, namespace, row count, DSL, SQL, and result.
|
|
11
|
-
- Create a DataViewer preview URL only when the card's **Open DataViewer**
|
|
12
|
-
action is clicked. Links are short-lived local development previews, not
|
|
13
|
-
frozen result snapshots. An expired link can be regenerated from the card.
|
|
14
|
-
- Update the managed Launcher to `0.1.22`. Its lite profile serves the existing
|
|
15
|
-
DataViewer UI using a bounded in-memory cache without MongoDB, and its start
|
|
16
|
-
scripts bind to loopback. Runtime restarts invalidate preview links.
|
|
17
|
-
- Do not claim CTE preview support in this release. Existing CTE execution
|
|
18
|
-
remains available through its prior CLI path without a DataViewer card.
|
|
19
|
-
|
|
20
|
-
## Acceptance scope
|
|
21
|
-
|
|
22
|
-
- Plugin checks: `npm run check`, Node tests, Python onboarding tests, and an
|
|
23
|
-
isolated DSH `0.1.7-rc.2` web boot with the Foggy settings tab visible.
|
|
24
|
-
- Launcher: formal release gate, default and Analytics Console smokes, six
|
|
25
|
-
GitHub assets, and SHA-256 verification.
|
|
26
|
-
- End-to-end DSL: an isolated Java Runtime with SQLite demo data validates and
|
|
27
|
-
executes a QueryModel query. A click-generated DataViewer link shows actual
|
|
28
|
-
columns and six rows in the browser.
|
|
29
|
-
|
|
30
|
-
Install the exact version with:
|
|
31
|
-
|
|
32
|
-
```powershell
|
|
33
|
-
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.3
|
|
34
|
-
```
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.2-rc.3
|
|
2
|
+
|
|
3
|
+
This pre-release targets DeepSeek Harness `0.1.7-rc.2` on the `dsh017` npm
|
|
4
|
+
channel. It keeps the `beta`, `rc`, and `dsh015` channels unchanged.
|
|
5
|
+
|
|
6
|
+
## Changes since 0.4.2-rc.2
|
|
7
|
+
|
|
8
|
+
- Add a native `foggy_query` tool for bounded, read-only standard QueryModel DSL
|
|
9
|
+
validation and execution. Successful calls render a Harness card with the
|
|
10
|
+
model, namespace, row count, DSL, SQL, and result.
|
|
11
|
+
- Create a DataViewer preview URL only when the card's **Open DataViewer**
|
|
12
|
+
action is clicked. Links are short-lived local development previews, not
|
|
13
|
+
frozen result snapshots. An expired link can be regenerated from the card.
|
|
14
|
+
- Update the managed Launcher to `0.1.22`. Its lite profile serves the existing
|
|
15
|
+
DataViewer UI using a bounded in-memory cache without MongoDB, and its start
|
|
16
|
+
scripts bind to loopback. Runtime restarts invalidate preview links.
|
|
17
|
+
- Do not claim CTE preview support in this release. Existing CTE execution
|
|
18
|
+
remains available through its prior CLI path without a DataViewer card.
|
|
19
|
+
|
|
20
|
+
## Acceptance scope
|
|
21
|
+
|
|
22
|
+
- Plugin checks: `npm run check`, Node tests, Python onboarding tests, and an
|
|
23
|
+
isolated DSH `0.1.7-rc.2` web boot with the Foggy settings tab visible.
|
|
24
|
+
- Launcher: formal release gate, default and Analytics Console smokes, six
|
|
25
|
+
GitHub assets, and SHA-256 verification.
|
|
26
|
+
- End-to-end DSL: an isolated Java Runtime with SQLite demo data validates and
|
|
27
|
+
executes a QueryModel query. A click-generated DataViewer link shows actual
|
|
28
|
+
columns and six rows in the browser.
|
|
29
|
+
|
|
30
|
+
Install the exact version with:
|
|
31
|
+
|
|
32
|
+
```powershell
|
|
33
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.3
|
|
34
|
+
```
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.2-rc.4
|
|
2
|
+
|
|
3
|
+
This pre-release targets DeepSeek Harness `0.1.7-rc.2` and remains on the
|
|
4
|
+
`dsh017` npm channel. The `beta`, `rc`, `dsh015`, and `latest` channels are
|
|
5
|
+
unchanged.
|
|
6
|
+
|
|
7
|
+
## Fixes since 0.4.2-rc.3
|
|
8
|
+
|
|
9
|
+
- Register `foggy_query` with Harness's existing tool runtime instead of
|
|
10
|
+
installing a second private `@deepseek-ai/dsh-tools` copy. The duplicate
|
|
11
|
+
runtime caused `Cannot read properties of undefined (reading 'prepare')`
|
|
12
|
+
before the DSL query reached Foggy Runtime.
|
|
13
|
+
- Allow a normal Launcher upgrade to replace a same-named asset only when the
|
|
14
|
+
existing file still matches the SHA-256 recorded for the previous installed
|
|
15
|
+
version. The previous file is backed up; unexpected file changes remain
|
|
16
|
+
fail-closed. Downloads are verified before replacing the existing file.
|
|
17
|
+
- Convert Query DSL `groupBy` and `orderBy` string shorthand into equivalent
|
|
18
|
+
object entries when creating a DataViewer preview. A valid, executed query
|
|
19
|
+
is no longer incorrectly labeled as ineligible for preview.
|
|
20
|
+
- Warn that the current DataViewer table can omit ad-hoc aggregate columns
|
|
21
|
+
even though the query card contains the complete result. This is an engine
|
|
22
|
+
display limitation, not a failed Query DSL execution.
|
|
23
|
+
|
|
24
|
+
The DSL-only DataViewer behavior from rc.3 is unchanged: a preview URL is
|
|
25
|
+
created only when the user clicks the successful query card's button. CTE
|
|
26
|
+
preview is not included.
|
|
27
|
+
|
|
28
|
+
Install the exact version with:
|
|
29
|
+
|
|
30
|
+
```powershell
|
|
31
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.4
|
|
32
|
+
```
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.2-rc.5
|
|
2
|
+
|
|
3
|
+
This pre-release targets DeepSeek Harness `0.1.7-rc.2` and stays on the
|
|
4
|
+
dedicated `dsh017` npm channel. The `beta`, `rc`, `dsh015`, and `latest`
|
|
5
|
+
channels remain unchanged.
|
|
6
|
+
|
|
7
|
+
## Changes since 0.4.2-rc.4
|
|
8
|
+
|
|
9
|
+
- Pin Runtime Launcher `0.1.23`, which includes the lite-profile DataViewer
|
|
10
|
+
preview page without requiring the Analytics Console or MongoDB.
|
|
11
|
+
- The DataViewer page puts readable query details and the executed DSL side by
|
|
12
|
+
side, supports copying DSL, and places refresh and CSV export below the
|
|
13
|
+
details. Query links are created on demand from successful DSL result cards.
|
|
14
|
+
- The table supports local filtering and exports the current filtered result.
|
|
15
|
+
CTE preview is not included. Preview links are process-local development
|
|
16
|
+
aids, not durable production shares.
|
|
17
|
+
|
|
18
|
+
The plugin keeps the current Harness `0.1.7-rc.2` tool integration. The
|
|
19
|
+
Runtime is updated only when the user selects **Update components** or
|
|
20
|
+
**Update and start** in Foggy settings; package installation does not restart
|
|
21
|
+
an existing Runtime.
|
|
22
|
+
|
|
23
|
+
Install the exact version with:
|
|
24
|
+
|
|
25
|
+
```powershell
|
|
26
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.2-rc.5
|
|
27
|
+
```
|
|
@@ -0,0 +1,96 @@
|
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.3-rc.1
|
|
2
|
+
|
|
3
|
+
This pre-release targets the published DeepSeek Harness `0.2.0-rc.2`.
|
|
4
|
+
Npm publication uses the dedicated `dsh020` channel; `latest`, `beta`, `rc`, `dsh015`,
|
|
5
|
+
and `dsh017` remain unchanged. GitHub release assets can be installed directly
|
|
6
|
+
without relying on the npm channel.
|
|
7
|
+
|
|
8
|
+
## Changes since 0.4.2-rc.5
|
|
9
|
+
|
|
10
|
+
- Result-card **View data** uses the configured Foggy MCP connector's
|
|
11
|
+
`dataset.open_in_viewer` tool through Harness's tool policy pipeline.
|
|
12
|
+
The connector keeps its configured authorization headers; browser-side
|
|
13
|
+
inputs contain the model, namespace, and query DSL. Missing or ambiguous
|
|
14
|
+
connectors and policy denials fail without an anonymous HTTP fallback.
|
|
15
|
+
- The assistant's explicit open-view tool and the card entry share the same
|
|
16
|
+
service authorization scope. The web view opens without an extra login form.
|
|
17
|
+
- Explicit `having` conditions remain in the card/viewer DSL alongside
|
|
18
|
+
detail-level `slice`; the plugin does not convert one into the other.
|
|
19
|
+
- Pin CLI and Launcher `0.1.24`. The Launcher stores viewer links in SQLite by
|
|
20
|
+
default, with configurable link lifetime (no expiry by default) and a
|
|
21
|
+
separately configurable browser-session lifetime (one day by default).
|
|
22
|
+
Existing URLs may also be revoked. The page re-executes the saved query and
|
|
23
|
+
follows its service authorization scope; it is not a frozen result snapshot.
|
|
24
|
+
- Update DSH peer requirements and the Linux experience entry to `0.2.0-rc.2`.
|
|
25
|
+
Private Python stays on `3.12.13` and both Foggy Skills stay on their latest
|
|
26
|
+
published `0.1.18` release. Managed component updates remain explicit.
|
|
27
|
+
|
|
28
|
+
## Install and upgrade
|
|
29
|
+
|
|
30
|
+
Use Node.js 24+ and Java 17+. With the `0.2.0-rc.2` DSH command installed:
|
|
31
|
+
|
|
32
|
+
```powershell
|
|
33
|
+
dsh --version
|
|
34
|
+
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.3-rc.1.tgz
|
|
35
|
+
```
|
|
36
|
+
|
|
37
|
+
After npm publication, the equivalent exact-version installation is:
|
|
38
|
+
|
|
39
|
+
```powershell
|
|
40
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@0.4.3-rc.1
|
|
41
|
+
```
|
|
42
|
+
|
|
43
|
+
The pinned launcher command can also be selected without changing a global DSH
|
|
44
|
+
installation:
|
|
45
|
+
|
|
46
|
+
```powershell
|
|
47
|
+
npx --yes @deepseek-ai/dsh@0.2.0-rc.2 plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.3-rc.1.tgz
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
Restart the Harness web process after the package upgrade. In **Settings →
|
|
51
|
+
Built-in plugins → Foggy Data Analysis**, confirm plugin `0.4.3-rc.1`, then stop the
|
|
52
|
+
managed Runtime and choose **Update components** before starting it again.
|
|
53
|
+
The page reports installed and target component versions. Plugin installation
|
|
54
|
+
does not replace or restart an already-running Runtime.
|
|
55
|
+
|
|
56
|
+
Configure exactly one Foggy MCP connector exposing `dataset.open_in_viewer`.
|
|
57
|
+
Keep its authorization headers in the private connector configuration. Neither
|
|
58
|
+
the video screenshots nor the public release evidence should show launch
|
|
59
|
+
tokens, viewer-link fragments, cookies, or credentials.
|
|
60
|
+
|
|
61
|
+
## Acceptance evidence
|
|
62
|
+
|
|
63
|
+
Windows API/package acceptance on 2026-10-02 uses Node.js `24.19.0` and a
|
|
64
|
+
separate npm installation of DSH `0.2.0-rc.2`; it does not modify the user's
|
|
65
|
+
Harness profile or launch a web server. The packed gateway loads against the
|
|
66
|
+
actual DSH Typert and Skill services. The actual DSH tool runtime successfully
|
|
67
|
+
dispatches a synthetic MCP viewer call and blocks it under an explicit policy
|
|
68
|
+
denial. Client contracts retain `conversation.chat.turnTail`, `turnDataSource`,
|
|
69
|
+
and tool-root records. The completed-turn card rendering regression and the
|
|
70
|
+
onboarding regression remain part of the full test gate.
|
|
71
|
+
|
|
72
|
+
The additional API acceptance gate is repeatable with:
|
|
73
|
+
|
|
74
|
+
```powershell
|
|
75
|
+
$env:FOGGY_DSH_COMPAT_ROOT = '<isolated installation containing DSH and the packed plugin>'
|
|
76
|
+
npm run check
|
|
77
|
+
npm test
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Without this environment variable the three isolated API tests are reported as
|
|
81
|
+
skipped. Release acceptance must set it. Browser UI and real-data acceptance is
|
|
82
|
+
a separate post-publication check; passing an API/package test is not a claim
|
|
83
|
+
that a native Windows screenshot or real model query has already been verified.
|
|
84
|
+
|
|
85
|
+
## Authorization review boundary
|
|
86
|
+
|
|
87
|
+
The two viewer entry points inherit the MCP connector's service authorization.
|
|
88
|
+
The native `foggy_query` tool still validates and executes through the managed
|
|
89
|
+
CLI. Its Runtime authorization is configured separately, for example through
|
|
90
|
+
`FOGGY_RUNTIME_AUTHORIZATION`; this release does not extract MCP headers for
|
|
91
|
+
native CLI queries. A restricted-service demonstration must verify the actual
|
|
92
|
+
query tool and its matching authorization, then generate the viewer through
|
|
93
|
+
that service's MCP connector. This is service authorization, not a personal
|
|
94
|
+
login or a unified authorization protocol. The release review verifies the
|
|
95
|
+
MCP adapter and tool-policy denial without claiming that all query entry points
|
|
96
|
+
automatically share one identity.
|
|
@@ -0,0 +1,135 @@
|
|
|
1
|
+
# Foggy DeepSeek Harness plugin 0.4.4-rc.1
|
|
2
|
+
|
|
3
|
+
This candidate adds Launcher/CLI version selection and targets the published
|
|
4
|
+
DeepSeek Harness `0.2.1-rc.2` (`latest`). The `0.2.1-rc.4` (`next`) SDK is also
|
|
5
|
+
included in compatibility acceptance. Node.js 24+ and Java 17+ are required.
|
|
6
|
+
|
|
7
|
+
The settings page also provides a **Tutorial** link to
|
|
8
|
+
[ai-data.qlfloor.com](https://ai-data.qlfloor.com/) in its documentation section.
|
|
9
|
+
|
|
10
|
+
Native-host acceptance also fixed start/stop commands when download caches are
|
|
11
|
+
configured, completed the host's existing repair/diagnostics remote descriptors,
|
|
12
|
+
and ensured settings keep polling when operation completion races with status
|
|
13
|
+
probes. The current page refreshes to the new Runtime/component state without
|
|
14
|
+
requiring the user to close and reopen settings.
|
|
15
|
+
|
|
16
|
+
Bash entrypoints are normalized to LF and protected by `.gitattributes` so a
|
|
17
|
+
Windows-built npm package executes correctly on Linux and WSL2.
|
|
18
|
+
|
|
19
|
+
## Component versions
|
|
20
|
+
|
|
21
|
+
The Foggy settings page checks the fixed official GitHub repositories when
|
|
22
|
+
opened and every six hours while open. **Check for updates** forces a refresh.
|
|
23
|
+
It distinguishes installed versions, upstream latest versions, and the defaults
|
|
24
|
+
validated with this plugin. Prereleases are labeled. Checks never download or
|
|
25
|
+
activate a runtime component.
|
|
26
|
+
|
|
27
|
+
Select a version, stop Runtime, and choose **Download and use**. Launcher and
|
|
28
|
+
CLI choices are independent and persist across plugin upgrades. Saved downloads
|
|
29
|
+
can be selected again for offline rollback. A failed download does not change
|
|
30
|
+
the active install state. New versions use separate Launcher and CLI virtual
|
|
31
|
+
environment directories, retaining older components and their verified assets.
|
|
32
|
+
Runtime starts and managed component operations share a user-directory lock.
|
|
33
|
+
|
|
34
|
+
Only assets from the official `foggy-projects/foggy-data-mcp-bridge` and
|
|
35
|
+
`foggy-projects/foggy-runtime-cli` releases are accepted. Resolution checks
|
|
36
|
+
SHA256SUMS, GitHub digests when supplied, and the release manifests before the
|
|
37
|
+
existing installer verifies the downloaded bytes. Unsupported or incomplete
|
|
38
|
+
releases cannot be activated. The minimum selectable version is `0.1.24`.
|
|
39
|
+
Network failures retain cached release information and do not block the
|
|
40
|
+
installed Runtime; failed checks are retried after fifteen minutes or manually.
|
|
41
|
+
|
|
42
|
+
Validated bundled defaults:
|
|
43
|
+
|
|
44
|
+
| Component | Version |
|
|
45
|
+
| --- | --- |
|
|
46
|
+
| Launcher / Java Runtime | 0.1.46 |
|
|
47
|
+
| Runtime CLI | 0.1.25 |
|
|
48
|
+
| Analysis / Semantic Query Skills | 0.1.18 |
|
|
49
|
+
| Private Python | 3.12.13 |
|
|
50
|
+
|
|
51
|
+
Launcher 0.1.46 includes Compose/time-plan stability fixes. CLI 0.1.25 fixes
|
|
52
|
+
member-query routes and error handling. Analytics Console remains opt-in and
|
|
53
|
+
this candidate does not add a Console settings entry.
|
|
54
|
+
|
|
55
|
+
## Install and upgrade
|
|
56
|
+
|
|
57
|
+
The new `engines.dsh` declaration makes the supported host range explicit.
|
|
58
|
+
Upgrade Harness to `0.2.1-rc.2` or a compatible newer 0.2.x host before installing
|
|
59
|
+
this candidate. Older host users can keep their corresponding previous plugin
|
|
60
|
+
line. A new npm publication should use `dsh021`, preserving the existing
|
|
61
|
+
`latest`, `beta`, `rc`, `dsh015`, `dsh017`, and `dsh020` tags.
|
|
62
|
+
|
|
63
|
+
```powershell
|
|
64
|
+
dsh plugin --profile web add --workspace-root ./foggy-projects-deepseek-harness-plugin-0.4.4-rc.1.tgz
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
After npm publication, the equivalent channel installation is:
|
|
68
|
+
|
|
69
|
+
```powershell
|
|
70
|
+
dsh plugin --profile web add --workspace-root @foggy-projects/deepseek-harness-plugin@dsh021
|
|
71
|
+
```
|
|
72
|
+
|
|
73
|
+
Restart Harness after installing the package. Open **Settings → Built-in plugins
|
|
74
|
+
→ Foggy Data Analysis**. Existing installations can stop Runtime and use
|
|
75
|
+
**Update components** to apply new defaults to components without a saved user
|
|
76
|
+
selection, or choose Launcher/CLI versions individually. First-time users
|
|
77
|
+
initialize Foggy before selecting alternative component versions.
|
|
78
|
+
|
|
79
|
+
## Acceptance
|
|
80
|
+
|
|
81
|
+
Run syntax and regression checks with Node.js 24. Real DSH API/package acceptance
|
|
82
|
+
must point to an isolated installation containing DSH and the final packed
|
|
83
|
+
plugin; omitting this configuration skips those checks and is insufficient for
|
|
84
|
+
release acceptance.
|
|
85
|
+
|
|
86
|
+
```powershell
|
|
87
|
+
$env:FOGGY_DSH_COMPAT_ROOT = '<isolated DSH 0.2.1-rc.2 installation>'
|
|
88
|
+
$env:FOGGY_COMPONENT_RELEASE_LIVE_TEST = '1'
|
|
89
|
+
npm run check
|
|
90
|
+
npm test
|
|
91
|
+
|
|
92
|
+
$env:FOGGY_DSH_COMPAT_ROOT = '<isolated DSH 0.2.1-rc.4 installation>'
|
|
93
|
+
$env:FOGGY_DSH_COMPAT_VERSION = '0.2.1-rc.4'
|
|
94
|
+
npm test
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
The API gates cover the host's official plugin compatibility evaluator, gateway
|
|
98
|
+
and native Skill loading, the actual MCP adapter/tool-policy denial, and the
|
|
99
|
+
completed-turn client contract. UI acceptance uses the real client component
|
|
100
|
+
with an isolated mock API; it is separate from Runtime acceptance.
|
|
101
|
+
|
|
102
|
+
Windows Runtime acceptance covers an old 0.1.24 installation, upgrade to the
|
|
103
|
+
new defaults, Java 17 startup and capabilities, explicit stop, and offline
|
|
104
|
+
component rollback. Publication requires preserving these checks and packaging
|
|
105
|
+
the final source with an updated checksum and release manifest.
|
|
106
|
+
|
|
107
|
+
Viewer creation continues through the configured MCP connector and tool policy.
|
|
108
|
+
Grant-authorized `/data-viewer/open#...` links retain their existing validation.
|
|
109
|
+
The standard lite launcher's development viewer route is accepted only for the
|
|
110
|
+
currently running managed loopback Runtime in `none-dev-test-only` mode, with
|
|
111
|
+
matching port, model, and opaque query ID. The UI identifies that route as a
|
|
112
|
+
local development preview: it does not carry MCP Authorization into the browser.
|
|
113
|
+
Other or protected services must supply a grant-authorized link. The plugin
|
|
114
|
+
does not anonymously create a replacement link or blindly enable the optional
|
|
115
|
+
authorization module, which requires a host-provided identity provider.
|
|
116
|
+
|
|
117
|
+
Viewer requests now require at least one detail-level `slice` filter. Unfiltered
|
|
118
|
+
queries continue to display their results and explain the preview requirement;
|
|
119
|
+
the plugin does not synthesize filters. Native queries keep their separately
|
|
120
|
+
configured CLI Runtime authorization; transport headers are not extracted from
|
|
121
|
+
MCP. This release does not unify those scopes.
|
|
122
|
+
|
|
123
|
+
The published Skill 0.1.18 demonstration requires explicit `salesdrop` →
|
|
124
|
+
`default` datasource binding before replay with Launcher 0.1.46; the normal
|
|
125
|
+
plugin onboarding already binds namespaces. Its full question bank also has a
|
|
126
|
+
pre-existing CLI source-field precheck that rejects SD-001's derived caption
|
|
127
|
+
field. The unchanged SD-001 payload passes direct Runtime validation/execution.
|
|
128
|
+
Do not claim the legacy full question bank passed unchanged.
|
|
129
|
+
|
|
130
|
+
## Recorded platform acceptance (2026-10-27)
|
|
131
|
+
|
|
132
|
+
- The actual Harness 0.2.1-rc.2 Web host passed 21 native settings assertions, including official CLI installation, private Python initialization, online release checks, real downloads, explicit switching, host restart persistence, rollback, diagnostics, and the Tutorial link. Browser errors: zero.
|
|
133
|
+
- WSL2 Ubuntu 24.04 passed 13 real installation/Runtime/rollback/failure-preservation phases and 16 native component/locking tests. All eight Bash entrypoints passed LF, syntax and help checks; private-Python manifest resolution and the Linux installer dry-run passed.
|
|
134
|
+
- The WSL environment had a DNS failure. Official assets were downloaded and SHA256-verified on Windows, then tested through the Linux-native cache. WSL online cold downloads are not claimed. No system packages or user profiles were changed.
|
|
135
|
+
- Final packed SDK test counts and artifact hashes are recorded in the attached release manifest.
|