@twinsearth/w2m-dsh-plugin 0.37.0 → 0.38.0

package/CHANGELOG.md

@@ -4,6 +4,47 @@ 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.38.0] — 2026-10-15
+
+**A seven-phase council run on MacMini — real-machine evidence for the tool that had never touched one.**
+
+0.37.0's `w2m_council` was the only substantial addition in this span that had **never run anywhere but this
+laptop.** It now has a measurement, and the exit code came from the machine:
+
+```
+OK phases=7 outcome=ship dissent=1 reproduced=true      exit 0
+```
+
+Driven through `node -e` on MacMini against its own checkout at 0.37.0: the council was convened, roles
+assigned, two arguments recorded, two weighted votes cast, the outcome fixed, the decision sealed, and the
+sealed decision **read back after the council stopped being advanceable** — with its dissent, its reason, and a
+`recount` that reproduced the outcome from the stored ballots. **Every one of those was asserted before the
+process was allowed to exit `0`**, so this is not a "did it load" smoke test.
+
+### The same run answered a question that had only been a hypothesis for four rounds
+
+**v4.10.0's council works on MacMini because it reaches for nothing that machine lacks.** `council.mjs` imports
+`node:crypto` and `./authority.mjs`, and neither needs `node_modules`. The eight suites that failed there in
+0.32.0 therefore failed on **what their fixtures reach for**, not on the modules under test — **a measurement
+now, where four earlier releases recorded a guess as a guess.**
+
+It also sharpens the shape of that failure: a suite whose *subject* has no dependencies still fails if the
+*suite* imports one, and **from an exit code alone the two are indistinguishable.**
+
+### The sixth time I exceeded the ceiling
+
+The update dispatch — download a release tarball and extract it — **expired**. Measured again, and the number
+has not moved: the agent's lease survives roughly **50 seconds** (`heartbeatIntervalMs 10s × missedHeartbeats 2
++ leaseGraceMs 30s`), and an expired lease carries **no exit code at all**, so the work was lost rather than
+reported as failed.
+
+**What matters is what happened next:** rather than retrying the download, a **three-line probe** established
+that the extraction had in fact completed — **the partial run had succeeded and only the report was lost.** A
+retry would have spent another dispatch redoing finished work, and could have raced the `tar` it had left
+half-written.
+
+**No new tests.** What changed is a measurement, and a hypothesis that stopped being one.
+
 ## [0.37.0] — 2026-10-15
 
 **`council.mjs` is wired. v4.10.0's committee governance is reachable, and its dissent arrives with its decision.**

package/docs/1.0.0-ACCEPTANCE.md

@@ -68,16 +68,24 @@ declared its own `export const AUTHORITY_MAX = 100` instead of importing the bou
 **Two copies of a limit that nothing can keep in step, failing silently** — raise the real maximum and this
 module keeps refusing `101` while naming the wrong number as authoritative. It now imports it.
 
-### `v4.10.0`'s council is built and not routed — found here, not claimed before
+### `v4.10.0`'s council was BUILT AND NOT ROUTED — **fixed in 0.37.0**
 
 `reachability-classify` reported `src/agent/council.mjs` as a closed loop, and reading it to check that
 confirmed the finding: **275 lines implementing committee governance, imported by nothing but its own suite.**
 `v4.10.0` is marked *shipped in 0.11.0* in `ROADMAP.md`, and **0.30.0 verified its three falsifying tests are
 asserted by name** — which they are. **What was never checked is whether anything routes a question to it.**
 
-**This is the same defect as `field-authority` and `approval-gate`, in a third module**, and it is the one the
-reachability work was built to find. It is recorded here as **BUILT, NOT ROUTED** rather than described as
-delivered, and routing it needs a tool surface and a session — not a line of code.
+**This was the same defect as `field-authority` and `approval-gate`, in a third module** — the one the
+reachability work was built to find.
+
+**`w2m_council` now routes it.** The state lives in `createCouncilSessions` because a council walks **seven
+phases across many calls** and one held inside a single invocation **could never finish**. Every read of a
+decision returns the **dissent with its reasons** and a **`recount`**, so v4.10.0's third falsifying test —
+*"a decision with recorded dissent is retrievable with the dissent"* — holds **after the council that produced
+it is gone**, which is a property of the session rather than of the decision. Both are tested.
+
+**A tie is still refused, not broken**, and the tool does not paper over it: a split council is the one case
+where the council exists to escalate to a person.
 
 ---
 

package/package.json

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

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