Files

T

gramps d8c1bdba24 feat(stream): RECONNECTING driven by the status poll — no invented countdown (TASK 32·2)

Creator challenge (2026-11-05): "I really don't think that's going to be a constant — it's going to
depend on so many variables, some that are dark to us." Correct, so the measured-grace constant and
the countdown are dropped from the spec. YouTube's cutoff is server-side and depends on ingest health,
prior stream quality, region and load; a pinned number would be a guess wearing a timer, and it would
be wrong exactly when the creator is staring at it.

What ships instead:

- **Amber RECONNECTING** in the top bar with measured facts only: elapsed seconds and the attempt
  number ("0:12 · attempt 2 of 4"). The seconds come from a stopwatch started at the drop.
- **The status poll speeds up while recovering** (30 s → 4 s) and drives the sign; it restores 30 s
  when recovery ends.
- **`chatEndedEvent`** — already in the chat feed we poll and previously skipped — now raises a signal
  that prompts an immediate status check. It never decides anything: `liveBroadcasts.list`
  `lifeCycleStatus` stays authoritative, with `liveStreams.list` health as the push-received signal.
- At `complete`: red OFF AIR (the existing stop path) rather than a pretend-live sign.

Tests: `ChatEndedSignalTests` (the marker is not a chat row, the service raises the signal, and a
complete broadcast ends recovery with the honest message). FAST gate: 543 passed, 0 warnings.

2026-11-05 14:53:06 -08:00

2.3 KiB

Raw Blame History

HANDOFF — 2026-11-05 (alert stack + media/chroma fixes)

State

main. TASK 21 (video layer + soundtrack), TASK 64 (green/blue screen) and TASK 32·4 (fragmented MP4) are complete; TASK 49 is retired (YouTube owns chat moderation — we just don't paint tombstones).
Left panel alert stack shipped: Steam licence indicator pinned at row 1 (Entitlement 30 fps · Maximum 60 fps, pin → close once owned, permanent while owned), event rows LIFO beneath, click → About or the Logs tab with that event's lines painted. Detail: docs/ai/ui-surface.md.
Video layer fixes this session: the preview-pane trigger whitelist (a video layer was invisible), a quadratic frame copy that capped 1080p playback at 2 fps, and deadline pacing for video and audio.
Tests: 575 green, 1m50s; FAST=1 ./scripts/verify.sh = 527 in ~62s.

Next action

32·1 + 32·2 shipped: blip retry (immediate/+1/+2/+3 s), and the RECONNECTING sign driven by the status poll (4 s cadence while recovering) with measured elapsed/attempt only — the countdown was dropped after the creator pointed out YouTube's cutoff depends on variables we cannot see. The chatEndedEvent in the chat feed now prompts an immediate status check.
Next: 32·5 (ingest pre-flight), then 32·2/32·3 (countdown + Back on air) which need YOUR measurement take: pull the network on a private stream and time how long YouTube holds the broadcast.
Open loop: 32·4 is proven by construction only — kill ffmpeg mid-recording and play the file.
Do not push absent a checkpoint request.

Landmines

The preview pane draws frame-source layers from a whitelist of DataTriggers. A layer type with no trigger is invisible in the preview while its decode looks healthy (alert box 2026-09-26, scoreboard, video layer 2026-11-05). Add the trigger with the layer type; pin it with MediaPreviewDisplayTests.
Nothing in the suite drives the real cursor any more; the drag arithmetic is pure (DragReorderMathTests).
Integration tests constructing MainWindow must set a temporary LayoutPathOverride and clear it in finally.
Media sessions are keyed by path + look (MainViewModel.MediaSessionKey); never acquire by raw path.
Bundled FFmpeg stays outside the single-file exe (ExcludeFromSingleFile="true").

2.3 KiB Raw Blame History

HANDOFF — 2026-11-05 (alert stack + media/chroma fixes)

State

Next action

Landmines

2.3 KiB

Raw Blame History