Fix stream keep-alive handling and bump to v1.0.0

- Force-close each /stream/{channel_id} response instead of allowing
  keep-alive reuse. Jellyfin's SharedHttpStream tuner client was reusing
  a pooled keep-alive connection mid-stream from an earlier request and
  reading raw MPEG-TS bytes as an HTTP status line, failing with
  'Received an invalid status line'.
- Broaden the disconnect exception handling to ConnectionAbortedError
  alongside ConnectionResetError.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WDDfSVPh5pgNe7TRpZUgJA

CHANGELOG.md

@@ -14,3 +14,13 @@ All notable changes to this project are documented in this file.
   (`channels.example.yaml`, `.env.example`).
 - Unit test suite covering config parsing, URL expiry parsing, ffmpeg argument building, playlist generation, and
   broadcast fan-out.
+
+### Fixed
+
+- `/stream/{channel_id}` now forces the connection closed after each response (`Connection: close`) instead of
+  allowing keep-alive. Jellyfin's M3U tuner client (`SharedHttpStream`) was reusing a pooled keep-alive connection
+  still mid-stream from an earlier request and reading raw MPEG-TS bytes as if they were a fresh HTTP response,
+  failing with "Received an invalid status line".
+- The yt-dlp resolver now correctly classifies which of the two `requested_formats` entries is audio when a live
+  stream is split into separate video-only and audio-only renditions; it previously relied on `acodec` being set,
+  which yt-dlp does not consistently do for audio-only formats, causing every resolve to fail.