dsh-plugin-toolkit 0.13.3 → 0.13.5

package/CHANGELOG.md

@@ -1,3 +1,20 @@
+## 0.13.5
+
+- **A wildcard export no longer fails the pack check.** `exports` can name a
+  pattern (`"./locale/*.json"`), while `npm pack` lists the files it shipped
+  (`locale/en.json`). Comparing them as strings reported a correctly packed
+  plugin as broken; the check now matches patterns by prefix and suffix.
+- Found by running `verify` against the neighbour project's plugin, which ships
+  exactly that export.
+
+## 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

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

@@ -79,6 +79,22 @@ function undeclaredContext() {
   });
 }
 
+/**
+ * A declared path can be a pattern: `exports["./locale/*.json"]` names a folder
+ * of files, and `npm pack` lists the files it actually shipped. Exact set
+ * membership would report a correctly packed plugin as broken — which it did,
+ * on this repository's own neighbour.
+ */
+function shipsPath(shipped, target) {
+  if (target.includes('*') === false) return shipped.has(target);
+  const [head, tail] = target.split('*');
+  const suffix = tail ?? '';
+  for (const file of shipped) {
+    if (file.startsWith(head) === true && file.endsWith(suffix) === true) return true;
+  }
+  return false;
+}
+
 export async function verify({ dir, mount = true }) {
   const failures = [];
   const report = doctor(dir);
@@ -101,7 +117,7 @@ export async function verify({ dir, mount = true }) {
   // installed plugin is missing its own code.
   const shipped = new Set(packed.files);
   for (const target of declaredPaths(report.manifest)) {
-    if (shipped.has(target) === false) {
+    if (shipsPath(shipped, target) === false) {
       failures.push({
         check: 'pack',
         message: `the tarball does not contain ${target}, so the installed plugin would be missing it`,
@@ -113,7 +129,7 @@ export async function verify({ dir, mount = true }) {
   const repoEntry = resolveEntry(dir, report.manifest);
   if (repoEntry !== null) {
     const relative = path.relative(dir, repoEntry).split(path.sep).join('/');
-    if (shipped.has(relative) === false) {
+    if (shipsPath(shipped, relative) === false) {
       failures.push({
         check: 'pack',
         message: `the tarball does not contain ${relative}, so the installed plugin has no panel`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-plugin-toolkit",
-  "version": "0.13.3",
+  "version": "0.13.5",
   "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": {