@3dsource/angular-unreal-module 0.0.146-dev.7 → 0.0.146-dev.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3dsource/angular-unreal-module",
-  "version": "0.0.146-dev.7",
+  "version": "0.0.146-dev.8",
   "description": "Unreal module for connect with unreal engine stream",
   "keywords": [
     "3dsource",

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

@@ -1291,25 +1291,26 @@ declare class StreamStatusTelemetryService2 {
     /**
      * Emit the region / signaling / webrtc phases for an ADOPTED connection.
      *
-     * The prefetch script established the connection in parallel with page load,
-     * so its raw timeline (prefetch_start … ready) mostly predates this session —
-     * showing it verbatim would look identical to a non-prefetched connect. What
-     * matters is measured from the moment Angular reached the connect call
-     * (session start, == `lastMilestonePerf` here): the REAL wait until adoption,
-     * and how much the prefetch SAVED by finishing the handshake during page load.
-     *
-     * So the three phases fill exactly the `[session start → adopted]` window
-     * (split across signaling / webrtc by the prefetch's own sub-step ratio; the
-     * region was served from cache → ~0), and the savings figures ride in params:
-     *  - `prefetchConnectMs` — full handshake the prefetch measured (the cost a
-     *    cold, non-prefetched connect would pay here).
-     *  - `prefetchSavedMs` — how much of it completed before Angular was ready.
-     *  - `adoptionWaitMs` — the actual wait Angular experienced (= window).
-     *  - `adoptionOverheadMs` — gap between prefetch-ready and adoption.
+     * The prefetch script established the connection in PARALLEL with page load,
+     * so the phases are positioned at their real (anchor-relative) spans — shifted
+     * LEFT to overlap the HTML-loading / route-idle rows — rather than sequentially
+     * after them. That's the whole point of the prefetch: the handshake already
+     * happened while the page was loading. Each phase ships:
+     *  - `duration` — the real sub-step time the prefetch spent.
+     *  - `spanStartMs` — anchor-relative start, so the viewer left-shifts the bar.
+     *  - `adoptionAtMs` — where Angular took over (the next phase, Unreal
+     *    communication, resumes here on the sequential timeline).
+     *  - savings params: `prefetchConnectMs` (full handshake), `prefetchSavedMs`
+     *    (done before Angular was ready), `adoptionWaitMs` (real connect→adopted
+     *    wait), `adoptionOverheadMs` (prefetch-ready → adopted gap).
      */
     private emitAdoptedConnection;
-    /** Emit one adopted phase with an explicit (prefetch-derived) duration and
-     *  advance `lastMilestonePerf` synthetically so the next phase chains right. */
+    /**
+     * Emit one adopted phase positioned at its real `spanStartMs` (left-shifted
+     * to overlap page load) with its real prefetch `duration`. `prefetched`,
+     * `spanStartMs` and `adoptionAtMs` ride as top-level wire fields the viewer
+     * uses to lay the bar out; the rest become display params.
+     */
     private emitAdoptedPhase;
     /** Streamer identity params for the adopted signaling phase — mirrors the
      *  `ssinfo-received` closer's shape (client / instanceName / …ssData). */