@brutalsystems/muster 3.1.1 → 3.1.2

package/CANONICAL_ID.md

@@ -288,7 +288,7 @@ sessions; the send was a reply, so `reply_misrouted` caught it, but a new
 message would have gone through.
 
 This is not an exotic collision. It happens whenever a short name and a longer
-one built on it coexist — `muster` / `muster-b1`, `ferry` / `ferry-9b`.
+one built on it coexist — `muster` / `muster-b1`, `atlas` / `atlas-9b`.
 
 **It is kept because it cannot be fixed from the listing alone.** The hazard is
 indistinguishable from the behaviour directly above it in this document: `auth`

package/CONTRACT_PROVENANCE.md

@@ -513,7 +513,7 @@ The entire delta across both files is three hunks:
 - `CANONICAL_ID.md`: the normative version line, `1.9.2` → `2.0.0`.
 - `CANONICAL_ID.md`: the new paragraph described above.
 - the fixture: `tincan_version`, and one `rawName` in the prefix-collision
-  case, `cxx-be` → `billing-api`.
+  case, renamed to `billing-api`.
 
 `naming.ts` does not appear and no expected value moved. The renamed peer is
 **input**, not an expected output, and that case's expected `canonicalId`
@@ -528,6 +528,19 @@ fixture moved `publish.yml`, `RELEASING.md` and `docs/verification.md` on
 their own. Only the two frozen hashes in `test/naming.test.ts` are hand-written,
 and those are the third site behaving as documented.
 
+## Local text edit — 2026-10-17
+
+One example pair in `CANONICAL_ID.md`'s prefix-collision paragraph used a
+project name from a real machine; it now reads `atlas` / `atlas-9b`. The
+example illustrates the hazard and is not normative, so no rule, case or
+expected value changed. The fixture is untouched.
+
+| File | SHA-256 |
+| --- | --- |
+| `CANONICAL_ID.md` | `516d55ba07d191a29c68b74ea1181bc79149ab53b6c821cc9fe6dab14a78b58a` |
+
+A future re-sync takes upstream's text for that line.
+
 ## What the vendored copy covers, and what it deliberately does not
 
 The copies pin **the address format Muster generates** — slugify, suffix,

package/dist/config.js

@@ -13,7 +13,7 @@ import { RequesterConfigError } from "./requester-policy.js";
  * What a remote requester is permitted here.
  *
  * `level` defaults to `normal`: an enrolled remote caller gets a launch like
- * the operator's own, as a local one does (Mike, 2026-10-14). Naming `read` or
+ * the operator's own, as a local one does. Naming `read` or
  * `work` is how a profile caps it. `min_enforcement` follows the level it is
  * written beside — `none` for a normal profile, which muster does not enforce,
  * and `kernel` for a capped one — unless the profile names it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brutalsystems/muster",
-  "version": "3.1.1",
+  "version": "3.1.2",
   "description": "Launch instructed, reachable local agent sessions",
   "type": "module",
   "engines": {
@@ -14,6 +14,7 @@
     "test": "vitest run",
     "typecheck": "tsc -p tsconfig.check.json",
     "check": "npm run typecheck && npm test && node scripts/check-tarball.mjs",
+    "check:public": "scripts/check-public.sh --tree",
     "test:contract": "MUSTER_CONTRACT=1 vitest run test/contract.test.ts",
     "postinstall": "node scripts/prepare-pty.mjs",
     "pretest": "npm run build",