dsh-cabinet-mode 0.0.0-stage → 0.1.4

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/CHANGELOG.md ADDED
@@ -0,0 +1,229 @@
1
+ # Changelog
2
+
3
+ All notable changes to this project are documented in this file.
4
+
5
+ ## [0.1.4] - 2026-11-03
6
+
7
+ ### Added
8
+
9
+ - **npm publication through npm Trusted Publishing (OIDC).** Pushing a `v*` tag
10
+ now runs `.github/workflows/release.yml`, which verifies the tree, packs the
11
+ tarball, publishes `dsh-cabinet-mode` to `registry.npmjs.org` with
12
+ `npm publish --access public` authenticated by the workflow's OIDC identity
13
+ (`id-token: write`, no `NPM_TOKEN`), creates the GitHub Release, and refreshes
14
+ the plugin market index branch. The npm-side trusted publisher must be created
15
+ on npmjs.com first; the preconditions are documented in both READMEs. The first
16
+ version was bootstrapped with `npm stage publish` (the npm registry refuses a
17
+ trusted publisher for a package that does not exist yet), which left the public
18
+ prerelease placeholder `0.0.0-stage` on the registry. Prerelease versions are
19
+ published with `--tag next` so `latest` never points at a version the index
20
+ skips; the first bootstrap also needs that flag because npm rejects an untagged
21
+ prerelease.
22
+ - **Plugin market index (format 1).** `scripts/market-index.mjs` builds
23
+ `marketplace.json` from the npm registry: it lists every published version,
24
+ skips prereleases and deprecated versions, keeps `engines.dsh` optional (this
25
+ package still declares no DSH version gate, so entries carry no `engines`
26
+ member), writes integer-second `publishTimestamp` values, and sorts versions in
27
+ descending SemVer order. `--check` compares the registry with the published
28
+ index byte for byte. The script uses only Node built-ins; two test seams
29
+ (`MARKET_REGISTRY_MANIFEST`, and a local path / `file:` URL in
30
+ `MARKET_INDEX_URL`) allow offline fixture runs without changing the production
31
+ defaults.
32
+ - `scripts/publish-market-index.sh` publishes `marketplace.json`, `icon.svg` and a
33
+ README to the orphan `market-index` branch, force-pushing only when the content
34
+ changed (three attempts). It is the only publisher implementation (CI and
35
+ `npm run market:publish` both call it) and refuses to run on a working tree with
36
+ modified or staged tracked files; run it only in a disposable clone with no
37
+ uncommitted work (Windows uses Git Bash).
38
+ - `.github/workflows/market-index.yml`: manual and weekly refresh of the index
39
+ branch. `.github/workflows/ci.yml`: pull-request checks (repository
40
+ verification, script syntax, `npm pack --dry-run` and tarball content checks).
41
+ - **Install/update from the plugin market.** Both READMEs document the index URL
42
+ `https://raw.githubusercontent.com/luodaoyi/dsh-cabinet-mode/market-index/marketplace.json`,
43
+ adding it as an index source in the DSH plugin market, installing from it, and
44
+ the required DSH restart. The documented update path is the real one for
45
+ third-party plugins — uninstall the old version, install the new one, restart —
46
+ because the market has no in-place update.
47
+
48
+ ### Changed
49
+
50
+ - The release workflow no longer says "Nothing is published to npm": the GitHub
51
+ Release is now an additional artifact, not the only distribution channel.
52
+ - README install/upgrade examples point at the 0.1.4 GitHub Release assets, and
53
+ the npm-related "unverified" statements now describe the npm/index flow
54
+ accurately.
55
+ - `docs/cross-platform.md` records the npm Trusted Publishing path, the market
56
+ index generator, and the code-level update chain (no in-place update, SemVer-only
57
+ comparison, no periodic check, 10-minute index cache).
58
+ - `files` in `package.json` now lists `docs/cross-platform.md` and `docs/images`
59
+ explicitly instead of the whole `docs/` directory, so internal research and
60
+ verification material stays in git but out of the npm tarball.
61
+ - Removed the unused `@deepseek-ai/dsh-plugin-market-index` devDependency and the
62
+ Windows-only Node copy of the branch publisher: the repository stays
63
+ dependency-free and the publish pipeline needs no install step.
64
+
65
+ ### Unverified
66
+
67
+ - The release workflow, the npm publish and the index refresh have **not run
68
+ yet**: no version is on npm, the `market-index` branch does not exist, and a
69
+ real plugin-market install/update has not been performed. The UI labels and
70
+ click path of the plugin market are unverified. The
71
+ `dsh-cabinet-mode@<version>` install spec was confirmed locally by executing the
72
+ format-1 reader (`@deepseek-ai/dsh-plugin-market-index@0.2.1-rc.5`,
73
+ `marketInstallTarget`). The market update path documented in the READMEs (no
74
+ in-place update; uninstall → install → restart; SemVer-only comparison; no
75
+ periodic auto-check; 10-minute index cache) is a code-level finding recorded in
76
+ `docs/research/market-index-research.md` §5, not an end-to-end test.
77
+
78
+ ## [0.1.3] - 2026-10-31
79
+
80
+ ### Fixed
81
+
82
+ - **rc.5 install notes are now conditional and match observed behavior.** The
83
+ desktop-carrier `dsh` CLI runs `dsh plugin --profile desktop list/add ...`
84
+ (exit 0, verified on DSH 0.2.1-rc.5); the real gates are the profile
85
+ initialization prompt (fully quit DeepSeek Harness before installing/upgrading)
86
+ and the `--dump-config` rejection on desktop profiles. The previous blanket
87
+ "rc.5 rejects `dsh plugin`" wording was wrong.
88
+ - **The unverified list now reflects reality**: DSH 0.2.1-rc.5 real install and
89
+ upgrade were tested on Windows (2026-10-31); what remains untested is the
90
+ post-restart UI (mode picker / preset card / icon display), teammate behavior,
91
+ Linux/macOS, real `remove`, and other DSH versions.
92
+
93
+ ### Added
94
+
95
+ - Explicit **Upgrade** section: the same install command with the new version
96
+ URL, then fully quit and restart. Upgrades were performed and verified on
97
+ Windows: v0.1.0 → v0.1.1 via the plugin CLI on DSH 0.2.1-rc.3, then
98
+ v0.1.1 → v0.1.2 and v0.1.2 → v0.1.3 via the embedded-pnpm route on
99
+ DSH 0.2.1-rc.5.
100
+
101
+ ### Changed
102
+
103
+ - `scripts/verify.mjs` no longer hard-codes the package version; version sync is
104
+ enforced by the CHANGELOG-section check and the README release-URL checks,
105
+ both derived from `package.json`.
106
+
107
+ ## [0.1.2] - 2026-10-31
108
+
109
+ ### Added
110
+
111
+ - **Bundle icon**: the package now ships `icon.svg` (a Ming-dynasty
112
+ grand-secretary portrait provided by the project owner, embedded as a bitmap
113
+ inside the SVG) and declares it via `"icon": "./icon.svg"`, following the same
114
+ convention as the shipped `dsh-experimental-agent-team-profile` bundle.
115
+ - **README hero image** (`docs/images/cabinet-portrait.jpg`) and a team-layout
116
+ diagram (`docs/images/cabinet-team.svg`) in both READMEs, plus a Screenshots
117
+ section inviting real runtime captures.
118
+ - **DSH 0.2.1-rc.5 install note**: desktop builds at rc.5 reject
119
+ `dsh plugin --profile desktop ...`; the READMEs now document the plugin-page
120
+ route and the embedded-pnpm route (with `dsh.profile.bundles` kept).
121
+
122
+ ### Fixed
123
+
124
+ - `scripts/verify.mjs` now also asserts the icon file, the `icon` field and the
125
+ `files` entry, and the package version was bumped so the release URLs in the
126
+ READMEs stay in sync (`v0.1.2`).
127
+
128
+ ## [0.1.1] - 2026-10-29
129
+
130
+ ### Added
131
+
132
+ - **"DSH-side constraints" (中文:DSH 侧限制与说明) sections** in `README.md` and
133
+ `README.zh.md`, recording verified facts instead of implying the mode is
134
+ unrestricted: Agent Team member/task/message limits from the profile's
135
+ `@deepseek-ai/dsh-experimental-agent-team-profile` configuration
136
+ (`maxMembers: 8`, `maxTasks: 256`, `maxMessageBytes: 65536`,
137
+ `disposalTimeoutMs: 5000`; the deployment default for `maxMembers` is 16 and this
138
+ desktop profile sets 8), the Team-tool dependency on that profile bundle,
139
+ permission/sandbox ownership by DSH permission presets, the trusted-configuration
140
+ warning, and the no-OS-restriction / no-plugin-allowlist / no-npm-account facts.
141
+ - **No DSH version gate.** The package declares no `engines.dsh` and no DSH
142
+ `peerDependencies`; the README no longer pins a DSH version and explains how to
143
+ adapt the 22 plugin rows if a DSH version ships a different built-in Standard Mode
144
+ plugin set. 0.2.1-rc.3 is recorded as the **tested reference only**; no
145
+ multi-version testing has been performed.
146
+
147
+ ### Changed
148
+
149
+ - **F1 (documentation timeliness):** `README.md`, `README.zh.md` and
150
+ `docs/cross-platform.md` now record the Windows-tested GitHub Release asset URL
151
+ installation and the real `dsh plugin --profile desktop add` (2026-10-29,
152
+ `dsh plugin --profile desktop list` = 3 packages). Linux and macOS remain
153
+ code-level inferences and are still marked as not tested.
154
+ - **F3 (docs wording/paths):** local absolute paths in `docs/cross-platform.md` are
155
+ generalized to `<DSH_HOME>` / `<repo>` placeholders; README wording changed from
156
+ "ships no JavaScript" to "no plugin-runtime JavaScript (no `main`/`lib`); optional
157
+ Node.js fallback scripts only".
158
+ - Version bump to **0.1.1**; release URL and tarball filename examples in both
159
+ READMEs now point at `v0.1.1` / `dsh-cabinet-mode-0.1.1.tgz`.
160
+
161
+ ### Fixed
162
+
163
+ - **F2 (backup timestamp granularity):** `scripts/install.mjs` and
164
+ `scripts/uninstall.mjs` backup names now use second-granularity timestamps
165
+ (`YYYYMMDD-HHMMSS`) plus a short random suffix, so install → uninstall → install
166
+ within the same minute never overwrites an earlier backup. Size and SHA-256
167
+ verification are unchanged.
168
+ - `scripts/verify.mjs`: the DSH version check is informational only (no version
169
+ gate, never fails on a different DSH version); added assertions for the absence of
170
+ DSH version-gate fields, the DSH-side constraints sections, `<DSH_HOME>`
171
+ placeholder usage, and version consistency across `package.json`, READMEs and
172
+ `CHANGELOG.md`.
173
+
174
+ The preset itself is unchanged: the 22-row plugin list, the cross-platform
175
+ `!!js process.platform` guards for `tool-bash`/`tool-pwsh`, and the dual-identity
176
+ persona are byte-identical to 0.1.0.
177
+
178
+ ## [0.1.0] - 2026-10-29
179
+
180
+ First public release.
181
+
182
+ ### Added
183
+
184
+ - `cordis.patch.yml`: a pure declarative DSH bundle that inserts one
185
+ `@deepseek-ai/dsh-agent-preset` declaration for **Cabinet Mode** (`config.id: cabinet`,
186
+ display name `内阁模式`, `order: 5`).
187
+ - The preset's 22-row plugin list is copied verbatim from DeepSeek Harness 0.2.1-rc.3
188
+ `@deepseek-ai/dsh-web-app` shipped `presets/standard.patch.yml`, except for the
189
+ `persona` row, so the mode behaves exactly like the built-in Standard Mode apart
190
+ from its identity prompt.
191
+ - Dual-identity persona: the same persona prefix is shared by the Lead and every
192
+ teammate. Identity is decided only by the exact Team runtime-context phrases
193
+ `You are the Team Lead named "lead".`, `You are teammate "<name>".`, and
194
+ `Your Team Lead is named "lead".`; teammates must never claim to be the Lead.
195
+ Lead duties: read the request, break it down, assign work, adjudicate, summarize,
196
+ close the loop. Default posture is research-only; sources must never be fabricated.
197
+ - Cross-platform plugin rows: `tool-bash` is disabled on Windows via
198
+ `!!js process.platform === 'win32'` and `tool-pwsh` on other platforms via
199
+ `!!js process.platform !== 'win32'`, matching the shipped Standard Mode; Linux and
200
+ macOS therefore use bash automatically. No absolute paths, no shell-specific install
201
+ steps, no `lib/` build step.
202
+ - `README.md` (English) and `README.zh.md` (Chinese) with a first-screen copy-paste
203
+ install prompt for AI agents, a three-line manual install, a Windows/Linux/macOS
204
+ install matrix, rollback commands, and an explicit list of unverified items.
205
+ - Node.js fallback installer scripts (no third-party dependencies, dry-run by default):
206
+ `scripts/install.mjs`, `scripts/uninstall.mjs`, `scripts/verify.mjs`. `--apply` writes
207
+ the profile `cordis.patch.yml` with backup, SHA-256 verification, idempotency,
208
+ BEGIN/END markers, empty/`[]`/comments-only target handling, and post-write
209
+ structure checks with automatic restore on failure.
210
+ - `docs/cross-platform.md`: code-level cross-platform analysis of the bundle install
211
+ chain, preset platform guards, and the fallback patch path. Windows was tested;
212
+ Linux and macOS are code-level inferences and are marked as not tested.
213
+ - `.github/workflows/release.yml`: on a `v*` tag, packs the npm tarball, emits
214
+ `SHA256SUMS.txt`, and publishes both as GitHub Release assets with the built-in
215
+ `GITHUB_TOKEN`. Nothing is published to npm.
216
+
217
+ ### Known limitations
218
+
219
+ - Real installation and the post-restart mode picker were only exercised on
220
+ Windows with DSH 0.2.1-rc.3; Linux and macOS are code-level inferences.
221
+ - The mode is fixed for the lifetime of a session once the session has produced
222
+ output.
223
+ - A preset is not a sandbox: declarations are trusted configuration and can run
224
+ host code.
225
+ - Applying this bundle and also appending the same insert to a profile patch would
226
+ declare `config.id: cabinet` twice; the preset declaration then fails to load.
227
+ Use exactly one installation method.
228
+ - Teammate behavior under this persona (inheriting the same prefix and not claiming
229
+ to be the Lead) was not live-tested.
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 luodaoyi
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.