dsh-cabinet-mode 0.0.0-stage → 0.1.5

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