dsh-plugin-toolkit 0.13.2 → 0.13.4

package/CHANGELOG.md

@@ -1,3 +1,22 @@
+## 0.13.4
+
+- **`docs/why-it-exists.md`**: the five failures that shaped these checks, each
+  with the exact error text, the root cause, the check that catches it now, and
+  how to reproduce it. Linked from both READMEs.
+- **A release for the GitHub Action** (`v1.0.0`), so the action can be published
+  to the Marketplace.
+
+## 0.13.3
+
+- **`verify` no longer fails a correct plugin.** The check that calls a client
+  module's `apply()` before its services exist handed it `{}`, so
+  `ctx.inject(...)` — the cordis API every plugin uses — threw
+  `ctx.inject is not a function` and the plugin was reported as broken. The
+  probe now models a real context: `inject`, `on`, `effect`, `logger`, `get`,
+  `set` and `provide` exist; only the services are absent.
+- Found by this repository's own example plugin, whose CI went red on the
+  previous release. That is the whole point of the example.
+
 ## 0.13.2
 
 - **A table of the four ways a plugin installs and still does nothing** — red

package/README.md

@@ -73,6 +73,8 @@ Releasing one plugin fifteen times taught me three things the ecosystem's toolin
 2. **The market index is a second release, done by hand.** Each version needs an entry carrying `publishTimestamp` from the registry and `engines.dsh` from the manifest. Forget the range and the index validator rejects the PR with `Engines mismatch` — after the tag is already public.
 3. **Reading a manifest is not the same as checking it.** A plugin can have a valid `package.json` and still be uninstallable: `files` that omit the entry the manifest points at, a bundle patch that does not exist, a README that never states the host range it declares.
 
+The five failures behind these checks — a red dot with no panel, a row the host drops, an app that disables every plugin after one unguarded `apply()`, a tab nothing can open, and a checker that was wrong — are written up with their exact error text and how to reproduce each one: [Five plugins that installed and did nothing](https://github.com/WJDdidi-1/dsh-plugin-toolkit/blob/main/docs/why-it-exists.md).
+
 ### Four ways a plugin installs and still does nothing
 
 Each of these shipped in a real version of this toolkit before the check below existed. A manifest check passes on all four.

package/README.zh.md

@@ -44,6 +44,8 @@ npx dsh-plugin-toolkit@latest release --pr --merge              # 打 tag、等
 
 前三条是静态的：`doctor` 和 `verify` 不用开应用就能抓到。第四条是 UI 契约，必须把面板挂起来、检查注册出去的参数——那是 [`testkit`](#不用浏览器测面板) 的活。
 
+这五个事故——红点没有面板、宿主丢掉一行、一行没加保护的 `apply()` 让应用禁用全部插件、注册了却没人能打开的标签、以及一个判错了的检查器——都写了原始报错和复现步骤：[插件装上了，却什么都不做](https://github.com/WJDdidi-1/dsh-plugin-toolkit/blob/main/docs/why-it-exists.md)。
+
 ## 安装要求
 
 - Node.js 18 或更新（CI 在 18/20/22 × ubuntu/macos/windows 上跑）。

package/lib/verify.mjs

@@ -39,8 +39,37 @@ function packTarball(dir, destination) {
  * What cordis hands a plugin that declares no `inject`: every undeclared
  * property read throws. A plain `{}` hides the bug this is looking for.
  */
+// cordis itself is present on every context — `ctx.inject`, `ctx.on`,
+// `ctx.effect` and the logger. What can be absent is the *services*.
+function cordisApi() {
+  const noop = () => () => {};
+  const base = {
+    inject: (list, callback) => {
+      // A declared service may still be absent when apply runs: record nothing,
+      // call nothing. That is exactly what the host does before a service mounts.
+      void list;
+      void callback;
+      return () => {};
+    },
+    on: noop,
+    effect: noop,
+    logger: () => {},
+    get: () => undefined,
+    set: () => {},
+    provide: noop,
+    reflect: { get: () => undefined, set: () => {}, provide: noop },
+  };
+  return base;
+}
+
+/** A context whose services have not mounted yet; reading one gives undefined. */
+function absentContext() {
+  return cordisApi();
+}
+
+/** A context that also enforces cordis's rule: an undeclared read throws. */
 function undeclaredContext() {
-  const base = { inject: undefined };
+  const base = cordisApi();
   return new Proxy(base, {
     get(target, key) {
       if (key in target) return target[key];
@@ -212,7 +241,7 @@ export async function verify({ dir, mount = true }) {
         faceProblems.push('the client module declares no inject list, so the loader calls apply() before its services exist');
       }
       try {
-        face.apply({});
+        face.apply(absentContext());
       } catch (error) {
         faceProblems.push(`apply() throws when the services are absent, which fails the web boot: ${error.message}`);
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-toolkit",
-  "version": "0.13.2",
+  "version": "0.13.4",
   "description": "Preflight, release and test DeepSeek Harness plugins: check a folder or any GitHub repository, wait for npm to actually serve the version, and keep the market index honest.",
   "type": "module",
   "bin": {