@3dsource/angular-unreal-module 0.0.184 → 0.0.186

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3dsource/angular-unreal-module",
-  "version": "0.0.184",
+  "version": "0.0.186",
   "description": "Angular integration for Unreal Engine Pixel Streaming",
   "keywords": [
     "3dsource",

package/types/3dsource-angular-unreal-module.d.ts

@@ -941,13 +941,26 @@ type SignalingRetryKind = 'ws-retry' | 'connect' | 'orchestration' | 'region-cyc
  * rtt) over one aggregation window (5 s, ~20 samples at 250 ms).
  *
  * - `p50` — the typical tick; robust to outliers, primary dashboard signal.
- * - `p95` — the bad tail users actually perceive; preferred for SLOs.
+ * - `p95` — the bad tail where HIGH is bad (rtt, jitter, qp).
+ * - `p05` — the bad tail where HIGH is good (fps, bitrate). Consumers need a
+ *   robust low end, and `min` cannot serve: it is a single tick, so one
+ *   dropped frame defines the window. Sent for every metric so the shape
+ *   stays uniform; only fps and bitrate have a reason to read it.
+ *
+ * All three percentiles use linear interpolation between order statistics
+ * (type 7), matching the consumer's `percentile()` so the word means one
+ * thing across both repos.
  * - `min` — worst single tick (freeze detection).
  * - `max` — best single tick (did we ever reach the target?).
+ *
+ * Every field is a percentile of the SAME window, so a consumer may compare
+ * them to each other — but must never average them across windows to obtain
+ * a population percentile.
  */
 interface WindowAggregate {
     readonly p50: number;
     readonly p95: number;
+    readonly p05: number;
     readonly min: number;
     readonly max: number;
 }
@@ -1116,6 +1129,27 @@ interface SampleData extends TelemetryEventEnvelope {
     readonly jitter: WindowAggregate;
     readonly rtt: WindowAggregate;
     readonly packetsLost?: number;
+    /**
+     * Bytes the video stream delivered DURING this window — how far
+     * `inbound-rtp.bytesReceived` moved since the previous window closed, not a
+     * running total.
+     *
+     * What turns a bandwidth figure on the receiving end into a measurement.
+     * Volume needs the window's MEAN bitrate; {@link bitrate} carries
+     * p50/p95/min/max and no mean, so without this a consumer has to work the
+     * volume out from the median — which runs low on a stream that spikes at
+     * every keyframe.
+     *
+     * A delta rather than the cumulative counter on purpose: a cumulative value
+     * is only usable if the previous sample survived the trip, so one dropped
+     * POST would move bytes silently into the next window.
+     *
+     * Omitted when the counter is missing or went backwards (a renegotiation
+     * restarts it) — see `CounterWindow`. A consumer reads the gap as "estimate
+     * this window from the bitrate", which is the honest reading; it must never
+     * treat a missing value as zero bytes.
+     */
+    readonly bytes?: number;
     readonly viewPort: {
         readonly width?: number;
         readonly height?: number;