@hydranium/protocol 1.0.0-next.225 → 1.0.0-next.227

package/README.md

@@ -60,6 +60,7 @@ names, a worked example — is in
 @hydranium/protocol               # transfer documents, references, RPC machinery
 @hydranium/protocol/data          # DataServerProtocol / DataClientProtocol
 @hydranium/protocol/client        # the host-neutral client tier
+@hydranium/protocol/messages      # every message it raises, by code
 @hydranium/protocol/node          # process memory and heap-snapshot helpers
 @hydranium/protocol/testing       # test doubles, waiters, catalogue audit
 @hydranium/protocol/testing/node  # the Node-only doubles

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hydranium/protocol",
-  "version": "1.0.0-next.225",
+  "version": "1.0.0-next.227",
   "description": "Generic, language-agnostic types, constants, and pure utilities for the hydranium framework.",
   "keywords": [
     "hydranium",

package/src/rpc/README.md

@@ -43,8 +43,8 @@ data-server head ships with `'data-server/'` by default; adopters that
 combine the data-server with their own protocol head under one prefix pass
 their adopter namespace (e.g. `'myapp/'`) on both sides.
 
-Trailing-slash discipline is the adopter's responsibility — `'foo'` is a
-literal prefix, not interpreted as a namespace segment.
+A namespace ends in `/` or is empty: `bindRpcMethods` and `createRpcProxy`
+throw a `TypeError` for `'foo'`.
 
 ### Notification discrimination: `isNotification`