0.2.69 - Homepage loading improvements pass

server/internal/credits/README.md

@@ -79,10 +79,13 @@ viewers is enough only when both rolled into the next episode, which is unambigu
 they left.
 
 **Visual** scanning finds a sustained structural transition — dark, flat, textured with thin
-text, and staying that way for a minute. Darkness is *multiplied* rather than added into the
-frame score, which is the one modelling decision worth defending: under a weighted sum a
-night exterior reaches the credit-like floor on darkness and flatness alone, which is exactly
-how a final scene comes to be reported as a credits roll. A unit test pins that case.
+text, and staying that way for about half a minute. Darkness is *multiplied* rather than added
+into the frame score, which is the one modelling decision worth defending: under a weighted
+sum a night exterior reaches the credit-like floor on darkness and flatness alone, which is
+exactly how a final scene comes to be reported as a credits roll. The candidate frame itself
+must also be genuinely dark, and at least 65% of the remaining frames must stay credit-like;
+those two guards stop a dim final scene or a temporary title card becoming an early marker.
+Unit tests pin both cases.
 
 The two fail in unrelated ways, so agreement between them is worth far more than either
 alone — hence a probabilistic union rather than an average. Disagreement beyond 20 seconds
@@ -163,3 +166,6 @@ in which demand-driven narrowing is doing nothing, and the design would need rev
   on every playback.** Readings wobble by seconds; a ±12s difference is not news.
 - **The detector never learns why an episode was chosen.** That boundary is what stops it
   being tuned to agree with the predictor rather than with the media.
+- **An `ffmpeg` decoder crash gets one conservative retry.** The retry is single-threaded and
+  discards corrupt packets; ordinary network, authentication and timeout failures are not
+  retried by the sampler.