triss-dsh-provider-bundle 0.35.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 ayleen
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,76 @@
1
+ # triss-dsh-provider-bundle
2
+
3
+ A configuration-only [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (`dsh`) provider bundle. It activates three provider routes that already exist in the `@earendil-works/pi-ai` catalogue resolved by your Harness installation — no new transport adapter, endpoints, or model metadata are bundled.
4
+
5
+ ## What it does
6
+
7
+ The bundle replaces the dormant `llm-pi-ai` composition row so these catalogue routes become active:
8
+
9
+ | Route | Credential reference | Initial acceptance model for resolved `pi-ai@0.82.1` |
10
+ | --- | --- | --- |
11
+ | `opencode` | `OPENCODE_API_KEY` | `nemotron-3-ultra-free` (free tier; paid `deepseek-v4-flash` blocked by the acceptance workspace's balance) |
12
+ | `opencode-go` | `OPENCODE_API_KEY` | `deepseek-v4-flash`, `glm-5.2` |
13
+ | `zai` | `ZAI_API_KEY` | `glm-5.2` |
14
+
15
+ The table is release evidence tied to the resolved `pi-ai` version, not a package-owned catalogue. Model availability, billing, quota, and provider policy remain service-owned runtime facts.
16
+
17
+ The bundle declares only `id` + credential references. Endpoints, protocols, model catalogues, and authentication logic stay owned by `pi-ai`; the bundle never duplicates `baseURL`, `api`, `models`, `headers`, context windows, output limits, reasoning formats, or pricing. It does not change the Harness default provider or model. Both OpenCode routes share one `OPENCODE_API_KEY` reference without copying the secret. Triss's own `ZHIPU_API_KEY` is deliberately not aliased; if you want the same underlying credential in both products, store it under each product's expected reference.
18
+
19
+ ## Prerequisites
20
+
21
+ - Node `^22.19.0 || >=24.0.0` (verified against the DeepSeek Harness engine range)
22
+ - `pnpm` installed and on `PATH` (the `dsh plugin` command forwards to `pnpm`)
23
+ - pnpm 9 treats the Harness profile directory (which carries its own
24
+ `pnpm-workspace.yaml` with `packages: [.]`) as a workspace root, so
25
+ `dsh plugin add` needs the `-w` flag (the form the lifecycle CI job
26
+ verifies) or `NPM_CONFIG_IGNORE_WORKSPACE_ROOT_CHECK=true` in the
27
+ environment. Verified against the compatibility tuple dsh `0.1.0-rc.6` ×
28
+ pnpm `9.0.0`; revisit when either pin moves.
29
+ - A Harness profile that already includes `@deepseek-ai/dsh-base` (this bundle does not own the runner or UI layer)
30
+
31
+ Tested with: `@deepseek-ai/dsh` at commit `47f9438`, `@deepseek-ai/dsh-llm-pi-ai@0.1.0-rc.5`, resolved `@earendil-works/pi-ai@0.82.1`. This package installs only into Harness profiles; global installation is unsupported because it would recreate an installation-anchor ambiguity.
32
+
33
+ ## Install
34
+
35
+ Prerequisites check, then install into a profile whose template boots a one-shot application. **Profile name selects the application template** in DeepSeek Harness (`dsh` 0.1.0-rc.6 defines exactly two named templates):
36
+
37
+ | Profile name | Template | What boots |
38
+ | --- | --- | --- |
39
+ | `headless` | `dsh-base` + `dsh-headless` | one-shot CLI application — exits when the run completes |
40
+ | `web` | `dsh-base` + `dsh-web-app` | interactive web application — waits for a browser client forever |
41
+ | any other name | `dsh-base` only | custom base-only profile — no app-specific bundles |
42
+
43
+ Only `headless` terminates by itself; `web` blocks waiting for a client, and a custom profile carries no application template at all. If you smoke-test this bundle from a terminal, create or use a `headless` profile:
44
+
45
+ ```bash
46
+ pnpm --version
47
+ node --version
48
+ dsh plugin --profile headless add -w triss-dsh-provider-bundle@0.35.0
49
+ dsh --profile headless --dump-config
50
+ ```
51
+
52
+ Removing the bundle never deletes your user settings; in a clean profile with no user `llm-pi-ai` settings and no later activating patch, removal restores the dormant base posture.
53
+
54
+ ## Compatibility evidence
55
+
56
+ Every acceptance records Node, pnpm, `@deepseek-ai/dsh`, `@deepseek-ai/dsh-llm-pi-ai`, resolved `pi-ai` version + lockfile integrity, and this package's version + tarball integrity. Compatibility is never claimed from the Harness version alone.
57
+
58
+ Tested tuple (packed-tarball fixture, `dsh plugin` full cycle — add, remove, reinstall):
59
+
60
+ | Fact | Value |
61
+ | --- | --- |
62
+ | Node | `v22.23.1` (satisfies `^22.19.0`) |
63
+ | pnpm | `9.0.0` (lockfileVersion `9.0`) |
64
+ | `@deepseek-ai/dsh` | `0.1.0-rc.6` |
65
+ | Profile template | `dsh-headless@0.1.0-rc.6` (bundles: `dsh-base` + `dsh-headless`) |
66
+ | This package | `0.35.0` |
67
+
68
+ Artifact integrity (tarball sha256/sha512) for each release is recorded in the
69
+ root repository `CHANGELOG.md` release entry — it cannot be embedded here,
70
+ because this README ships inside the tarball it would describe.
71
+
72
+ The `llm-pi-ai` adapter and its `pi-ai` dependency are supplied by the profile's `dsh-base` bundle, not by this package (the companion declares no dependencies).
73
+
74
+ ## License
75
+
76
+ MIT — see [LICENSE](./LICENSE).
@@ -0,0 +1,9 @@
1
+ - id: llm-pi-ai
2
+ config:
3
+ providers:
4
+ opencode:
5
+ apiKeyEnv: OPENCODE_API_KEY
6
+ opencode-go:
7
+ apiKeyEnv: OPENCODE_API_KEY
8
+ zai:
9
+ apiKeyEnv: ZAI_API_KEY
package/package.json ADDED
@@ -0,0 +1,37 @@
1
+ {
2
+ "name": "triss-dsh-provider-bundle",
3
+ "version": "0.35.0",
4
+ "description": "Configuration-only DeepSeek Harness (dsh) provider bundle activating the pi-ai opencode, opencode-go, and zai catalogue routes.",
5
+ "type": "module",
6
+ "files": [
7
+ "cordis.patch.yml",
8
+ "README.md",
9
+ "LICENSE"
10
+ ],
11
+ "keywords": [
12
+ "deepseek",
13
+ "deepseek-harness",
14
+ "dsh",
15
+ "pi-ai",
16
+ "opencode",
17
+ "zai",
18
+ "glm",
19
+ "provider-bundle",
20
+ "plugin"
21
+ ],
22
+ "author": "ayleen",
23
+ "license": "MIT",
24
+ "repository": {
25
+ "type": "git",
26
+ "url": "git+https://github.com/ayleen/triss-coworker.git",
27
+ "directory": "packages/dsh-provider-bundle"
28
+ },
29
+ "engines": {
30
+ "node": "^22.19.0 || >=24.0.0"
31
+ },
32
+ "dsh": {
33
+ "bundle": {
34
+ "patch": "./cordis.patch.yml"
35
+ }
36
+ }
37
+ }