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.

HANDOFF.md

@@ -13,8 +13,11 @@
 
 ## Next action
 
-- **TASK 32·1 shipped** (blip retry, immediate/+1/+2/+3 s, alert-stack episodes, complete-broadcast check).
-  Next: 32·5 (ingest pre-flight),
+- **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.