Repository navigation
feat: build event guides automatically for high-confidence event channels (#175, event slice 3) - #256
Conversation
…nels (#175, event slice 3) Channels the detector rates high get a guide built from their own provider programmes (real titles and times, channel name in gaps). Any parse problem, missing time or error falls back to the normal provider guide; no channel is dropped. Saved user choices win. Frozen contracts are untouched. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf
…ed titles as filler (#175) Real EPG Ripper check: 46% of programmes use offsets other than +0000, which made four PPV channels fall back to the normal guide. The reader now applies the offset and uses the UTC instant. Titles such as Next PPV Event is To Be Advised are filler, not events. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf
|
Update after a read-only check on the real EPG Ripper and Jesmann US guides. Found: 46% of EPG Ripper programmes use offsets other than +0000, so four PPV channels (Prima Sport PPV1 to PPV4) fell back to the normal guide only because of that. The event guide reader now accepts any +/-HHMM offset and uses the UTC instant. A bad offset still falls back. Titles such as Next PPV Event is To Be Advised are now filler. No channel was dropped on either guide (applied + fallback = high). Tests under PowerShell 7: 69 passed, 0 failed, 1 skipped (needs an env var). Not verified: the fix on the real guide (re-check running), Windows PowerShell 5.1, the full suite (CI). The guide window code still reads only +0000 stamps; a guide with none would fall back safely. 🤖 Generated with Claude Code |
|
Re-check on the real guides after the offset fix (read only).
Known, not fixed: provider stop times of the form hh:59:59 followed by a start at hh:00:00 leave 1-second blocks titled with the channel name between programmes. No gap or overlap; cosmetic only. Not verified: the real build script and merged-guide ids, Windows PowerShell 5.1, the full suite (CI). 🤖 Generated with Claude Code |
Event slice 3 (#175, issue #30). Channels the detector rates high now get an event guide built automatically from their own provider programmes. No approve or reject step.
Frozen contracts (guide-id v1.0, digest projections, M3U entry byte format, BuildIdentityInput, blocker-2-contract/v7, accepted-state, transport/trust) are not touched.
Tests under PowerShell 7: all relevant files 0 failed, 6 new. About 255 lines changed including tests.
Not verified: real provider guides (a read-only check is running; this should not merge until it is read), Windows PowerShell 5.1, the full suite (CI), and a full Build-My-Lineup run with an applied event channel. The reader accepts only +0000 XMLTV times; other offsets fall back to the normal guide. Venue, city and carrying channels are not written yet.
🤖 Generated with Claude Code
https://claude.ai/code/session_01NzHAckAcs78Lu3rv8Gqgrf