MOSS-Image-SFT, MOSS-Image-NSFW and Kromoss all failed as "Failed to load
image model", with a 404 naming the repository -- which read as the model not
existing on the Hub. All three repositories are public and complete; the 404
was on a file.

They declare _class_name: MOSSImagePipeline, a class that ships in the repo,
so kwargs_for_declared_class passed custom_pipeline=<repo id>. diffusers
resolves a repo id by one convention only: pipeline.py at the root. These
repos call their file pipeline_moss_image.py, so every attempt fetched
<repo>/resolve/main/pipeline.py -- a path that had never existed.

So read the module name instead of assuming it. model_index.json names it: a
component slot holding neither diffusers nor any installed package is naming a
module that travels with the weights ("scheduler": ["pipeline_moss_image",
"MOSSImageScheduler"]). Given that bare name diffusers does the right thing --
load_pipe_from_hub looks for <module>.py among the repo's files and loads it
from the repo. None when the repo does ship pipeline.py, so every community
pipeline keeps the resolution that is already correct for it.

The log line now names repo and module both, since the gap between them is
what a 404 on this path is about.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014T3rZozi1Ehk96NG1WesgC