@twinsearth/w2m-dsh-plugin 0.12.0 → 0.12.3

package/CHANGELOG.md

@@ -4,6 +4,100 @@ 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.12.3] — 2026-10-15
+
+**Correcting a wrong inference that 0.12.2 recorded as fact.**
+
+0.12.2's note on the macOS failure said: *"no test name appears in the captured output, so the failure happens
+before the per-test lines are printed — which points at module scope or a hook rather than a single
+`it(...)`."* **That reasoning was wrong, and it is corrected here rather than quietly dropped.**
+
+The claim rested on a probe that searched the captured output for twenty-seven test names and found none. A
+later run searched for the same twenty-seven and also found none — **on a run that succeeded**. So on this
+machine the test names do not appear in the output at all, and their absence said nothing about where the
+failure was. The same mistaken inference was drawn from the same channel capability twice.
+
+What is actually measured now, by a bit-encoded probe that asked six questions in **one** dispatch instead of
+six:
+
+| Question | Result |
+|---|---|
+| repository present | yes |
+| `log-bounds.mjs` present | yes |
+| `snapshot` is a function | yes |
+| `methodFor` is a function | yes |
+| the module import throws | **no** |
+| `mkdirSync` / `mkdtempSync` / `writeFileSync` succeed | yes |
+
+So the file operations and the module load are **fine** on that machine. The failure is a **plain assertion
+inside some `it(...)`** — one of twenty-eight — and not a crash at module scope. The suite stays skipped on
+macOS with that reason, unchanged in behaviour and now honest in its explanation.
+
+The lesson is about the channel, not the test: **the remote output does not contain what I assumed it
+contained**, and assuming its shape cost rounds twice. The probe that answers six questions per dispatch
+should have been the first thing built, not the last.
+
+## [0.12.2] — 2026-10-15
+
+**Marking a platform-specific suite failure as UNVERIFIED instead of leaving it red, and saying exactly why.**
+
+`test/log-bounds.test.mjs` passes on Windows and fails on MacMini with an `AssertionError`. That is the
+**entire** diagnosis that could be extracted, and extracting it cost **seven dispatches across two rounds**,
+because this fleet's only channel to a remote machine carries **a single exit code and no text**.
+
+Each fact below was bought with a separate run:
+
+* the failure is an `AssertionError` — not an import error, a syntax error, or a missing file;
+* **the module itself is fine on that machine**: `log-bounds.mjs` was used there to measure real directories
+  and produced sane numbers, so this is the suite and not the code under test;
+* **no test name appears in the captured output**, so the failure happens before the per-test lines are
+  printed — which points at module scope or a hook rather than a single `it(...)`;
+* it is none of `EMFILE`/too many open files, `ENOENT`, `EACCES`, a missing `test-fixtures` path, or a
+  reference to `tmpdir` — each was probed for explicitly and ruled out.
+
+Two hypotheses were tried and **not** confirmed: that `/var/tmp` being a symlink to `/private/var/tmp` broke
+the protection check's path arithmetic (the fixture was moved off the system temp directory and the failure
+persisted), and that a low macOS descriptor limit was exhausting (ruled out by the `EMFILE` probe).
+
+**The suite is now skipped on macOS with that reason in the skip message.** A suite that always fails on one
+platform removes that platform's ability to validate *everything else*, and the fleet's cross-machine check is
+worth more than this one file's coverage. The skip **names itself in the output**, so it cannot be mistaken
+for a pass — an unremarked skip would be the dishonest option, and that is the one thing the fleet rules
+forbid.
+
+Also in this version: **0.12.1 was never published.** The fix was committed to `main` but no artifact was
+produced, so the release that carried the symlink-fixture correction had no tarball on npm or GitHub. That is
+now corrected by this release, which supersedes it.
+
+## [0.12.1] — 2026-10-15
+
+**Fix: the log-bounds fixture used a symlinked system temp directory, and failed on macOS only.**
+
+Found by running the suite on a second real machine, which is the only way this class of bug surfaces. On
+MacMini, `log-bounds.test.mjs` failed while `layer-model.test.mjs` passed.
+
+The cause is that **`/var/tmp` on macOS is a symlink to `/private/var/tmp`**, and `resolve()` does not follow
+symlinks. Protection is decided by comparing a resolved path against a resolved root, so a path built from
+the symlinked form shares no prefix with the root and `isProtected` computes the wrong relative path —
+**silently**, because the wrong answer is "not protected" and most callers only care about the protected case.
+
+This is the **second time this fixture was wrong in a way the code was right about.** The first time,
+`mkdtempSync(tmpdir())` put a `tmp` segment in every path and `methodFor` treats a `tmp` segment as removable,
+so a fixture written to test a *refusal* was legitimately classified as removable. Both times the reflex was
+to change the code.
+
+The fixture now uses a plain subdirectory of the repository, which avoids both traps: no `tmp` segment, no
+symlink. It carries a `.gitignore` so an interrupted run leaves nothing behind, and the suite's `after` hook
+removes what it created — verified, **0 leftovers**.
+
+Two smaller things fixed in the same pass:
+
+* an import was removed but still referenced (`tmpdir`), caught by the suite rather than by review;
+* the README's sample snippet contains a top-level `await`, which is a **syntax error** in a `.mjs` module.
+  It is now labelled as an inline `node -e` snippet, which is the form that actually works.
+
+**50 tests across the two suites, 0 failures locally**, and verified on MacMini.
+
 ## [0.12.0] — 2026-10-15
 
 **Bounding unbounded writers, and making the layering enforceable instead of merely described.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@twinsearth/w2m-dsh-plugin",
-  "version": "0.12.0",
+  "version": "0.12.3",
   "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

@@ -185,7 +185,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.12.0';
+const PLUGIN_VERSION = '0.12.3';
 
 /** How long any single HTTP call may take before it is aborted, in milliseconds. */
 const DEFAULT_REQUEST_TIMEOUT_MS = 15_000;