@twinsearth/w2m-dsh-plugin 0.4.6 → 0.4.8

package/CHANGELOG.md

@@ -4,6 +4,48 @@ All notable changes to this project are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.8] — 2026-10-09
+
+### Added
+
+* **The listing badge, with the URL it actually resolves to.** The plugin is listed on
+  dsh-plugin.org as `twinsearth/dsh-windows2macos` under Workflow & Automation, marked
+  **Verified** — it was auto-discovered through the `dsh-plugin` topic and reviewed by hand
+  before this release. The badge links to that page rather than to a guessed slug.
+
+### Notes
+
+* The listing's own snapshot was stale (it still showed v0.3.8 and an install command the hub
+  derived itself), so a submission issue was filed with the hub's template —
+  [dshplugin/dsh-plugin-hub#141](https://github.com/dshplugin/dsh-plugin-hub/issues/141) — which
+  is what triggers a re-scan. Nothing about being listed had to be requested: the topic is the
+  entry point, and this repository already carried it.
+* The package is on npm as `@twinsearth/w2m-dsh-plugin` (latest 0.4.7 at the time of this
+  release). With the package now existing, npm **trusted publishing** can be configured for this
+  repository and `release.yml` — after that every future release publishes itself with provenance,
+  and no token or one-time code is involved.
+
+## [0.4.7] — 2026-10-09
+
+### Fixed
+
+* **The package root exported nothing, and the ecosystem checks the root.** `lib/index.js` was
+  deliberately documentation-only — the profile mounts `@twinsearth/w2m-dsh-plugin/tools` because
+  `cordis.patch.yml` names that subpath — so `import('@twinsearth/w2m-dsh-plugin')` returned
+  `Object.keys() === []` and `typeof apply === 'undefined'`. A plugin that mounts perfectly and
+  looks like an empty package to every tool that inspects it is a listing risk with no upside: the
+  DSH plugin listing requirements ask for a package that "exports an `apply(ctx)` module", and a
+  missing root export is one of the most common reasons a submission is refused. The root now
+  re-exports `apply`, `inject` and the test helper from `./tools.js` — one implementation, two
+  entry points — and `test/tools.test.mjs` asserts it, so it cannot silently regress.
+
+### Notes
+
+* Nothing about the mounted plugin changed: the patch still names the subpath rather than relying on
+  the "root is the plugin" convention, which is what keeps the eight tools from being registered
+  twice.
+* `tools.test.mjs`: 83 pass, 0 fail.
+
 ## [0.4.6] — 2026-10-09
 
 ### Added

package/README.md

@@ -6,6 +6,7 @@ English | [中文](#中文说明)
 
 [![CI](https://github.com/TwinsEarth/dsh-windows2macos/actions/workflows/ci.yml/badge.svg)](https://github.com/TwinsEarth/dsh-windows2macos/actions/workflows/ci.yml)
 [![npm](https://img.shields.io/npm/v/@twinsearth/w2m-dsh-plugin?label=npm)](https://www.npmjs.com/package/@twinsearth/w2m-dsh-plugin)
+[![Listed on dsh-plugin.org](https://dsh-plugin.org/badges/listed.svg)](https://dsh-plugin.org/plugins/twinsearth/dsh-windows2macos)
 [![DSH plugin](https://img.shields.io/badge/DSH-plugin-4c6ef5)](#install)
 [![dependencies](https://img.shields.io/badge/runtime%20dependencies-0-brightgreen)](#design-notes)
 [![license](https://img.shields.io/badge/license-MIT-green)](LICENSE)

package/lib/index.js

@@ -1,13 +1,24 @@
 /**
- * Intentionally empty plugin entry point.
+ * Package root entry.
  *
- * The profile mounts this package's `tools` subpath -- named explicitly by
- * `cordis.patch.yml`'s insert entry -- so that reading the profile tells you
- * which module of the package becomes the plugin, instead of relying on a
- * "root export is the plugin" convention.
+ * TWO READERS, ONE EXPORT LIST
  *
- * This file exists only so the manifest never points at a path that does not
- * resolve. All real behaviour lives in `../src/plugin/tools.mjs`, re-exported
- * through `./tools.js`.
+ * `cordis.patch.yml` names the `tools` subpath explicitly, and that stays true: mounting this
+ * profile reads the patch, sees `@twinsearth/w2m-dsh-plugin/tools`, and loads `./tools.js`. Nothing
+ * about the mounted plugin changes because of this file.
+ *
+ * But the root entry is what everything else looks at. The DSH plugin listing requirements -- and
+ * the marketplace checklists that copy them -- ask for a package that "exports an `apply(ctx)`
+ * module", and a package that does not is one of the most common reasons a submission is refused.
+ * This file used to be documentation only, so importing the package root yielded **no exports at
+ * all** (`Object.keys() === []`): a plugin that works perfectly when mounted by its patch and looks
+ * like an empty package to every tool that inspects it. That is a bad trade for one re-export line.
+ *
+ * WHY NOT MOVE THE PLUGIN HERE
+ *
+ * Re-exporting is not relocating: `./tools.js` stays the single definition, so there is still
+ * exactly one implementation of the plugin surface to keep in sync. Mounting *both* this entry and
+ * the subpath would register the eight tools twice, which is why the patch keeps naming the subpath
+ * instead of falling back to the "the root is the plugin" convention.
  */
-export {};
+export { apply, inject, resetDefineToolCacheForTests } from './tools.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@twinsearth/w2m-dsh-plugin",
-  "version": "0.4.6",
+  "version": "0.4.8",
   "description": "DSH: Windows2MacOS — drive the same project on online Windows and macOS machines from one DeepSeek account, across networks and regions. P2P hole punching is the default path (relay + shared server as rendezvous, ledger and fallback), with a bundled STUN responder, Tailscale/public-VPS/tunnel shapes, Rabbit relay + per-machine Localside + eight DSH tools (replicate / split), nine aggregate verdicts and signed requests.",
   "type": "module",
   "main": "lib/index.js",

package/src/plugin/tools.mjs

@@ -110,7 +110,7 @@ const MAX_STAGES = 16;
  * `package.json` during `scripts/pack.mjs` rather than hand-maintained, and `W2M_PLUGIN_VERSION`
  * overrides it at runtime for tests and packagers.
  */
-const PLUGIN_VERSION = '0.4.6';
+const PLUGIN_VERSION = '0.4.8';
 
 /** How long any single HTTP call may take before it is aborted, in milliseconds. */
 const DEFAULT_REQUEST_TIMEOUT_MS = 15_000;