@robota-sdk/agent-transport-webrtc 3.0.0-beta.86 → 3.0.0-beta.88

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # @robota-sdk/agent-transport-webrtc
 
+## 3.0.0-beta.88
+
+### Patch Changes
+
+- @robota-sdk/agent-interface-session@3.0.0-beta.88
+- @robota-sdk/agent-interface-session-mobility@3.0.0-beta.88
+- @robota-sdk/agent-interface-transport@3.0.0-beta.88
+- @robota-sdk/agent-remote-pairing@3.0.0-beta.88
+- @robota-sdk/agent-transport@3.0.0-beta.88
+
+## 3.0.0-beta.87
+
+### Patch Changes
+
+- Release the migrated Robota product with its public SDK namespace, robota command, compatible SDK exports, internal product configuration, and verified CLI startup and delivery corrections.
+- Updated dependencies
+- Updated dependencies [7d9cc66]
+  - @robota-sdk/agent-interface-session@3.0.0-beta.87
+  - @robota-sdk/agent-interface-session-mobility@3.0.0-beta.87
+  - @robota-sdk/agent-interface-transport@3.0.0-beta.87
+  - @robota-sdk/agent-remote-pairing@3.0.0-beta.87
+  - @robota-sdk/agent-transport@3.0.0-beta.87
+
 ## 3.0.0-beta.86
 
 ### Patch Changes
@@ -124,7 +147,7 @@
   - The device lists read from public records are bounded per paired device, each device's newest
     before any device's next, and the chunks of one list carry a shared version, so a read that finds
     chunks of two versions yields no list. Records written before this change are not read as lists.
-  - CLI processes that share `~/.robota/devices/address-cache.json` apply each change to the file as it
+  - CLI processes that share `$PRODUCT_USER_STATE_DIR/devices/address-cache.json` apply each change to the file as it
     is on disk, so one process no longer overwrites what another learned.
 
 - 4241fc5: Device mesh follow-ups.
@@ -210,7 +233,7 @@
     pairwise secret (`derivePairRendezvous(...).relayInbox()`).
   - `agent-cli` — a device holding the signing key reissues its roster and revocation list before they
     expire while an interactive session runs. The host can open this device's mesh endpoint from the
-    identity under `~/.robota/devices`, saving newer lists a peer hands over; no command starts it yet.
+    identity under `$PRODUCT_USER_STATE_DIR/devices`, saving newer lists a peer hands over; no command starts it yet.
   - `agent-command` — `/devices add|join` still reports that enrolment is not available yet.
 
 - e15e22b: The Node WebRTC transport runs on `node-datachannel` (libdatachannel, DTLS by OpenSSL). The DTLS stack
@@ -234,7 +257,7 @@
     The tool reaches only files inside the workspace whose path does not look like it holds secrets
     (`.env*`, `~/.ssh`, keys and credentials), and it does not exist in a turn a peer's message started.
   - The receiving operator approves every file. A received file is kept as an inert copy (mode 0600)
-    under `~/.robota/peer-files/<sender>/`. It is never run and never placed in the model's context.
+    under `$PRODUCT_USER_STATE_DIR/peer-files/<sender>/`. It is never run and never placed in the model's context.
     The conversation is told only its name, size and sha256. A name that leaves that directory is
     refused, a symbolic link is never written through, and nothing is overwritten.
   - Transfers travel on a channel of their own (a separate connection on this host, a separate data
@@ -326,7 +349,7 @@
     rate. Discovery yields candidates only: admission is still the device handshake, and an address is
     remembered only after an admission it carried.
   - `agent-cli` — the device mesh endpoint can look on the local network (`lan` option), remembering
-    the addresses that worked in an owner-only `~/.robota/devices/address-cache.json`; no command starts
+    the addresses that worked in an owner-only `$PRODUCT_USER_STATE_DIR/devices/address-cache.json`; no command starts
     it yet.
 
 ### Patch Changes

package/README.md

@@ -1,6 +1,6 @@
 # @robota-sdk/agent-transport-webrtc
 
-WebRTC peer-to-peer transport for the Robota SDK (Node.js). `WebRtcTransport` carries a Robota
+WebRTC peer-to-peer transport for the Robota SDK (Node.js). `WebRtcTransport` carries an agent runtime
 session over an `RTCDataChannel`, so a remote client can drive a live session directly, peer to
 peer, without session content passing through a server. It reuses the transport-neutral session
 bridge and wire protocol from `@robota-sdk/agent-transport`, the same ones the WebSocket transport
@@ -102,10 +102,10 @@ requires attaching again.
 - [`@robota-sdk/agent-transport-webrtc-web`](../agent-transport-webrtc-web/README.md): the browser
   peer that answers this transport's offer (internal).
 
-For how the Robota CLI uses this for remote control and connecting your own devices, see the
+For how the agent runtime 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
 
-Robota is dual-licensed under the [GNU AGPL-3.0](../../LICENSE) or a [commercial license](../../COMMERCIAL.md). See [LICENSING.md](../../LICENSING.md).
+This package is dual-licensed under the [GNU AGPL-3.0](../../LICENSE) or a [commercial license](../../COMMERCIAL.md). See [LICENSING.md](../../LICENSING.md).