test(catchup): verify Xtream archive metadata persistence green - #317
Draft
MrFr3di wants to merge 2 commits into
Draft
test(catchup): verify Xtream archive metadata persistence green#317MrFr3di wants to merge 2 commits into
MrFr3di wants to merge 2 commits into
Conversation
This was referenced Sep 2, 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
1 participant
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.
GREEN checkpoint for #315 Task A, parent #184.
Exact head
c6a64ee2c39c50acbeb5f0ea4dcba44986210b0dcontains the observed RED test from #316 plus the minimum production mapping inXtreamLiveRefresher:tv_archive=truepersistscatchupMode=xtreamand the normalized retention days through the existing generic catalog import fields; false/null does not declare catch-up. No Room schema/DAO/importer/UI/player/workflow changes.This PR is an immutable verification checkpoint only and will not be merged; the final #315 implementation will use a fresh non-draft PR after Tasks B/C and composition are complete.