feat(catchup): resolve Xtream archive through existing playback intent - #319
Open
MrFr3di wants to merge 10 commits into
Open
feat(catchup): resolve Xtream archive through existing playback intent#319MrFr3di wants to merge 10 commits into
MrFr3di wants to merge 10 commits into
Conversation
MrFr3di
force-pushed
the
feat/315-xtream-catchup
branch
from
September 2, 2026 19:04
fb218f5 to
cee8500
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #315, parent #184.
Completes the bounded Xtream catch-up slice through the existing provider-neutral playback architecture; no second catch-up framework, player path, provider registry, or Room schema change.
Implemented:
tv_archive/tv_archive_durationthrough the existing generic catch-up metadata;CatchupProgramintents into an opaque Xtream archive reference plus the existingResolvedPlaybackTimelinecontract;XtreamPlaybackReferenceResolverusing the existing credential lookup,SourceUrlPolicy, exact HTTP approval and redaction ownership;/timeshift/{username}/{password}/{duration}/{start}/{streamId}.{ext}, with duration in minutes and UTCstartformattedyyyy-MM-dd:HH-mm;NotApplicable;SUPPORTEDin the compatibility corpus without claiming alternate timeshift dialects.TDD evidence includes separate RED/GREEN checkpoints for metadata persistence, archive intent resolution, transport materialization, and M3U+Xtream application composition. Composition RED:
a50e0a4673fd93a9203d65afaa343549d51be22f; production composition:b0aad3230bd3011e32f69867fee10b82051ccb34.Final exact head
cee85003f38637b28b0e2169ce725db7196726b4isahead 10 / behind 0againstmain22011085b52179c33661c8fc11e37137785d3a02and passed:Compatibility note: the first implemented Xtream timeshift dialect derives the start value deterministically in UTC because the bounded source model does not persist provider/server archive timezone. Alternate panel timezone/dialect behavior is intentionally not claimed by this PR.