@robota-sdk/agent-transport-webrtc 3.0.0-beta.83 → 3.0.0-beta.85

package/CHANGELOG.md

@@ -1,5 +1,53 @@
 # @robota-sdk/agent-transport-webrtc
 
+## 3.0.0-beta.85
+
+### Patch Changes
+
+- Updated dependencies [9a01e78]
+  - @robota-sdk/agent-transport@3.0.0-beta.85
+  - @robota-sdk/agent-interface-session@3.0.0-beta.85
+  - @robota-sdk/agent-interface-session-mobility@3.0.0-beta.85
+  - @robota-sdk/agent-interface-transport@3.0.0-beta.85
+  - @robota-sdk/agent-remote-pairing@3.0.0-beta.85
+
+## 3.0.0-beta.84
+
+### Patch Changes
+
+- 9c6a8db: The wire protocol gained several request/reply pairs so a GUI never has to scrape command output for
+  data it can read directly.
+
+  `get-settings`/`update-settings` read and write the Settings screen; a patch applies through the same
+  function its matching slash command uses, so the two paths cannot drift. `list-models` returns the
+  configured models grouped by provider profile, with the current profile and model. `get-agent-definitions`
+  returns the agent switcher's roster and current selection. `project-status`, `project-diff` and
+  `project-memory` back the Project panel's git status, one file's diff, and project memory; a host
+  without this capability answers `protocol_error` instead of hanging. `rename-session` and
+  `delete-session` rename or remove a stored session from the list, current or not, each with its own
+  success/failure reply.
+
+  The `messages` frame gained an optional `display` field — the same history projected into display
+  segments (text runs and finished tool calls, diffs included) — and the connection's own `driverId`, so
+  a reload, reconnect or resume shows tool rows and tells a co-driver's turns from its own. The `error`
+  frame gained optional `code`, `provider`, `retryAfterSeconds` and `model` fields so a renderer can say
+  what kind of failure happened (`auth`, `rate_limit`, `model_unavailable`, `network`, `provider`) instead
+  of showing only raw text; a session error this classification does not recognize is unchanged.
+
+  `TCommandSurfaceLocality` names whether a `'remote'`-sourced command is provably on this machine. The
+  WebRTC/device-mesh transport now forwards `'remote'` for it (it proves no locality, the same rule
+  already applied to pairing), and both the WS and WebRTC transports forward it into the Settings
+  read/write path, so a command that refuses a remote surface (installing a plugin) refuses identically
+  regardless of which transport carried it.
+
+- Updated dependencies [e8d70ac]
+- Updated dependencies [9c6a8db]
+  - @robota-sdk/agent-interface-session@3.0.0-beta.84
+  - @robota-sdk/agent-transport@3.0.0-beta.84
+  - @robota-sdk/agent-interface-session-mobility@3.0.0-beta.84
+  - @robota-sdk/agent-interface-transport@3.0.0-beta.84
+  - @robota-sdk/agent-remote-pairing@3.0.0-beta.84
+
 ## 3.0.0-beta.83
 
 ### Minor Changes

package/README.md

@@ -13,7 +13,7 @@ uses. The package also contains the building blocks for connecting one user's de
 npm install @robota-sdk/agent-transport-webrtc @robota-sdk/agent-transport node-datachannel
 ```
 
-Requires Node.js 22 or later. The WebRTC implementation, `node-datachannel` (libdatachannel, a
+Requires Node.js 22.12 or later. The WebRTC implementation, `node-datachannel` (libdatachannel, a
 native module), is an optional peer dependency loaded lazily. If it is not installed or has no
 prebuilt binary for the platform, `start()` fails with an explicit `WebRTC transport unavailable`
 error; there is no fallback implementation. `@robota-sdk/agent-transport` provides the
@@ -87,7 +87,9 @@ requires attaching again.
 - Relay: `TurnServer` and `MeshTurnRelay`, a TURN relay one of the user's devices can run for its
   paired devices.
 - Enrollment: `dialEnrollment` and `listenForEnrollment` open the channel used to enroll a new
-  device.
+  device; they fail with `EnrollmentLinkError`.
+- Admission frames: `localProofFrame` (the local-peer nonce) and `handoffGrantFrame` /
+  `judgeHandoffGrant` (a signed cross-device hand-off grant, verified by a host-supplied verifier).
 
 ## Related packages
 
@@ -97,8 +99,12 @@ requires attaching again.
   DTLS-fingerprint channel binding the pairing gate uses.
 - [`@robota-sdk/agent-transport-ws`](../agent-transport-ws/README.md): the WebSocket transport for
   the same protocol.
+- [`@robota-sdk/agent-transport-webrtc-web`](../agent-transport-webrtc-web/README.md): the browser
+  peer that answers this transport's offer (internal).
 
-See [docs/SPEC.md](docs/SPEC.md) for the package contract.
+For how the Robota CLI uses this for remote control and connecting your own devices, see the
+[devices and remote access guide](../../content/guide/devices-and-remote.md). See
+[docs/SPEC.md](docs/SPEC.md) for the package contract.
 
 ## License