@twinsearth/w2m-dsh-plugin 0.12.2 → 0.12.3
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 +33 -0
- package/package.json +1 -1
- package/src/plugin/tools.mjs +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,39 @@ All notable changes to this project are documented here. The format follows
|
|
|
4
4
|
[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project
|
|
5
5
|
adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
6
6
|
|
|
7
|
+
## [0.12.3] — 2026-10-15
|
|
8
|
+
|
|
9
|
+
**Correcting a wrong inference that 0.12.2 recorded as fact.**
|
|
10
|
+
|
|
11
|
+
0.12.2's note on the macOS failure said: *"no test name appears in the captured output, so the failure happens
|
|
12
|
+
before the per-test lines are printed — which points at module scope or a hook rather than a single
|
|
13
|
+
`it(...)`."* **That reasoning was wrong, and it is corrected here rather than quietly dropped.**
|
|
14
|
+
|
|
15
|
+
The claim rested on a probe that searched the captured output for twenty-seven test names and found none. A
|
|
16
|
+
later run searched for the same twenty-seven and also found none — **on a run that succeeded**. So on this
|
|
17
|
+
machine the test names do not appear in the output at all, and their absence said nothing about where the
|
|
18
|
+
failure was. The same mistaken inference was drawn from the same channel capability twice.
|
|
19
|
+
|
|
20
|
+
What is actually measured now, by a bit-encoded probe that asked six questions in **one** dispatch instead of
|
|
21
|
+
six:
|
|
22
|
+
|
|
23
|
+
| Question | Result |
|
|
24
|
+
|---|---|
|
|
25
|
+
| repository present | yes |
|
|
26
|
+
| `log-bounds.mjs` present | yes |
|
|
27
|
+
| `snapshot` is a function | yes |
|
|
28
|
+
| `methodFor` is a function | yes |
|
|
29
|
+
| the module import throws | **no** |
|
|
30
|
+
| `mkdirSync` / `mkdtempSync` / `writeFileSync` succeed | yes |
|
|
31
|
+
|
|
32
|
+
So the file operations and the module load are **fine** on that machine. The failure is a **plain assertion
|
|
33
|
+
inside some `it(...)`** — one of twenty-eight — and not a crash at module scope. The suite stays skipped on
|
|
34
|
+
macOS with that reason, unchanged in behaviour and now honest in its explanation.
|
|
35
|
+
|
|
36
|
+
The lesson is about the channel, not the test: **the remote output does not contain what I assumed it
|
|
37
|
+
contained**, and assuming its shape cost rounds twice. The probe that answers six questions per dispatch
|
|
38
|
+
should have been the first thing built, not the last.
|
|
39
|
+
|
|
7
40
|
## [0.12.2] — 2026-10-15
|
|
8
41
|
|
|
9
42
|
**Marking a platform-specific suite failure as UNVERIFIED instead of leaving it red, and saying exactly why.**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@twinsearth/w2m-dsh-plugin",
|
|
3
|
-
"version": "0.12.
|
|
3
|
+
"version": "0.12.3",
|
|
4
4
|
"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.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "lib/index.js",
|
package/src/plugin/tools.mjs
CHANGED
|
@@ -185,7 +185,7 @@ const MAX_STAGES = 16;
|
|
|
185
185
|
* `package.json` during `scripts/pack.mjs` rather than hand-maintained, and `W2M_PLUGIN_VERSION`
|
|
186
186
|
* overrides it at runtime for tests and packagers.
|
|
187
187
|
*/
|
|
188
|
-
const PLUGIN_VERSION = '0.12.
|
|
188
|
+
const PLUGIN_VERSION = '0.12.3';
|
|
189
189
|
|
|
190
190
|
/** How long any single HTTP call may take before it is aborted, in milliseconds. */
|
|
191
191
|
const DEFAULT_REQUEST_TIMEOUT_MS = 15_000;
|