@nexus-code/remote-protocol 0.1.0 → 0.2.0

package/README.md

@@ -7,7 +7,7 @@ There are two layers:
 - **Relay frames** (`relay.ts`): what a device and its account's room on the relay send each other. The relay reads these: who a message is for, its sequence number, and the account key version it was sealed with. It cannot read the message itself.
 - **Sealed messages** (`sealed.ts`, `rpc.ts`, `view.ts`): what a sealed frame carries between two devices of the account.
   - A `hello` that says which protocol version and capabilities a device serves.
-  - JSON-RPC 2.0 requests, answers and notifications: list and watch sessions, read and drive chats, read terminals.
+  - JSON-RPC 2.0 requests, answers and notifications: list and watch sessions and their changes, read and drive chats, read, watch and drive terminals, wait on either, and read a workspace's files and git. What a device serves is per capability (`CAPABILITIES`); a hello's `schema` names the package version it speaks (`SCHEMA_VERSION`).
   - The chat view: the conversation as the serving device's app already built it, trimmed for drawing.
 
 Beside them:
@@ -26,3 +26,7 @@ declarations in `dist`, and `zod` 3.25 or later as a peer. The desktop app
 imports `src` directly; `npm run build` (run by `prepublishOnly`) makes
 `dist`. Relative imports in `src` end in `.js`, as Node's ES modules need
 them.
+
+A version is published by GitHub Actions (`.github/workflows/publish-remote-protocol.yml`)
+when a tag `remote-protocol-vX.Y.Z` naming the version in `package.json` is pushed:
+trusted publishing, with no token or one-time password, and with provenance.