@twinsearth/w2m-dsh-plugin 1.1.14 → 1.1.16

package/.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "The w2m fleet plugins: one account, many machines, any of Windows, macOS or Linux.",
-    "version": "1.1.14"
+    "version": "1.1.16"
   },
   "plugins": [
     {
       "name": "w2m-fleet",
       "source": "./",
       "description": "Read fleet state and dispatch commands across the machines registered to one account. Read-only MCP surface: the five exposed tools cannot change anything.",
-      "version": "1.1.14",
+      "version": "1.1.16",
       "author": {
         "name": "TwinsEarth"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "w2m-fleet",
   "description": "Drive the same project on online Windows, macOS and Linux machines from one account: read fleet state, dispatch commands and read results. The MCP surface is deliberately read-only.",
-  "version": "1.1.14",
+  "version": "1.1.16",
   "author": {
     "name": "TwinsEarth"
   },

package/CHANGELOG.md

@@ -2,6 +2,106 @@
 
 All notable changes to this project are documented here.
 
+## [1.1.16] — 2026-10-18
+
+**A machine waiting to be admitted now appears where you already answer questions -- and the README leads with how to
+install it.**
+
+### Admission in `w2m_approvals`
+
+`w2m_approvals` merges `GET /v1/fleet/admission/pending` into its list as `kind:'fleet_admission'` rows, so a machine
+asking to join shows up beside the permission requests already there. Settling an `adm-` id goes to the **relay's**
+decide endpoint, not the local permission index: admission is not an authority escalation, and pushing it through
+`approvalRequestFor` -- whose shape requires a needs-approval verdict and a capability -- would record a lie in the
+audit trail. The list is shared; the stores are not.
+
+The countdown is derived from the **relay's clock** (`rabbit_time`), never this machine's: three machines in this fleet
+disagree by tens of seconds, and a local countdown would fire the automatic approval early on a fast machine. The relay
+still owns the decision and still refuses to auto-approve with no member online.
+
+### Two defects the tests caught
+
+- the merged request omitted `rabbitUrl` and the device token, so it threw into the surrounding catch and the rows were
+  **silently missing** -- a probe showed the fetch was never called at all (`calls: []`);
+- the refusal code was read from `json.code`, but protocol errors arrive at `json.error.code`, so `reason_code` was always
+  null and a late `ALREADY_DECIDED` decision looked like a success path.
+
+Five assertions now cover that seam: rows and their fields, relay-clock countdown, an unreachable relay still showing the
+local queue, `adm-` routing reaching the relay, and a late decision reported rather than thrown.
+
+### README rewritten around installation
+
+Five routes, easiest first: DSH plugin (zero configuration), npm/MCP for any client, Claude Code marketplace, Codex, and
+the verified release tarball. Then quick start, the 11 tools registered, the `W2M_*` environment a dispatched command
+receives, the fleet model, the security posture, and an explicit **verified / not verified** table that names the approval
+popup, the four-machine `W2M_INDEX` run, the unimplemented chat channel and the macOS P2P downgrade instead of implying
+they work.
+
+Two claim checks rejected the first draft and were right: a `SHA256SUMS` release-download URL does not name a
+`<name>-<version>.tgz` asset, and "eleven tools" had to be the measured number.
+
+### Not in this release
+
+The approval **popup** (a dedicated 10-second countdown control) is not implemented -- the rules are enforced by the
+relay and this tool lists and settles the requests. The fleet chat channel remains designed (FLEET-CHAT-DESIGN.md) and
+not built. No four-machine `W2M_INDEX` run yet.
+
+### Verified
+
+Gate GREEN (final pass, 15 of 15). 2458 tests in 102 files, 2444 pass, 0 fail, 14 skip. tools 120, tool-cards 8,
+claims 47.
+
+## [1.1.15] — 2026-10-17
+
+**A machine that cannot join the old way now proves its account, asks to join, and waits for an answer -- and the
+executed command finally learns which machine and which slice it is.**
+
+### The fallback path is connected end to end
+
+v1.1.14 shipped the server half. This release connects the client:
+
+* \`pairNow\` classifies its failure and, for **only** the three degradable reasons (invalid pairing code, unreachable
+  relay, timeout), calls the new chain: challenge -> sign with the account key -> submit proof -> poll until a terminal
+  state. Anything else still needs a human and still does not change mechanisms;
+* **a rejection is final.** The chain stops on \`rejected\`; re-asking would turn a decision into a notification queue;
+* **an unfinished wait is reported, never hung on**: \`STILL_PENDING\` after the poll budget, \`expired\` when the relay
+  says so;
+* the seed for the account key is the **fleet key, never the account code** -- the account code is written to the log,
+  and deriving a signing key from a value anyone can read would hand out the account's identity;
+* the machine id comes from the agent object in scope, **not** from device.json: this machine never paired, which is the
+  entire situation.
+
+### Polling without a device token
+
+The asking machine has no device token -- that is why it is asking. The request response therefore carries a
+\`poll_token\`, and \`GET /v1/fleet/admission/{id}?poll_token=\` is reachable **ahead of** the device-token gate. A wrong
+token returns 404 rather than revealing whether the request exists.
+
+### The command learns where it is (P1)
+
+\`runArgv\` accepts an environment, and every executed command receives \`W2M_INDEX\`, \`W2M_INDEX_TOTAL\`,
+\`W2M_STAGE_INDEX\`, \`W2M_TASK_ID\`, \`W2M_MODE\`, \`W2M_MACHINE_ID\`, \`W2M_MACHINE_NAME\`. Values come from the OFFER,
+never from argv, so one machine cannot reshape a fleet-wide split. The variables are merged over \`process.env\` rather
+than replacing it -- PATH must survive, or no interpreter is found. \`W2M_STAGE_INDEX\` is deliberately separate from
+\`W2M_INDEX\`: for a split over four machines each runs one stage (0) but they are machines 0..3.
+
+This makes the operator's acceptance shape possible: \`process.exit(Number(process.env.W2M_INDEX)+1)\` yields 1/2/3/4
+across four machines. The single-machine half is tested here; the four-machine run needs the fleet and is **not yet
+verified**.
+
+### NOT shipped, stated plainly
+
+* **The approval UI** (10s popup with countdown plus a standing dialog) is not written. The server enforces the rules it
+  must: no automatic approval with zero members online, and a rejection beats the ten seconds;
+* **no end-to-end run**: new install -> popup -> admitted has not been executed, so \`agent.runtime.machineId\` being
+  non-empty on a real machine is **UNVERIFIED** -- if it is empty the fallback logs and does not fire;
+* the fleet chat / broadcast channel is designed (FLEET-CHAT-DESIGN.md) and not implemented.
+
+### Verified
+
+Full gate GREEN (final pass, 15 of 15). Suites touched: tools 115, account-join 6, account-identity 6, join-challenge 8,
+join-degradation 3, admission 16, admission-routes 3, relay 163, broadcast 19.
+
 ## [1.1.14] — 2026-10-17
 
 **A new machine joins by itself, and a machine that cannot join the old way can now prove its account and ask.**