Remote Chat Failover Needs a Tab-Stop Origin Banner, Not a Skeleton Overlay

<p>Our quiz app shows the same countdown twice: once on the host's screen behind the bar, and once on every player's phone. Same clock, same seconds, two separate components

<p>I tabbed onto Retry after a sluggish timeout, and VoiceOver still described the composer as empty. The Network panel told a much less comforting story about that same impatient

<p><strong>Short answer:</strong> Treat every typing-start signal as a renewable client-side lease, expire it locally, and use the stop event only to hide the indicator sooner; a