@urun-sh/core 0.2.11 → 0.2.14

package/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.2.12
+
+- DELETE the dead legacy data-stream subscribe handshake. `TransportSession.subscribeStream()` / `unsubscribeStream()` and the `{t:"stream.subscribe"|"stream.unsubscribe"}` signaling control frames are removed: the session-server's vanilla-Yjs cutover made that doc-lane opt-in deliberately inert (`crdt/legacy-stub.ts handleStreamControlText` no-op, `StreamSubscriptions.shouldDeliver() === false`), so the frames did nothing. Named-DATA delivery is the contract §5 server-push path — the server pushes `consumeData` for every named stream to every leg, the client attaches a mediasoup `DataConsumer` (native `recvTransport.consumeData`) and acks `dataConsumerReady` on channel OPEN. Public API unchanged: `session.stream(name).messages()` / `emit()` behave identically; which handlers receive the flowing data is now a purely local concern.
+- NOTE FOR CONSUMERS PINNED BY THE REGISTRY: npmjs currently serves `@urun-sh/core` latest as **0.2.8** — the 0.2.9/0.2.10/0.2.11 publishes never landed in the public packument (same registry-side failure as the 0.2.0 line, see the 0.2.1 entry). 0.2.8 predates #146, so its `dataConsumerReady` ack fires at channel CREATION and the server's first-envelope gate releases before the SCTP channel opens — the FIRST envelope of every named stream (one-shot results, first captions) is dropped. This release is the first resolvable version past that gap; after publish, VERIFY the registry actually serves 0.2.12.
+
 ## 0.2.1
 
 - Republish of the 0.2.0 line. `npm publish` reported success for `@urun-sh/core@0.2.0` / `@urun-sh/react@0.2.0` but the version never landed in the public npm packument (a registry-side persistence failure — npm/npm#20851), leaving 0.2.0 unresolvable via `npm install` and occupied (so not re-publishable). Bumped to 0.2.1 to ship a clean, resolvable release. No source changes vs 0.2.0.