@camstack/addon-pipeline 1.2.102 → 1.2.103

package/dist/stream-broker/index.js

@@ -25455,15 +25455,32 @@ var TimelineSession = class {
 	/**
 	* The profile this session will actually play, given the one asked for.
 	*
-	* A segment covering `epochMs` wins outright. Failing that the answer is the
-	* first profile the camera DEMONSTRABLY records — a gap carrying a
-	* `nearestEdgeMs` means "footage exists on this tier, just not here", which is
-	* exactly what the feeder's snap-to-nearest needs. Falling back to `requested`
-	* when nothing has footage is only correct as a last resort: the session
-	* default is `mid`, and no camera on this cluster records `mid`, so returning
-	* it for a tap into a gap left the feeder with nothing to snap to and turned a
-	* recoverable crack into `seek-no-footage` — the operator sees "no recording"
-	* on a camera that recorded seconds either side.
+	* **The requested tier wins whenever it has footage AT ALL** — a segment
+	* covering `epochMs`, or a gap carrying a `nearestEdgeMs`, which means
+	* "footage exists on this tier, just not here" and is exactly what the
+	* feeder's snap-to-nearest needs. Only a tier that records NOTHING is
+	* abandoned, and then the answer is the first tier that demonstrably does.
+	* Falling back to `requested` when nothing has footage anywhere is the last
+	* resort: the session default is `mid`, and no camera on this cluster records
+	* `mid`, so returning it for a tap into a gap left the feeder with nothing to
+	* snap to and turned a recoverable crack into `seek-no-footage` — the
+	* operator sees "no recording" on a camera that recorded seconds either side.
+	*
+	* The requested tier is checked to EXHAUSTION before any other is consulted,
+	* and that ordering is load-bearing twice over:
+	*
+	* 1. The scrub is pinned to `low` by the client, and every D163 pre-cache
+	*    behaviour is gated on `deps.profile === 'low'` by exact string equality
+	*    — the 90 s/30 s entry warm, the whole-segment read, and the 24 MB
+	*    fragment budget (2 MB for anything else). `profileSearchOrder` puts
+	*    `high` BEFORE `low`, so a momentary `low` gap used to hand the drag a
+	*    `high` feeder and silently turn all three off. The client cannot repair
+	*    that: it re-sends `setProfile` only when its own `lastSentProfile`
+	*    mirror disagrees, and the mirror never learns the server moved.
+	* 2. `seek` and `scrubCommit` route through `playAt`, so every finger-release
+	*    pays this loop. locate is a cap RPC (1-8 s on cold footage); walking the
+	*    ladder to re-confirm a pin the caller already holds is latency the
+	*    operator feels as a slow commit.
 	*/
 	async resolveProfile(requested, epochMs) {
 		const locate = this.deps.locate;
@@ -25481,7 +25498,10 @@ var TimelineSession = class {
 				continue;
 			}
 			if (loc.kind === "segment") return profile;
-			if (withFootage === null && loc.nearestEdgeMs !== null) withFootage = profile;
+			if (withFootage === null && loc.nearestEdgeMs !== null) {
+				if (profile === requested) return profile;
+				withFootage = profile;
+			}
 		}
 		return withFootage ?? requested;
 	}

package/dist/stream-broker/index.mjs

@@ -25450,15 +25450,32 @@ var TimelineSession = class {
 	/**
 	* The profile this session will actually play, given the one asked for.
 	*
-	* A segment covering `epochMs` wins outright. Failing that the answer is the
-	* first profile the camera DEMONSTRABLY records — a gap carrying a
-	* `nearestEdgeMs` means "footage exists on this tier, just not here", which is
-	* exactly what the feeder's snap-to-nearest needs. Falling back to `requested`
-	* when nothing has footage is only correct as a last resort: the session
-	* default is `mid`, and no camera on this cluster records `mid`, so returning
-	* it for a tap into a gap left the feeder with nothing to snap to and turned a
-	* recoverable crack into `seek-no-footage` — the operator sees "no recording"
-	* on a camera that recorded seconds either side.
+	* **The requested tier wins whenever it has footage AT ALL** — a segment
+	* covering `epochMs`, or a gap carrying a `nearestEdgeMs`, which means
+	* "footage exists on this tier, just not here" and is exactly what the
+	* feeder's snap-to-nearest needs. Only a tier that records NOTHING is
+	* abandoned, and then the answer is the first tier that demonstrably does.
+	* Falling back to `requested` when nothing has footage anywhere is the last
+	* resort: the session default is `mid`, and no camera on this cluster records
+	* `mid`, so returning it for a tap into a gap left the feeder with nothing to
+	* snap to and turned a recoverable crack into `seek-no-footage` — the
+	* operator sees "no recording" on a camera that recorded seconds either side.
+	*
+	* The requested tier is checked to EXHAUSTION before any other is consulted,
+	* and that ordering is load-bearing twice over:
+	*
+	* 1. The scrub is pinned to `low` by the client, and every D163 pre-cache
+	*    behaviour is gated on `deps.profile === 'low'` by exact string equality
+	*    — the 90 s/30 s entry warm, the whole-segment read, and the 24 MB
+	*    fragment budget (2 MB for anything else). `profileSearchOrder` puts
+	*    `high` BEFORE `low`, so a momentary `low` gap used to hand the drag a
+	*    `high` feeder and silently turn all three off. The client cannot repair
+	*    that: it re-sends `setProfile` only when its own `lastSentProfile`
+	*    mirror disagrees, and the mirror never learns the server moved.
+	* 2. `seek` and `scrubCommit` route through `playAt`, so every finger-release
+	*    pays this loop. locate is a cap RPC (1-8 s on cold footage); walking the
+	*    ladder to re-confirm a pin the caller already holds is latency the
+	*    operator feels as a slow commit.
 	*/
 	async resolveProfile(requested, epochMs) {
 		const locate = this.deps.locate;
@@ -25476,7 +25493,10 @@ var TimelineSession = class {
 				continue;
 			}
 			if (loc.kind === "segment") return profile;
-			if (withFootage === null && loc.nearestEdgeMs !== null) withFootage = profile;
+			if (withFootage === null && loc.nearestEdgeMs !== null) {
+				if (profile === requested) return profile;
+				withFootage = profile;
+			}
 		}
 		return withFootage ?? requested;
 	}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/addon-pipeline",
-  "version": "1.2.102",
+  "version": "1.2.103",
   "description": "Pipeline bundle — runner, detection, motion, audio + stream broker. Multi-entry npm package shipping pipeline addons under a single bundle.",
   "keywords": [
     "camstack",