feat(catchup): resolve persisted M3U archive intent through catalog access - #304
Merged
Merged
Conversation
This was referenced Sep 1, 2026
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 #285, parent #184. Non-draft replacement for #302; head/base/tree are unchanged.
Scope
Completes the remaining M3U Slice E catalog/access integration only:
PlaybackArchiveRequest/ typed archive resolution incatalog:api;catalog:refreshdelegates to the already-acceptedM3uCatchupTransportResolver;catchupMode/source/days/correctionare supplied byRoomPlaybackCatalog.resolveIntent()only for explicit catch-up intents;ResolvedPlaybackRequest;ResolvedPlaybackTimelineis carried with the resolved request;PlaybackIntent.Liveand existingresolveVariant()stay on the legacy Live path and cannot select an archive template;No Room migration, Media3 URL parsing, Guide UI, Xtream catch-up, DVR, local-timeshift, second player/seek/retry owner, new provider framework, or third persistent AVD.
TDD / exact-head evidence
RED preserved at
backup/catchup-285-catalog-archive-red-20260901/86d71bf0090aa1c5c9a841ee752ec1802fed63fd.Qualified exact head:
dfb4204e5b61fc5f87821b63a14747351c733b63, directly on acceptedmain@d124358bc7a3e616114cc74cc19c92e0760275fb, shape 1 ahead / 0 behind.Exact-head GREEN evidence already completed on this identical SHA:
#302 was closed only because the connector's ready-for-review GraphQL mutation fails on removed GitHub field
Repository.fullDatabaseId; no code or branch ref changed.