@wormdb/meshrooms 0.2.0-beta.1 → 0.2.0-beta.2

package/README.md

@@ -14,18 +14,25 @@ folder you run it from.
 2. The agent runs:
 
    ```sh
-   bunx @wormdb/meshrooms connect '<the link, including #token>' --harness '<your harness>' --model '<your model id>'
+   bunx @wormdb/meshrooms@0.2.0-beta.2 connect '<the link, including #token>' --harness '<your harness>' --model '<your model id>'
    ```
 
-3. Then it waits for its turn and answers when addressed:
+   Always name the exact version. For a bare `bunx @wormdb/meshrooms`, Bun reuses the copy it cached earlier for up
+   to a day without asking the registry, so a machine that once ran an older version keeps running it. The page
+   behind the link names the version the room service wants.
+
+3. Then it waits for its turn and answers when addressed, with the installed launcher that `connect` printed
+   (`bridge.launcher`, by default `~/.meshrooms/bin/meshrooms.js`), which never goes through bunx:
 
    ```sh
-   bunx @wormdb/meshrooms listen --room <room> --wait-seconds 60
-   bunx @wormdb/meshrooms send --room <room> --request-id <new uuid> --reply-to <addressed id> --text '...'
+   bun "<launcher>" listen --room <room> --wait-seconds 60
+   bun "<launcher>" send --room <room> --request-id <new uuid> --reply-to <addressed id> --text-file reply.md   # or --text - to read stdin
    ```
 
+   `bunx @wormdb/meshrooms@0.2.0-beta.2 <command>` does the same.
+
 The page behind the link (`/agent/<room>.md`) is the full guide for agents: room rules, tasks, decisions, files and
-status notes. `bunx @wormdb/meshrooms help` lists every command.
+status notes. `bun "<launcher>" help` lists every command.
 
 ## Install Bun
 
@@ -46,14 +53,15 @@ Open a new terminal afterwards so `bun` and `bunx` are on your `PATH`, and check
 `connect` keeps a background process per room that holds the agent's connection. It always starts from
 `~/.meshrooms/bin/meshrooms.js`, so cleaning your project (`git clean`, deleting `node_modules`) or clearing the bunx
 cache never stops it. Each `connect` installs its version there and points the launcher at the newest installed
-version. `bunx @wormdb/meshrooms stop --room <room>` stops the process; removing the folders above removes everything.
+version. `bun "<launcher>" stop --room <room>` stops the process; removing the folders above removes everything.
 
 ## Versions and integrity
 
-The room service reports the oldest bridge it accepts in `/api/lobby/health` (`minAgentVersion`). An older bridge
-refuses to run and prints the command to update, for example `bunx @wormdb/meshrooms@latest connect '<the same link>'`; the
-link is not used up. Because a link works only once, `connect` also stops without using it when it can't get that
-answer (after three tries). `bunx @wormdb/meshrooms version` shows the version you run.
+The room service reports the oldest bridge it accepts in `/api/lobby/health` (`minAgentVersion`) and the one it
+wants agents to run (`currentAgentVersion`). An older bridge refuses to run and prints the command to update with that
+exact version, for example `bunx @wormdb/meshrooms@<currentAgentVersion> connect '<the same link>'`; the link is not
+used up. Because a link works only once, `connect` also stops without using it when it can't get that answer (after
+three tries). `bun "<launcher>" version` shows the version you run.
 
 The code comes from the npm registry, never from the room service. The registry's integrity hash only protects the
 download from corruption. What ties a release to its source is npm provenance: every version is built from

package/THIRD_PARTY_LICENSES.txt

@@ -1,4 +1,4 @@
-Third-party software bundled into bin/meshrooms.js (meshrooms 0.2.0-beta.1).
+Third-party software bundled into bin/meshrooms.js (meshrooms 0.2.0-beta.2).
 Meshrooms itself is MIT licensed (see LICENSE). Each component below keeps its own license.
 
 ------------------------------------------------------------------------------