refactor: unify video asset readiness and repair warnings - #6688
Merged
Conversation
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.
Video Gen now describes the model, shared encoder, substitute encoder, and IC-LoRA weights in one asset list. One hook derives readiness and independent integrity dismissals, and one banner renderer routes repairs to the matching download. Generate and Add to queue now name the same first missing asset, including substitute encoders.
The model-specific loading gate, off-machine bypass, repair/download suppression, and changed-damage dismissal keys retain their existing behavior. Missing encoder metadata no longer produces literal
undefinedin repair messages. Repair banners have accessible group names.Validation:
Complexity measured against this branch's actual base (
ac2a79c60):VideoGenCC 303 → 218. The same Babel AST counter was used for both: baseline 1 plus conditionals, logical expressions, loops, catch/default patterns, non-default switch cases, and optional member/call branches, excluding nested functions' own paths. This is a fresh measurement rather than the issue's older 328 baseline. The page has zerocached === falsechecks and no per-asset integrity dismissal states.Closes #6681