@urun-sh/core 0.3.5 → 0.3.7

package/CHANGELOG.md

@@ -2,6 +2,28 @@
 
 ## Unreleased
 
+- **BREAKING: `WtMicUplinkHandle` and `WtCamUplinkHandle` require
+  `deliveredDatagrams(): number`; `WtUplinkSink` requires `delivered(): number`.**
+  A consumer that supplies only `setSource()` (and `requestKeyframe()` for the
+  camera) to `TransportSession.wtMicUplinkSeam` / `wtCamUplinkSeam` no longer
+  type-checks. Implementors report the datagrams QUIC has ACCEPTED from that
+  lane. There is deliberately no optional-with-fallback form: a lane that
+  cannot answer "did anything actually leave?" is the bug being removed
+  (urun-sh/urun-infra#2053 — `isProducingMedia` claimed a live microphone from
+  handle presence plus `MediaStreamTrack.readyState`, so the SDK reported a
+  healthy mic through an entire session in which nothing was transmitted).
+  Migration: return a per-lane counter incremented when that lane's datagram
+  write resolves. `WtUplinkSink` is internal — it is not exposed by the package
+  entrypoints — so only the two handle types affect external implementors.
+
+- **Media liveness is level-triggered, and a sender sequence RESTART resyncs
+  instead of wedging the leg forever** (urun-sh/urun-infra#2053). Both media
+  lanes kept a monotonic high-water mark with no RFC 3550 §A.1 restart rule, so
+  a sender that restarted its sequence space was discarded for the life of the
+  session — silently, and on video before the keyframe bit was even read. The
+  decode-stall watchdog is no longer one-shot, uplink datagram write rejections
+  are no longer swallowed, and publication requires delivery evidence.
+
 - **WT uplink lanes now share ONE datagram writer (`getWriter` lock).**
   `WritableStream.getWriter()` LOCKS the stream — the WHATWG contract is one
   writer at a time. `WebTransportSession.start()` built its uplink sink by