To change a picture from the gallery the AI had to open the saved card and set back, one by one, the model, LoRA and prompt the picture had been made with (8 to 12 calls in the exam). open_workflow now takes a picture's name too when no saved workflow has it: the server checks the picture is in the output folder and carries a workflow, and the page reads it from the PNG and opens it in a new tab, without the marks of the tab it ran on (the card that tab came from, which run_workflow would mistake it for, and its group of saves). The tool list is 18 characters shorter than before. Retaken with Gemini 3.8 Flash, questions 3 and 4 only: question 3 on a changed picture went from 28 calls (7 failed) to 21 (4), opening the picture's own workflow; written into docs/architecture/tool-exam.md. 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.
ui-flows.md: the UI map's hand-written part, in Chinese: what each part of a page is for, what a click does and why, and one name per thing (a glossary the structure check enforces). Where a word on screen is drawn and what it calls comes from the code:node tools/ui_map.mjs find <words>(tools/ui_map.mjs, its indextools/ui_map_scan.mjs;buildwrites the whole map to the untrackeddocs/ui-map.md).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.