DemonGatanjieuandClaude Opus 5.5
d379581853
"Doctor" said little about what it does: check the opened workflow's models and put back the ones this computer has. The rail, page, home card, help, tour, README, the unreleased changelog and the architecture docs now say Model Check (模型检查); the help paragraph now describes the check as it works today. Code, CSS and locale keys keep "doctor"; released changelog entries, audits and decisions keep the old name. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
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: generated-image snapshots, material assets, node-block reuse, and Model Check handoff.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
.agents/logs/ai_lessons.md.