[0xShug0]

Managed package loading currently duplicates model-specific entry-file and component selection rules in the WebUI. Move those rules into model-owned resolvers for YuE2, AuK, MiniMax Music3, LFM2 Audio, LiveAvatar and MiniMax-H3.

• The package manager supplies only package facts: family, root, installed-relative files and format. It does not interpret load or session options.
• Each model resolves its selected files into the existing path, load options and session options. The registry dispatches by explicit family; the server and UI consume the normalized result without duplicating those rules.
• Studio, Arena and app model choices use the resolved targets, preserve explicit component overrides and imported direct paths, and wait for resolution before managed loading.
• Existing CLI loading, server configs and path-based loader selection remain unchanged. No model specs, inference math or public loading flags are changed. The WebUI bundle is rebuilt.

Related to #1098: this supplies the model-owned resolution boundary; it does not add package-ID loading to the CLI or server config.

Validation

• Debug build with CUDA and Vulkan enabled; six focused CTest targets passed, including resolver and package-manager coverage.
• WebUI type checking/build and browser workflow checks passed.
• Real CUDA server loads through both legacy paths and resolved targets passed for all six models. Browser combination switching completed 12 generation cases, with selected paths/options checked against the loaded models.
• Existing YuE2 and Music3 server example configs worked with only their placeholder model paths replaced: lazy startup, documented API request, successful load and audio response.
• CLI inspection passed for all six models; real CLI generation passed with a Q4 YuE2 main model and F32 VAE. Server configuration tests passed.

Browser scripts, model assets, generated media and validation logs are not included.