The models page's Tidy chip (with a count) reads every model's header (model_kind) and lists files whose type does not match their folder - such as an Anima/Flux/Wan diffusion model in checkpoints, which Civitai labels "Checkpoint" - with why it matters, where it belongs (same subfolder, same drive) and Move there, taking its cover, info and notes along; never over a file. A whole checkpoint in diffusion models is marked as loading anyway. Identical files are grouped by SHA-256 (scan hashes; same-size unscanned files on Compare); each copy can go to the Recycle Bin. Moves are logged (model_move). Also: opening the Tidy or Sources view stops cards of an earlier load from being drawn into it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Architecture Topic Guide
Start with the repository-root ARCHITECTURE.md, then
open only the topic needed for the current task.
backend.md: Python routes, filesystem safety, persistence, scan state, model sidecars, and backend performance.frontend.md: extension bootstrap, UI ownership, localization, media lifecycle, panel state, and graph mutations.recipes.md: Workflow Recipes, packages, galleries, Parameter Notebooks, prompt roles, and recipe-to-model transitions.material-library.md: saved prompts and node values (material files), keeping an output image, and dragging prompts onto the canvas.recipe-model-lifecycle.md: authoritative model fields, Hash synchronization, local matching, partial append, and note privacy.model-resolution.md: model provenance, Model Check, hash injection, model scanning, and recovery policy.../decisions/README.md: concise records of product and architectural decisions that still explain current behavior.
These documents describe current contracts rather than implementation history.
For exact changes, use Git history. For user-visible releases, use
CHANGELOG.md. For recurring implementation traps, use
lessons.md.