DemonGatanjieu-Anomalous_Model_Browser/ARCHITECTURE.md

Anomalous Model Browser Architecture

This is the short entry point for maintainers and AI agents. It describes the system map, ownership boundaries, and rules that apply across subsystems. Read only the linked topic document relevant to the task; do not load every document by default.

Reading map

Before implementation, follow AGENTS.md, the canonical development and maintenance rules; its section 0 is required for every commit.

Saved prompts and saved node values are material files (anomalous_materials); there is no Material Library page any more. Prompt Studio lists the saved prompts (reading each body through web/modules/material_prompt_data.js; list summaries do not contain prompt bodies) and Current node lists the saved values. See the material contract below.

When changing...	Read...
Python routes, storage, paths, metadata, covers, or scan state	docs/architecture/backend.md
Browser lifecycle, UI state, localization, media, or graph edits	docs/architecture/frontend.md
Update-guide content/versioning or sidebar hover labels	docs/architecture/update-guide.md
Workflow Recipes, packages, galleries, Parameter Notebooks, or prompt roles	docs/architecture/recipes.md
Saved prompts and node values (material files), image parameter details, keeping an output image	docs/architecture/material-library.md
Model Check, provenance hashes, missing-model recovery, or model scanning	docs/architecture/model-resolution.md
Why a current product boundary exists	docs/decisions/README.md
Recurring implementation mistakes and post-mortems	docs/architecture/lessons.md

README.md is user-facing documentation and CHANGELOG.md is user-facing release history. Neither is the source of truth for internal architecture.

System shape

Anomalous Model Browser is a UI-only ComfyUI extension. It registers no custom nodes (NODE_CLASS_MAPPINGS is empty). ComfyUI loads the Vanilla JavaScript/CSS frontend from web/; the Python package registers /anomalous/ aiohttp routes and performs local filesystem, metadata, recipe, and scan operations.

ComfyUI frontend
  web/main.js
    -> web/modules/*                 UI, graph integration, localization
    -> /anomalous/*                 JSON and bounded media requests

ComfyUI Python server
  __init__.py
    -> api/__init__.py               route registration
    -> api/*.py                      storage and domain operations
    -> scraper.py                    explicit metadata/hash enrichment

User-owned data
  ComfyUI model folders              models and sidecars
  user/.../anomalous_recipes         workflow recipes and recipe assets
  user/.../anomalous_parameters      immutable parameter snapshots
  user/.../anomalous_materials       curated image/workflow material bundles
  user/.../anomalous_notebooks       prompt notes, with legacy originals preserved

The frontend and backend communicate through narrow JSON contracts. The frontend must not infer filesystem authority, and the backend must not depend on DOM or live LiteGraph state.

Ownership map

This map, with the topic documents, is also the file directory: every source module under api/, web/ and web/modules/ and each root Python file is named with its owner. node tools/check_structure.mjs checks this. Styles are covered by the styles.css manifest.

Backend

• api/ai_run_tracking.py attaches exact external prompt IDs to one task, prevents duplicate ownership, and returns bounded-wait execution receipts to the AI.

• api/ai_run_watch.py reads what a run shows beyond its node and steps: ComfyUI's console since it began (app.logger's buffer: the bar with its note, the models loading), the time per step and left, the card's memory, and once per run the size each sampler works at from the queued prompt, with warnings (an upscaled picture sampled again, a size past the card, a huge decode). api/ai_run_control.py stops a run (stop_run, the workbench's stop button): only its own prompts leave the queue or are interrupted; the step ends cancelled and a user's stop reaches the AI as a stop message. tests/test_ai_run_watch.py.

• api/ai_run_map.py reads a run's shape from the prompt ComfyUI queued (plumbing wired through; boxes with a role and facts, links with ComfyUI's types) and what changed since the task's run before; ai_task_runs.py keeps both on the run step, show_run_map puts it on the stage (a run_map block), web/modules/ui_ai_run_map.js words and draws it (Simple: told by web/modules/ui_ai_run_story.js, one part per sampler with the model and LoRAs feeding it, its prompts, where it starts and where it ends up; Full: top down, shrunk to its column). api/ai_task_canvas.py keeps each task's own canvas tab (default "new", set in the Gates window or per task): mcp_bridge.ask_page gives canvas actions the task's tab, web/modules/mcp_task_tab.js brings it to the front by clicking ComfyUI's tab (the store alone would not load its graph) or copies the open workflow into a new one before the first change; web/modules/ui_ai_task_canvas.js is the header's switch and the tab's chip. ai_pictures.mark_gone marks a task's pictures no longer in the output folder (gone) on its GET, which ui_ai_images.gonePicture shows instead of a broken picture. api/ai_pictures.py hands the AI output pictures (gallery card menu, the inspector's ✦): a user_pictures step, delivered as a pictures message with the pictures attached and what made each (read with ai_run_map); search_images(with_pictures) attaches the first six. tests/test_ai_run_map.py.

• api/config.py owns configured paths and active model-folder types.

• api/path_utils.py owns containment, filename validation, atomic JSON writes, and resolving a saved model value inside the model folders; api/utils.py is a compatibility export surface.

• api/metadata.py owns sidecar and safetensors metadata extraction. A model's information has three layers, the user's first: <model>.anomalous.json (what the model editor set; only the editor writes it), the scan result (<model>.info, or another tool's .civitai.info with Civitai ids; id: -1 means inferred from the file) and the file itself. Metadata reports info_source (civitai / local / empty) and user_fields. A cover is Civitai's only while it is byte-identical to <model>.civitai_bak.*; any other cover is the user's, and no scan replaces or deletes it.

• api/model_catalog.py, api/model_resolution.py, api/model_metadata.py, and api/model_media.py own model listing, identity recovery, mutation, and covers; api/model_folder.py shows a model file in Explorer / Finder, or without a file name opens the models folder (by type, folder index, subfolder and file name, never a path; a POST, so only this computer may ask); api/models.py is a compatibility facade; api/model_constants.py holds the model, media and sidecar extensions they share. api/model_type_listing.py lists a whole models folder with its subfolders for the models page's type chips.

• api/scanner.py and scraper.py own scan orchestration and enrichment; both scan routes map request fields to scraper switches in one place (_scraper_flags). civitai_client.py is the scraper's network side (version by hash, model page, media), telling "Civitai does not know the file" from "Civitai could not be asked" (and why); it asks Civitai's other address (civitai.red) when civitai.com does not answer (api_hosts, also for import, Model Check and the network test). net_proxy.py is the proxy every request of the plugin goes through (Settings → Network, NETWORK_PROXY in api/config.json; empty = urllib's own: HTTPS_PROXY or the Windows proxy), handed to the scan process as HTTP(S)_PROXY, and the names of why a request failed; api/network_check.py (GET /anomalous/civitai_check, this computer only) tests Civitai through it. api/scan_report.py turns the scraper's per-model report lines into one result per scan: kept as the last scan (/anomalous/last_scan), recorded in the activity log, each model located so the browser can open it (/anomalous/scan_model). api/kept_images.py says what each output image was kept as, for the gallery's star: the Workflow Recipe, combo or saved prompt that names it as its source image. api/quick_index.py (GET /anomalous/quick_index) lists every model file in a few words (type, place, shown name, base model, a few trigger words, cover URL) for the canvas's quick search, read once when the bar opens. api/scan_summary.py counts models matched on Civitai, unmatched and not yet scanned for the scan page and lists the last two, by the same sidecar rules the scraper uses (sidecar_info, is_unmatched, unmatched_reason in model_identity.py); it also lists the model files in other formats, which scans never read, so the page can say so, the models set to "don't scan", and the new ones whose header names no drawing model kind. It keeps the last summary (memory and user/anomalous/scan_summary.json) for the page to show at once, shares one count among the requests meanwhile, and lists the models found on Civitai on request (GET /anomalous/scan_matched). api/model_heads.py keeps what each model file's header says (model_kind.inspect_file) in user/anomalous/model_heads.json by real path, size and time, so a header is read once per file version, also across restarts; get_metadata reads headers through it. Models in component folders (VAE, text encoders, CLIP, CLIP Vision, upscalers) are counted and listed apart as well (components, component_models): many are not on Civitai. It also lists every model a scan reads for the scan settings' picker (/anomalous/scan_pickable), with size, cover and the card badge's metadata fields. api/scan_choice.py saves that choice (POST /anomalous/scan_choice, this computer only) into each model's <model>.anomalous.json.

• api/mcp_server.py serves /anomalous/mcp, the Model Context Protocol endpoint AI apps connect to (Streamable HTTP; the 2026-07-28 stateless protocol and the earlier initialize-based ones; this computer only, Host and Origin checked against DNS rebinding). api/mcp_tools.py holds the reading tools (summarised views over the same stores the pages use: models, scans, output images, combos, recipes, saved prompts, generated audio, activity log) and call_tool; api/mcp_actions.py the acting ones: canvas actions done by the open page, scans and Anomalous TTS speech through this server's own routes. api/mcp_bridge.py hands a canvas action to the page over ComfyUI's websocket and waits for its answer; web/modules/mcp_bridge.js is the page side, doing it with Anomalous's canvas code (one Ctrl+Z step each, logged as the AI's; the outcome carries the log entry's id as _activity, for the AI workbench's undo). api/mcp_canvas_edit.py holds the tools that build a workflow where the user watches: find_nodes reads this ComfyUI's node types from its own /object_info (kept two minutes); add_node, connect_nodes, set_values, remove_nodes and new_workflow (a new tab, blank or built from a workflow in ComfyUI's API form, never the open one) are checked for shape there and done by web/modules/mcp_canvas_edit.js through the bridge's recorded, after checking types, settings and choices against the nodes themselves; web/modules/canvas_build.js is its pure part (type fit, value checks, a free spot, the layered layout). open_workflow opens one of the user's saved workflows in a new tab. api/ai_toolbox.py keeps what the user hands the AI to work with in a task ("给 AI 的素材", web/modules/ui_ai_toolbox.js, from the task header a side panel (on the AI page a view of its side column, setToolboxHost; elsewhere docked on the right) that leaves the page usable (kinds as tabs, one line per item (rowCard), a card's detail over them) or, expanded, a large window: search, kinds, a column by source / origin / type, a card grid drawn as it scrolls, a detail pane, the picks below; the last choice is kept in the browser), by the names the AI's tools use (and whole custom node packs by folder, packs: get_toolbox lists their node types, chosen counts them picked), with a mode: prefer, or only (add_node / new_workflow then refuse other custom or paid node types). Node types come from the page's own definitions (web/modules/ai_toolbox_data.js: LiteGraph's registered types and their nodeData, so no request; page-only helpers go with their pack when their name says which); the rest in one answer from api/ai_toolbox_catalog.py (combos, workflows with covers and prompts, prompts saved or inside combos and workflows as combo:<name> / workflow:<name>, models with covers), read ahead when a task header is drawn and kept a minute. web/modules/ui_ai_toolbox_cards.js draws the cards (a node in miniature with its sockets in ComfyUI's colours, covers, prompt text) and the detail pane; web/modules/ui_ai_toolbox_icons.js each pack's badge, and the illustrations (web/assets/toolbox_*.webp, made with ChatGPT): the empty selection and the stand-in cover of a combo, workflow or model. Favourites (anomalous/ai_toolbox.json) stand in until the user picks for a task. A pick is a user_toolbox step the AI gets as a message (kind toolbox); begin_task names the picks, get_toolbox gives them in full, find_nodes lists them first. A rewired input shows in the receipt as a wired change (activity_diff.js keeps what feeds each input). web/modules/mcp_run.js captures exact prompt IDs from one native queue request, preserving native seed/widget callbacks and excluding later manual batches. Busy submissions and unsupported host request IDs are refused before queueing; wrappers/listeners are released. api/mcp_prompts.py serves prompts/list / prompts/get: ready-made requests (the AI app's slash commands) that tell the AI how to do a common job so the user can follow it on the AI workbench. api/mcp_apps.py serves the MCP Apps extension (io.modelcontextprotocol/ui): api/mcp_app/task_card.html, Anomalous's own card that apps supporting it show in the conversation under begin_task, show_panel, report and run_workflow results (resources/list / resources/read, _meta.ui.resourceUri on those tools). The card reads the task through app_task_view (steps, inline gallery thumbnails, open questions) and answers the AI's questions through app_answer, tools marked for the card only (visibility: ["app"], never steps, never given the user's news). It never answers a gate: an OK is only given in Anomalous, so no tool an AI can reach grants one. User guide: docs/guides/mcp.md.

• The AI workbench (1.62). api/ai_tasks.py keeps every MCP call as a step of a task (one file per task in the ComfyUI user folder, anomalous/ai_tasks/, the newest 300): a task is named by the AI (begin_task) or is one app's calls without a long pause (20 minutes); a step keeps the tool, a short summary, whether it worked and what it made (models, the combo, the canvas change by its activity entry, the spoken audio, the scan; a run's pictures are watched in ComfyUI's history until it ends, api/ai_task_runs.py, which also reads where it stands from ComfyUI's queue and progress registry, never changing them: queued and how many are ahead, or the node running, its steps, a percent like ComfyUI's tab title and the nodes done; kept on the step in memory, sent to the page as progress events that only move the step's bar, and given to the AI by run_status, which can wait for the run to end, and as your_run with one sentence in the AI's other answers while it goes and once after it ends, so the AI need not look for itself; the console's lines, time left, memory and the size warnings come with it, api/ai_run_watch.py, and the page draws them with a stop button, web/modules/ui_ai_run_live.js). A step a restart left "running" is marked stopped when the record is read again. What each tool is, in one place, is api/action_catalog.py: its kind (colours, words, counts), the stage of the work it belongs to (model, combo, prompt, canvas, run, picture, voice, library: the flow over a task) and its gate (canvas, gpu, download, network: what the user may want to approve); a test keeps it and the MCP tools in step. api/ai_task_changes.py puts the user's own changes (activity entries, activity_log.add_listener) made while an AI works into that AI's task as user_activity steps, which the AI receives once with its next call (a message of kind change); activity_log.tag names the task on the entry, and the activity page links to it. api/ai_gates.py holds the user's gates: each gate is auto, ask or never (anomalous/ai_gates.json, /anomalous/ai_gates); mcp_server.py asks it before running a tool. With ask the step waits in state asking (what it would do listed) for up to 50 s; the user's Allow or No comes through POST /anomalous/ai_tasks/{id}/gate. Unanswered by then, the AI is told to wait and call again; the later answer reaches it as a message of kind gate, and the same call made again after an Allow goes ahead without asking twice. api/ai_marks.py keeps the marks the user draws on an output picture for the AI (POST /anomalous/ai_tasks/{id}/marks: the marked PNG, checked, kept in anomalous/ai_marks/<task>/, never the output folder, gone with the task; the marks as fractions with notes): a user_marks step the AI receives like a message (kind marks) with the marked picture attached as an image to the same answer. web/modules/ui_ai_marker.js is the marker window (box, circle, arrow, pen; three colours; a note per mark; a brush for the area to repaint) opened from a picture's ✎ on the AI page, and the timeline row of marks sent. With "make a repaint mask" the page also sends a mask (white where boxes, circles, lines and brush strokes are); the server writes the picture with that area as its alpha to ComfyUI's input folder as anomalous_inpaint_<step>.png (a new file, never replacing one; kept when the task goes, as workflows may load it), and the AI's marks message carries its name with how to inpaint with it (LoadImage gives the MASK). The canvas tools read ComfyUI's lists anew once when a value is not among a drop-down's choices, so they take such a new file. web/modules/ui_ai_gate.js draws the card under a step that asks and the Gates window; ui_ai_flow.js the flow over a task (its stages in order, each done, running, waiting or failed; a stage leads to its first step). ui_ai_handoff.js is "Hand to AI" on a model's page, an output image's inspector and a combo card: a task the user starts with about (the model's model_id, the image, the combo's name; checked in ai_tasks.start_task), which begin_task hands to the AI, and the sentence to paste into the AI app. It tells the page through the anomalous.ai_task event; api/ai_tasks_routes.py serves /anomalous/ai_tasks (list, one task, start, rename or remove, a panel's answer, a message). The user can start a task first (New task): it waits, and the next app that calls takes it over, so its work starts there instead of joining its last task (one waiting at a time, found again after a restart). begin_task resumes a waiting or active task, including preliminary reads, and keeps a user's title; new_task=true explicitly separates a new request. Ended or idle tasks are not resumed. mcp_server.py starts an in-flight "running" step before each call and updates the same step in place when it finishes or fails (the app's name from its client info or User-Agent); api/mcp_task_tools.py holds the AI's own tools for it, begin_task and report (a note, with pictures from the output folder it made another way). web/modules/ui_ai_workbench.js is the page (rail entry ai): the tasks, one task's results strip and timeline with links (picture viewer, model page, combo, canvas locate and undo, scan page, ▶ for audio), updated live; also the home page's "What the AI did lately" and the rail's dot (owner.railNews). A task's parts stay in the page between redraws: a step is drawn again only when it changed (syncRows), so a scrolled diagram or strip and half-typed text survive the AI's steps coming in. ui_ai_message.js is the message box under a task (made once per task); ui_ai_mention.js gives it "@" (the task's pictures, combos, models, workflows, prompts, node packs and node types from the materials picker's data, chips of what is named) and "/" (ui_ai_commands.js: stop, undo, side views, new task, canvas mode, words to fill in); api/ai_message_refs.py checks what the "@" name and gives each to the AI with the message (in full, pictures attached; get_toolbox shares its lookup), tests/test_ai_message_refs.py. ui_ai_step_body.js is what a timeline step says under its title (the user's own steps with whether the AI has them, a decision's card, the AI's note). api/ai_decisions.py keeps a task's key decisions: log_decision (the AI records what was settled, why, what was left out, who decided, the steps it is about; a decision step), and the user's own choices read from the task's steps (panel answers, gates, materials, the canvas mode — ai_task_canvas.set_mode adds a user_canvas step — and stops); GET of a task adds decisions and decisions_gap (runs and canvas changes since the AI's last one), begin_task repeats them to an AI picking the task up. ui_ai_decisions.js draws the card and the side column's Decisions view. tests/test_ai_decisions.py. api/ai_task_links.py keeps which task a task goes on from (from: set when an AI begins a new task while on another, or the user starts one while looking at a task; changed or taken off by the user, never a loop); GET of a task adds links {from, next}, begin_task gives an AI the task it continues and what was decided there (continues). ui_ai_task_links.js shows them under the task's title and picks one to link. tests/test_ai_task_links.py. ui_ai_recent.js the home page's list, ui_ai_results.js what a step made and where it leads (and the strip of a task's results). ui_ai_side.js is the stage, the column on the right where the AI's panels are shown (the timeline keeps a line per panel that brings it there): like the timeline it reads from the top down, the task's panels in the order they came with their step numbers, the newest at the bottom. Opening a task, new/updated latest panels and late image loads follow the bottom while the reader is there; reading earlier content pauses follow, with a "See latest" button to resume. Timeline links instead locate the requested panel's start. The stage's close button hides it for the selected task (stage.hidden); updates preserve that choice and its DOM/drafts. A timeline panel link reopens it; selecting a different task resets it. The stage is one view of the side column: ui_ai_side_views.js is the switch in the window title bar, AI page only (stage, a run's node map at full size with a list of the runs, the materials picker; the shown one again closes the column), one pane per view kept between switches, and the picker's dock there. The task's header stays on top while the timeline scrolls. In a window too narrow for three columns the timeline and the side column are two tabs (a panel that asks brings the stage forward). The side column is a card whose left-edge grip sets its width (--ai-side-w, kept; the timeline keeps TIMELINE_MIN). The task list folds from the title bar's list button (headerLeadTools, listToggle); folded, pointing at it peeks the list over the page. ui_ai_task_list.js draws it (New task, Connect an AI and the gates, which AI came last, quick filters by state, the tasks by day with a state icon each). ui_ai_icons.js is the AI pages' one set of line icons and the icon button. ai_text_format.js lays out what the AI writes (its notes and replies: headings, lists, bold, code) with textContent only. A note may answer the user's message or marks (report's reply_to): the two steps point at each other, and the timeline links them both ways. ui_ai_connect.js says how to connect an AI app (the address, a sentence to send the AI so it sets itself up and starts on a waiting task, each common app's way), in a window from the list's "Connect an AI", and as a card (connectHint) that opens the guide in place on the empty page and under a task waiting for an AI (three numbered steps under a picture: what to do, the sentence to send, where the steps will show). The pictures (web/assets/ai_*.webp) were made with ChatGPT. ai_task_view.js holds its rules without DOM (folding reads, tool words, counts, result addresses). ask_user (api/mcp_task_tools.py) is the AI's question in the workbench: a one-block panel (choices with an optional recommended option and an other line, or an input) whose answer it waits for in the same call; the server instructions and begin_task tell the AI to ask this way rather than in its own chat. Panels the AI draws (show_panel, update_panel): api/ai_panels.py checks every block against a fixed set (heading, text, images from the output folder, models by id with their covers, table, list, params, choices, input, progress, divider; plain strings of bounded length, nothing run or read as markup) and keeps the panel as a step. update_panel preserves the order already seen: new blocks append; omitted blocks remain; unchanged resubmitted blocks match without their ids. Every new block gets a stable id, returned by the tools; an explicit existing id edits that block in place without changing its type or position. A uniquely labelled progress block also updates in place for clients that omit ids. The cumulative limit is 30 blocks; overflow or invalid input rejects the entire update before changing the panel, title or answers. Legacy records are not reordered on load; blocks without ids receive handles when updated. New phases should use show_panel. The user's answers come in through POST /anomalous/ai_tasks/{id}/answer and wait there until the AI reads them (get_answers, which can wait up to 55 s for one; Anomalous cannot call the AI). The user can also write to the AI on a task (POST /anomalous/ai_tasks/{id}/message, a user step); get_answers brings those messages too, and with no panel named waits for one; unread answers and user messages are also piggybacked once onto the next successful MCP tool response (ai_panels.attach_pending) so AI apps that do not poll get_answers still receive them immediately. web/modules/ui_ai_panel.js draws a panel in the timeline (textContent only) and the toast when the AI shows one while the user is elsewhere; a question can be skipped ({skip: true}, the AI reads skipped). web/modules/ui_ai_delivery.js is the pill under each answer and each thing the user gave the AI: sent and waiting, or the AI has it at delivered_at (set when ai_panels._collect hands it over). The stage blocks are data the page lays out, never drawings of the AI's own (no SVG is taken): marks on pictures (circles or boxes at fractions of the picture, a label that zooms there), the slider (before and after over each other), picks (pictures with a reason, "Take this one", "Put on the canvas" through ComfyUI's own file loading, drag onto the canvas) and the diagram (boxes and arrows; a box naming a canvas node finds it). ui_ai_stage.js draws them, ai_stage_layout.js holds where they go without DOM (a diagram's layers by its longest chain of arrows, boxes, arrow ends, marks).

• ui_ai_images.js connects task outputs and panel pictures to the existing image inspector, keep menu and ui_param_compare.js: tools over each output picture (shown on hover), and a tick; two ticked pictures, from any step or task, are compared from the bar at the foot of the AI page (a third tick replaces the oldest). Videos and temporary files get neither. Thumbnails load initially, metadata only after an explicit action. ui_canvas_changes.js renders the activity record's bounded before/after receipt for both the AI timeline and ui_activity.js, with a caller-owned locate action. Missing records show unavailable; receipts never reconstruct history from the current graph. The workbench retains only its selected task's activity entries and ignores superseded refresh/navigation responses.

• api/backup.py is Settings → Backup (/anomalous/backup/*): one .zip of the user's stores (recipes, combos, materials, parameters, optionally ComfyUI's saved workflows), the plugin settings without the Civitai key, and each model's user layer and own cover; putting it back adds what is missing, replaces differing files only on request (Recycle Bin first) and finds models again by SHA-256, else by folder, path and size. Its model list (every model's folder, path, size, SHA-256, link) names the models a new computer lacks. ui_backup.js is its export and import dialogs; ui_backup_downloads.js downloads the lacking models again through Model Check's downloads, into the path they had.

• api/lora_info.py reads a LoRA's safetensors header to tell whether it trains the text encoder (/anomalous/lora_info), so inserting it wires the CLIP line only then.

• api/model_download.py downloads the models a workflow misses (Model Check's "Download", /anomalous/download/*): one at a time into <file>.part, continued after an interruption, checked against the SHA-256 before it gets its name, never over an existing file; also where downloads go by default (download_settings.json). api/download_sources.py finds the one exact file: Civitai by hash, a Civitai version link, or a Hugging Face / GitHub file link the workflow carries, else a file of the same name in ComfyUI-Manager's model list (api/manager_catalog.py), checked by the hash. api/hf_card.py gives a model downloaded from Hugging Face its model card's example image as cover and its trigger words and example prompts as notes (never over the user's).

• api/model_import.py puts model files the user drops on the models page into the right models folder (/anomalous/import/*): finds the dropped file in this computer's Downloads or Desktop and moves it (or uploads a copy), tells what it is, checks it against Civitai and the scanned models, never replaces a file (" (2)").

• api/model_placement.py is the models page's Tidy check (/anomalous/placement/*): models whose header names another type than their folder, identical files (by SHA-256), and moving a model with its sidecars to where it belongs.

• api/model_usage.py is Tidy's "not used lately" (GET /anomalous/usage/check, this computer only, on a press): when each model and node pack was last used, from the run record, the PNG outputs' prompts (image_search's cached records, which keep the node types too), FLAC / Ogg sounds' prompts and the saved workflows, recipes, combos and parameter sets; nothing that came in the last 30 days is judged. Node packs come from ComfyUI's loaded packs, with whether they add to the page and which other packs take what only they make. Read with limits, deletes nothing. POST /anomalous/usage/keep (this computer only) keeps the packs the user says they still use, which no record can show, in user/anomalous/usage_kept.json.

• api/usage_ledger.py is the run record behind it: ComfyUI's on_prompt hook (registered in the plugin's __init__.py) notes each queued run's node types and model files with the time, and POST /anomalous/usage/opened (this computer only, capped lists) what an opened workflow holds, apart from the runs, in user/anomalous/usage_ledger.json, saved a few seconds later; it never stops a run.

• api/workflow_schema.py, api/recipe_schema.py, api/recipe_images.py, and api/recipe_store.py own recipe validation/shaping, images, CRUD, history, and integrity receipts; api/recipes.py is the HTTP facade. api/recipe_constants.py holds the size and count limits shared by recipes, parameters and materials.

• api/recipe_packages.py owns bounded inspect-stage-commit package handling.

• api/parameters.py owns Parameter Notebook persistence and lookup.

• api/notebooks.py owns combo (搭配, formerly Prompt Note) persistence and recoverable legacy copying.

• api/material_schema.py, api/material_assets.py, and api/material_store.py own curated material shaping, private assets, persistence/cache, search and lifecycle; api/materials.py owns HTTP mapping and compatibility entry points. api/node_material.py saves one canvas node's current values as a node_parameter_selection material (the current-node panel's "save").

• api/local_guard.py decides which requests only this computer may make (every change under /anomalous/; other devices may look), as one middleware, and lets other devices change things too when the server has an allow_remote_changes file (cloud servers); see backend.md.

• api/media_routes.py, api/gallery_routes.py, api/translation_routes.py, and api/folder_types.py own the formerly mixed utility route families.

• model_policies.py owns shared backend rename and protected-category policy.

• model_sidecars.py says where a model's side files are, shared with the scanner: beside it, or the plugin's own ones (.info, .anomalous.json, .civitai_bak.*) in the folder's hidden .amb (SIDECAR_LAYOUT in api/config.json); reading looks in both places. Covers stay beside the model. It also tells Civitai's cover from the user's (the SHA-256 a scan notes in the .info, or a copy kept aside, kept only while the user's own cover shows). api/sidecar_layout.py is Settings → Models → "Files that come with models" (/anomalous/sidecars/plan|apply, apply this computer only): saves the place, moves the files there and drops Civitai pictures kept twice to the Recycle Bin.

• model_identity.py owns file SHA-256 evidence and the base model a safetensors header tells, shared with the standalone scanner (which runs as its own process, so the API never imports scraper.py). model_kind.py reads a .safetensors / .gguf header (never formats that can carry code) and says which models folder the file belongs in and its base model; model import and the scanner's offline base model use it.

• recycle_bin.py is the only way the plugin deletes the user's files (models, covers, outputs, recipes, materials, notes, audio): to the system Recycle Bin, together, or not at all (TrashUnavailable on drives without one). api/trash.py is the API's import of it plus the message shown when nothing was deleted. The plugin's own temporary files, caches and bounded recipe history are still removed directly.

• api/audio_catalog.py owns the generated-audio side: the output-audio history, temp Preview Audio results (listed, and copied into output/audio/ on save), deletion, and streaming files from the output and temp folders. Characters and their reference clips belong to the Anomalous_TTS node and come from its routes.

• api/audio_metadata.py reads the ComfyUI prompt comment from FLAC and Ogg/Opus files (read-only) and extracts the TTS node's speech, sample and seed for the audio gallery.

• api/image_search.py powers the output gallery search (gallery_images?q=): it reads only the PNG text chunks before the pixel data (ComfyUI prompt and workflow, A1111 parameters), caches one record per image by mtime, and matches all query terms; hex terms of 8+ characters also match recorded model SHA256 values and, via collect_model_hash_index in model_resolution.py, local model files with that hash. Terms arrive as repeated term params, one phrase each. ui_search_chips.js is the reusable search-block input (Enter or a comma commits a block); ui_gallery.js places it above the gallery.

• api/version_manager.py owns the plugin's own version: the installed tag/branch (/anomalous/version, local only), published releases fetched only on request (GitHub releases API, falling back to git ls-remote tags; drafts skipped, pre-releases never counted as latest), switching to a published tag (detached checkout), returning to the default branch (fast-forward only), and undoing the last switch (recorded in the ignored .anomalous_version.local.json). Every switch refuses to run over modified tracked files. ui_version_manager.js is the version line (shown in the update guide opened by the header "!" button) and panel; nothing goes online until "check for updates" is clicked, and restarts go through ComfyUI Manager's reboot route when present. Every function takes an optional Checkout (another folder and its own state file): api/tts_version.py uses it for the companion node pack Anomalous_TTS, found among the custom_nodes folders by its node class and accepted only as a git clone whose origin is the official repository (/anomalous/tts_version, /releases local-only, /update, /undo; last switch in the ignored .anomalous_tts_version.local.json). ui_tts_version.js is its group in the GPT-SoVITS settings dialog: installed version, "Check for updates", update to the newest stable release or back, then the restart question.

• Generation presets (Anomalous_TTS interface 16): tts_presets_api.js holds the calls (/anomalous_tts/presets) and pure helpers (the language pairs the characters can meet, the presets file written back with only what differs from the built-in values plus the presets made here (custom_<id> with a label), where a preset is used and taking it out, a dialog row's numbers in effect next to the general ones, a character's defaults / defaults.by_language as rows and back, keeping every other field, where a mode sits between steady and lively, a line to listen with in each language). ui_tts_preset_switch.js draws the tones (the presets) as choices with the caller's listen row, and when asked for (Settings' Numbers switch, Voice-over's Numbers tab), the picked one against one fixed tone (the default one, or a character's usual): a sentence, a steady-to-lively scale and the four numbers as the Current node card's bars, each with its plain name and the node's own name (top_k …), editable in place. ui_tts_mode_preview.js makes and keeps the takes for listening (one line, one seed, only the mode changing, through Preview Audio). ui_tts_presets.js is the group in the GPT-SoVITS settings dialog (that switch with a character and a line to listen with, make default / reset / new / rename / delete; the rules per pair as a second part), saving each change at once; ui_tts_tuning.js is the per-character dialog behind the card's Own settings button, shown only with interface 16. ui_tab_strip.js is the row of tabs over one part at a time, shared by that dialog and Voice-over's side panel (the tab left open is remembered).

• web/main.js coordinates extension registration (with ?v=... versioned module imports busting aggressive browser ES Module caching and unconditional legacy storage key purging). browser.js owns the shared browser class and extracted-method wiring; browser_entry.js owns the single browser instance plus floating/topbar/menu entry behavior (pointer-capture drag, pre-mount positioning to avoid a flash, anomalous_trigger_pos_v3 persistence); the unsaved default position is defined in CSS; entry_controls.js owns entry mode, trigger size/style normalization, viewport clamping that keeps the button out of the sidebar dock, and saved-position storage (isValidSavedTriggerPosition); api/__init__.py sends Cache-Control: no-cache for this plugin's static files so a normal refresh revalidates them (modules are imported without ?v= query strings, which would create second module instances); and interface_settings.js owns language and theme preferences.

• ui_domain_switcher.js stores which side is active (image or audio: which list the list column shows, which guide "!" opens); the rail's pages switch it through ui_shell_nav.js. browser.switchAudioTab is the single entry for the audio panels (rail pages, the audio list's own entries) and hideAllPanels stops audio playback.

• audio_engines.js owns the audio page's one speech engine, GPT-SoVITS through the separate Anomalous_TTS node pack (docs/decisions AD-016), detected at runtime through /object_info/<node class>. Characters are normalised into one voice-group shape (node_value = what the node's character widget takes), so cards, sidebar and the Voice-over view share one implementation. While the pack is missing the studio shows install steps instead of cards; nothing else depends on it. Its data comes only from the node's HTTP contract, version 13 (/anomalous_tts/characters, /audio, /settings, /status, the pretrained download and import routes; the node repo's docs/INTERFACE.md); Anomalous never reads or writes its model folders. No call names a path on the computer: the storage place, other folders and package sources are set only in the node's settings file (status.settings_file), and imported files are always uploaded. loadGptSovitsStatus caches the setup status with the engine data (null for a node without /status, which hides setup and import). The character list is a summary without file lists; fetchGptSovitsCharacter gets one character's files. Engine presence and loaded voice groups are cached (MAX_AGE_MS) so re-renders from sidebar clicks, domain switches and the studio + sidebar pair cost no requests; invalidateEngineCache() drops them after a save or an added voice, and invalidateEngineCache({ rescan: true }) (Refresh button) also makes the node re-read its folders (?refresh=1). ui_audio_tts_editor.js is the reference audio editor (a character card's "Reference audio and emotions"): a large window with the voices on top (main voice, each emotion, new emotion) and every clip of the character below, one row each (listen, file and length, its line editable in place, where else it is used, Main / Aux for the voice picked), with filters, a search and the first 60 rows then more. It opens at once and loads the character's clips, their lines and lengths (/anomalous_tts/reference_lines) in the background (save waits for them), and keeps settings fields it does not know; 🗑 on a row moves that clip to the Recycle Bin through the node (removeGptSovitsClips, which also takes it out of the saved settings) and out of the window's voices. tts_voice_refs.js holds its rules without DOM: the voices read from the settings and the node's view (an emotion found from a file name is written only once changed), one main reference and any number of auxiliary ones per voice, the lines fixed here (lines; a voice's own text moves there), what keeps it from saving, the settings written back, and the order of the list. Auxiliary references and fixed lines need Anomalous_TTS interface 18 (auxiliary ones a v1 / v2 / v2Pro model). tts_setup_api.js holds the other calls (pretrained downloads, chunked upload, inspect, commit, discard) and the pure import-form rules (importKind, pickWeights, nameConflict, textFromFile, buildImportBody, importProblem, rowState / sectionState for the form's colours, setupSummary, pretrainedReminder, missingForLanguage, formatSize); no DOM. ui_tts_setup.js is the GPT-SoVITS settings dialog, opened from the sidebar footer (setupAttention gives that entry its dot). Missing pretrained files only get a dismissable dot when the studio's characters need them (dismissed ids in localStorage; a newly needed file brings it back); missing packages get a red one. Inside: a status chip by the title (ready, files to download, packages missing), then tabs: the tones, the tones for speaking another language, the base files (pretrained files and package sources, packages; a dot when they need the user, and the dialog opens there), where things are (the storage place and other places with characters, shown, not changed, and the settings file where folders are changed) and the version. It polls the status only while a download runs and it is open. ui_tts_import.js is the import window. It first asks what the user has (mode: single = one card led by its checklist, batch = a drop area then one card per draft, one unfolded at a time, add = files for an existing character, also opened straight from a card's "Add files"), and runs a spotlight tour once per screen ("?" replays it). It owns the drafts (characters being built; target = files added to an existing one), the unassigned tray, the characters waiting for the next batch (a large add opens one batch; the next opens on request or once the batch is imported), every file row (in exactly one draft's rows; a row keeps its own name in original and gets a clash-free name in a draft, sent to the node as the file's name), a debounced inspect per draft, and imports the ready drafts one after another (each commit on its own, without the rows leftOut names; closing discards uncommitted uploads). draw() rebuilds the cards on structural changes, refresh() only repaints status, so typing never loses focus. ui_tts_import_uploads.js sends browser files in chunks, three at a time, once they are in a draft (tray files wait); ui_tts_import_player.js plays one clip at a time for comparing (from memory). tts_import_groups.js holds the pure rules: which folders are never taken (skipFolder / isPackage: Python environments and base models anywhere, a package's program and training folders only inside a package, never the chosen folder), which draft a file goes to (groupFiles: a folder with one character's weights and clips is that character; other weights by stem; other files follow the character folder, the weights in their nearest folder, then folder names or file-name prefixes; unclaimed .list files go to every character), how an add splits into groups and batches (planGroups, splitBatch), new names for files that would clash inside a character (clashFreeNames), which files are left out (leftOut: clips outside 3–10 s and their line files), where a draft stands, and its checklist (the next step first). ui_tts_import_sources.js brings files in: the browser's dialogs and drops, all uploaded; every source gives folders starting with the chosen one, says which folders were left out, and confirms a very large upload. ui_tts_import_draft.js draws a draft's card (name in the header, steps left, the checklist with the next step's button and the chosen weights, one line per clip with its owner picker, the first clips with "show all", left-out files folded, line files, language) and the unassigned card (one folded line per folder when large), and builds each row's elements once, so they survive redraws and moves; ui_tts_import_screens.js holds the fixed screens (the window's frame, the toolbar over the cards, the first question, the batch drop area, the "add more" menu) and the tour steps. ui_tts_file_drop.js reads OS drops (walking dropped folders, only files an import can use, up to 5000) for the studio, the sidebar and the workbench, and binds the import window's own drop.

• audio_node_targets.js is the single table of canvas nodes the audio studio writes into (the character widget and the script widget of AnomalousTTS_CharacterSpeech). planVoiceDrop decides every character drop and names the reason for each refusal; unlisted nodes are refused, never matched by widget name. Supporting a node means adding one entry plus a test.

• The rail's Voices entry has two views, switched by ui_voice_tabs.js at the top of each and sharing the character list: Characters (shell page voices) and Voice-over (shell page script; ui_shell_nav.js keeps the rail on Voices and reopens the view used last). ui_audio_studio.js owns the Characters view: the character cards, preview playback, tag copying, dragging a card header onto a node through the shared bindMaterialDrag with targetHint/rejectHint telling the user what releasing does, and each card's "Voice-over" button (owner.openScript(group)). ui_script_page.js owns the Voice-over view: it loads the characters and mounts the script director, or shows the install steps or the way to import one when there is nothing to voice yet. A character picked in the list speaks there; the audio gallery's "voice it again" opens a file's lines with its character (owner.openScript(null, { speech, subfolder })). audio_script.js holds the pure script rules: splitting, bundling (buildScriptPackage, with [take:N] for retakes), combo value matching, and buildTtsPrompt (a GPT-SoVITS script as a ComfyUI API prompt saving to output/audio/<character>/). ui_script_director.js owns the script director, the Voice-over view's body: the lines, each read by its character (the one picked in the list on the left at first; the node's own character is the first line's), and a bundle ([name] where the speaker changes, a line's own [lang:…][speed:…][preset:…]) that is generated in the view, or, under "Into your own workflow" (ui_script_workflow.js), pushed to the selected/only target node, dragged onto one (writing the character and script widgets together, one Ctrl+Z step) or copied. The page feeds it the voice groups after each fetch. ui_script_cards.js draws the line cards: a click picks (ui_script_cast.js: Ctrl / Shift, the characters' colours), a double-click or ✎ edits the text in place, the name opens a menu of characters, emotion chips per the line's character, a tag when the line is set for itself, buttons on hover. The left side only picks; the side panel follows it (ui_script_tune.js) in three layers for this script, under a path (Whole script › character › line): nothing picked, the whole script (and each character in it); a character clicked in the list (castScriptCharacter), that character in this script; picked lines, who reads them and how. Each layer has the same rows (speed, tone, language) with where each value comes from; lasting settings are links at the foot. script_tune.js holds the rules without DOM: the layers (line over character over whole script over the character's usual values), each holding only the fields set on it, and the tags Anomalous_TTS interface 17 reads (only where a line differs from what the node gives by itself; the whole script's values go into the node's inputs). Every script is a draft in the drafts box (ui_script_drafts.js): one file in ComfyUI's user folder (user/<user>/anomalous_model_browser/voice_over_drafts.json, through ComfyUI's /userdata API), saved half a second after a change, read again and joined before each write so two tabs do not undo each other; a bar over the script names the open draft and leads to New, the box (cards: open, rename, copy, delete) and Close; deleted drafts stay in Recently deleted for 30 days. script_drafts.js holds its rules without DOM or storage (the shapes, the merge, titles, when a draft changed). A reload opens the draft that was open; the one draft the earlier version kept in localStorage moves in once. It puts the cards on one side and generating on the other: beside them once the page is wide, below them when it is narrow (docked browser); on a wide page ui_split_bar.js is the divider between them (dragged, remembered). A card is one row (number, text, buttons); "Into your own workflow" is folded. ui_script_run.js is the director's "Generate" section (the bar with the result and a way to the audio gallery; each character's values in this script, starting from its saved defaults and Auto, which it draws through ui_script_tune.js; the modes in the same switch measured against Auto (compact: scale and numbers folded) and heard on a line from the panel or the ▶ on its card (the takes heard stay on the side to compare), a preset's numbers changed there saved into the preset; links to the presets and to the character's generation settings; a node older than interface 17 reads the whole script as the first line's character reads, through its inputs): it runs the script without the canvas, plays the result, retakes the whole script (new seed) or one line ([take:N], the node caches the rest), and saves a character's language and speed to its defaults (keeping the rest of them) (only values that differ from the node's own defaults, which it reads from /object_info; needs Anomalous_TTS interface 11). ui_tts_pronunciation.js edits a GPT-SoVITS character's pronunciation table (the node's replace setting) from its card; each row can be heard as it reads now and as replaced, through a Preview Audio run, and saving keeps every other settings field. audio_tts_run.js queues one API prompt with this page's client id and follows it (websocket status, /history result, cancel = queue delete or targeted /interrupt); it never touches the canvas.

• In the audio domain the header ! opens AUDIO_USAGE_GUIDE (a how-to, see docs/guides/audio-studio.md) instead of the visual update guide.

• ui_audio_sidebar.js owns the audio navigation and the active audio filter (on Voice-over it is the cast: narrower, characters with their colours only, a click gives the picked lines to one and never leaves the page): characters grouped by language, groups folded in localStorage, a character unfolds into its clips (a click plays the clip through its studio row, switching the studio to that character when needed), a search box from six characters on, a red dot for characters that need a look, the GPT-SoVITS settings entry at the bottom and file drops on a character. Canvas drags go through audio_voice_drag.js, shared with the studio cards.

• ui_audio_gallery.js owns the generated-audio history (output folder): playback, seeking, search, paging, download and deletion, showing the speech/voice/seed recorded in each file, plus a section for unsaved temp previews that can be copied into output/audio/.

• ui_sidebar.js assembles the browser window (rail, list column, header, page panels; remote_view.js adds the header's "view only" chip when opened from another device; headerTools is a page's own slot in the header, shown on that page: the AI page's side switch) and puts the model folder column in the list column (ui_folder_list.js: the folders of the type the chips show, counts with subfolders, 📂 to open one in Explorer). ui_shell_rail.js owns the left icon rail: one entry per page, the tool slots and the settings slot. ui_shell_nav.js owns page navigation (goTo): the domain each page needs, which pages have a list and whether it is open (remembered per page; closed and overlaying below 760 px), the header's page title, and the page reopened next time. ui_home.js owns the home page (task cards, first steps). ui_shell_frame.js owns dragging, resizing and keeping the floating window on screen, and the full-window button (double-click on the header too); ui_scan_watch.js polls scan status for the rail's scan button, the progress panel and the model reload afterwards. The activity log (docs/decisions AD-018): api/activity_log.py keeps the entries (newest first, bounded, in the ComfyUI user folder), records this plugin's and Anomalous_TTS's successful write requests in a middleware, and serves /anomalous/activity (a handler may attach what it changed, request[ACTIVITY_DETAIL]; scans record themselves when they end); activity_canvas.js records canvas changes by comparing a snapshot taken when the user presses inside Anomalous with the canvas when they next press or type outside it (activity_diff.js holds the pure snapshot and difference); activity_log.js is the client and the words for each entry; ui_activity.js renders the activity page and the home page's recent list; canvas_undo.js keeps what each canvas entry did, in full, while the page stays open, and undoes an entry from the log while nothing has changed it since (entries that removed nodes or rewired existing ones are never offered).

• canvas_menu.js is AMB's part of the canvas's right-click menus (the extension's getNodeMenuItems and getCanvasMenuItems, browser_entry.js): for a node, Open in AMB (showForNode: the page opening with it selected shows; its saved values on Current node), change its model by picture (_openGalleryReplacer), insert a LoRA before / after, the model's pictures and details (/anomalous/find_model, openModelDetail), save its values or the picked nodes as a combo, each only where it applies; for the empty canvas, AMB's pages. canvas_menu_settings.js keeps which entries are on, their order and whether they sit in one "AMB" submenu or right in the menu (localStorage, no DOM); ui_canvas_menu_settings.js is its Settings -> Canvas group (two placement cards drawing a small menu each, a preview line per list). ui_quick_search.js is the canvas's quick search (Alt+B, the command Anomalous.ModelBrowser.QuickSearch, or the empty canvas's menu): a bar that finds combos, models and saved prompts as you type and puts the chosen one where the pointer was (a combo through sendNotebookToCanvas, a model through applyModelToCanvas, both following the pointer; a prompt as a new prompt node, prompt_card_drag.js addPromptNode); it takes every key while open. quick_search_data.js reads its lists (kept a minute) and matches without DOM; MODEL_LOADERS there is also the loader node applyModelToCanvas uses for each type. ui_settings_hub.js owns the display preferences (view mode, scale, atmosphere, window layout) and their application, the gear and language redraws; ui_settings_page.js is the settings page the gear opens (a tool page with Back), in tabs: Look (look and language, model cards and memory with the card image cache, opening mode and window), Models (folders, where downloads and imports go, where the side files go through sidecar_layout.js), Workflows (fingerprints), Node packs (those not used lately, ui_pack_usage.js), Canvas (the right-click menus, ui_canvas_menu_settings.js), Prompts (translation), Backup (ui_backup.js), Help; ui_feedback_dialog.js is the feedback window (Home and the settings page open it): one text box, then feedback.js opens a GitHub issue with it in the browser's language, the environment folded at the end when attached (versions and hardware only, never a path or ComfyUI's command line), or copies the environment, and openRepoPage() opens the project page for a Star (on a press only; nothing is fetched); ui_rail_tools.js owns the rail's tool buttons (scan, doctor, current node); ui_browser_navigation.js owns shared panel hiding/cleanup and workspace return, including Esc on the workspace panel (nbPanel, below the header and right of the rail; the list column steps aside while it is open). ui_scan_page.js is the scan page (a tool page like the doctor), quieter the further down: the scan card (a band of covers with an empty frame per model not scanned yet, what is left, the scan button with "pick models to scan" beside it, online or offline, what the scan will do in one sentence), the models' state as a bar and chips (the components on a chip of their own), what needs a look, the settings (ui_scan_settings.js: the scan options as tiles, the two that change files folded under "more"), the last scan in one line; icons from scan_icons.js. Each state chip, the components and the last scan open a list page from ui_scan_lists.js (not scanned, unmatched, other formats, the last scan's models) with Back, a button for the whole list (scan these / look them up again) and rows that open a model, whose Back returns to the list, or scan it; scan_results.js holds the words for scan results, shared with the activity page; net_failure.js the words for why Civitai could not be reached (net_proxy.py's codes), for the scan results and Settings → Network's connection test. ui_scan_picker.js is the scan page's model picker: every model a scan reads, by folder, state (not scanned, not found, damaged, found, don't scan) and search, as a list or covers; the page keeps its picks as items (none: the button scans everything). scan_runner.js starts and follows scans (every folder, picked or listed models, or one model from its card), shows the result and refreshes node drop-downs, hashes and the grid afterwards; before an online scan scan_connection.js checks whether Civitai can be reached and, when not, asks: scan from the files, set a proxy, or not now; folder visibility/order lives in ui_folder_manager.js. scan_progress.js owns the scan progress panel (updateScanProgress / finishScanProgress / failScanProgress): inside the scan page while it is shown (setScanProgressHost), floating at the bottom right otherwise. shortcut_controls.js owns the open-browser and Prompt Studio keyboard shortcuts (the second keeps its old "materials" ids), their fallback when ComfyUI's keybinding does not fire, and the settings control that opens ComfyUI's keybinding editor.

• ui_model_sources.js renders the Models page's Sources view (the last type chip): where each model is downloaded, for the open workflow or every model, with each link editable and saved in place; model_source_links.js owns its data and actions (collecting the workflow's models, resolving them here, saving a link to the model's information and the workflow, the canvas note and the clipboard list).

• ui_gallery_card.js builds one output's gallery card (viewer, workbench, cover pick, drag, star, compare, delete; a video's card plays in the viewer and has no workbench, star or menu); gallery_filter.js holds what the gallery lists (All / Pictures / Videos and the formats hidden in Settings, per browser) and ui_gallery_filter.js draws both controls; gallery_card_menu.js is its right-click menu (insert as a Load Image node reading the output file, parameters), drawn by action_menu.js (a small menu at the pointer or under a button); ui_param_compare.js compares parameters: a card's ⇄ picks an image, a second image's ⇄ or the canvas completes the pair (the image workbench's ⇄ takes the canvas; the Gallery's and Activity's ⇄ Canvas vs. newest picture pair the newest output PNG with it), and its window says whether both are the same node structure and lists each value that differs (prompts by the tags only one side has, seeds apart), writing ticked image values onto the canvas as one Ctrl+Z step with Undo; param_compare.js reads and compares the two sides without DOM. key_params.js keeps the starred key parameters (node type + widget name, a hidden ComfyUI setting); the window shows them first. ui_param_set_keys.js puts parameter sets in view: a recipe card's ▤ N chip (first in its specs line) (GET /anomalous/parameters/signatures; sets equal to the recipe not counted) opens its Parameters tab, and each set there shows its key values, how many values differ from the recipe, and ⇄. ui_keep_menu.js is the star's keep menu (also the workbench's Keep): the whole workflow, the combo or the prompts, each saying where it goes, opening what was kept already or removing it (to the Recycle Bin through the recipe, notebook or material delete route); image_keep.js does the keeping (an image as a combo, named by comboTitle — first LoRA or main model · two telling tags — and renamed by renameCombo; its prompts as a saved prompt, reading what was kept) without DOM. A new combo's toast is ui_kept_toast.js (the image's thumbnail, the name in a box to rename it on the spot, Open). An image becomes a node-structure combo: sampler_inputs.js (no DOM) picks the nodes upstream of its samplers' model / positive / negative / conditioning inputs (not through images, latents or masks), and image_keep_nodes.js saves them with captureStructure, every value as the image had it, models renamed to where they are on this computer; a workflow with no sampler gives the older main model + LoRAs + prompt combo.

• ui_combos.js renders the Combos page's list (搭配: a main model, LoRAs and a prompt, formerly Prompt Notes): search, ? (what a combo is), New, and a card per combo with its model's cover (one kept from an output image shows that image, the model's cover as a badge) and Put on canvas; a card opens the combo's editor, and dragged onto the canvas (material_drag.js) becomes a new group of nodes where it is dropped. Combos keep the notes' files. A combo can instead hold a node structure (data.kind === 'nodes'): combo_structure.js captures the canvas's picked nodes (subgraphs aside) with the links between them and puts them back (other boxes stored by name and restored untouched, slots = model drop-downs and text boxes, the folder a drop-down lists read from ComfyUI's own /models lists, inputs fed from unpicked nodes noted to wire); combo_slots.js holds its rules that need no canvas; ui_combo_structure.js is the save dialog, the slot editor, the slot model picker and "New"; ui_translation_peek.js is the read-only translation panel beside its prompts. lora_nodes.js knows the LoRA nodes a default combo puts its LoRAs in (ComfyUI's chain, rgthree's Power Lora Loader, Easy-Use's LoRA stack, the third-party ones only when installed) and a Power Lora Loader's rows (for structures, and as drop-down-like boxes for Model Check); ui_lora_node_choice.js is the default combo editor's choice among them.

• detached_graph.js lays a workflow on a graph of its own, off the canvas, under an id of its own: ComfyUI keeps widget values by graph id, so a copy under the canvas's id would write its values onto the canvas.

• recipe_save.js saves Workflow Recipes for the canvas save and for an output image's workflow (the gallery's keep menu, moving whole workflows kept as materials), laying an image's workflow on a canvas of its own to summarise it.

• ui_apply_receipt.js is the receipt of values written to a node from a panel (Current node's parameters) with its Undo. node_material_actions.js owns prompt envelope extraction (extractMaterialPromptEnvelope) and the node writes shared by those panels and prompt drops.

• ui_update_guide.js and update_guide_data.js own the non-intrusive update guide modal (accessible via header button #anomalous-update-notice-btn, the Help modal and Home's "What's new"; the current guide's ID and steps live in update_guide_data.js) with full bilingual localization. ui_spotlight_tour.js provides the interactive spotlight mask tour (startSpotlightTour), gliding smooth focal box highlights across the rail's pages and tools with directional tooltip cards and keyboard navigation; steps whose target is not on screen are skipped. The browser tour goes in the order the pages are used (rail, Gallery and what its ☆ keeps, Workflows, Combos, Prompts, then the tools), with its text in locales.js. Other views pass their own steps (text from locale keys) and an optional onClose; the GPT-SoVITS import window does.

• tool_registry.js holds the tool icons shared by the rail and Home.

• The rail's tool slots (ui_rail_tools.js, fixed) hold scan, doctor and current node; settings sits at the rail's bottom. The rail's Prompts entry is Prompt Studio's page (ui_prompt_composer.js); its "Beside the canvas" moves the studio into a drawer by the canvas with the browser folded away, and "Back to the window" returns it. There is no toolbox: the other tools open from their pages (share and import on Workflows, Model Sources as a view of Models, opened from the doctor too, translation in Current node).

• ui_share.js is share and import (the Workflows page's ⇅): the canvas workflow as a share code in Chinese characters or letters, and one place to paste a code or workflow JSON or drop a workflow file, an image, a recipe package or a backup .zip. ui_recipe_package.js exports a recipe package from a card or the detail's More menu and takes one in as a new card. share_code.js is the AMB2 code (lean workflow checked by rebuilding it, else the whole workflow; AMB0/AMB1 still open); details in docs/architecture/frontend.md.

• ui_model_types.js owns the models page's type chips (one per models folder, with its count) and owner.modelScope, what the grid lists: a whole type, or one list folder shown as a crumb. The grid's cards set currentType/PathIdx/Subfolder to their own model's folder (focusModel), which the editor, the scanner and "add to canvas" read. Its Import chip and files dropped on the grid open ui_model_import.js, the import window (one card per file: type, base model, where it goes, warnings, progress); model_import.js reads each file's header and asks, moves or uploads it, then scans the new files. The page's tabs (All models, Tidy with how many things it found, Sources) head the grid; under All models the type chips and the base model chips (owner.modelBase; model_bases.js names each model's family from its scanned base model or its header's guess). The Tidy tab is ui_model_tidy.js (owner.modelView === 'tidy'): cards with covers in two steps — models in a folder whose loader cannot read them (from → to, Move there), identical copies (pick the one to keep, recycle the rest); model_placement.js does its requests and keeps the tab's count. Under the two steps ui_model_usage.js lists the models not used for 30 / 90 days or never (picked ones go to the Recycle Bin) and leads to Settings → Node packs, where ui_pack_usage.js lists the node packs: each opens ComfyUI Manager's node list searched for it (Manager 3; its name is copied for the rest); packs that also add to the page are set apart, those marked "I still use it" listed last. usage_view.js is what both share: the check, kept in owner.modelUsage, and each page's head (groups, what the run record vouches for). usage_notes.js posts what each workflow ComfyUI opens holds (its own loadGraphData wrapper, once per content and page load) and the open tabs just before a check, so opening a workflow or putting a node on the canvas counts as use. ui_model_search.js is the models search in the header (shown on the models page through the shell's data-page): the grid lists the models of its type matching every word (owner.modelQuery).

• model_source.js shows where a model's information came from: the card badge (marked only when inferred from the file, "推断", or not scanned yet), the details' source line with the fields the user set, its links (source link, Civitai) and, for a model Civitai does not know, the note on what was read from the file.

• ui_grid.js and model-detail modules own model presentation: ui_grid.js manages chunked card rendering, card placeholder ergonomics (eliminating misleading unclickable text in favor of pure centered icon and status), card action buttons (one-click canvas addition with plus icon, model metadata editor, direct precision scanner without wizard modal popups) with absolute positioning cascades immune to tooltip target conflicts, vibrant hover affordance, safe docked sidebar preservation upon node addition, and multi-type node dispatch; ui_detail.js coordinates detail display (cover column, then the head from model_detail_head.js: back crumb, name, source line, Add node / Edit / Folder / Outputs; the foot with the path, Copy and Delete, and Show in folder, in model_location.js), ui_model_editor.js owns metadata editing (cover, name, source link, notes; styles styles/31-model-info.css), and model_widget_path.js puts a model path into a loader's widget. ui_gallery.js (cards in ui_gallery_card.js, filters in gallery_filter.js / ui_gallery_filter.js) and ui_gallery_detail.js own generated-output browsing and workbench lifecycle, with stage interaction in ui_image_stage.js and metadata tabs in ui_image_inspector.js.

• ui_recipes.js / ui_recipe_detail.js and ui_notebooks.js own their respective workspace surfaces and persistence flows. ui_recipes.js hands the Workflows page (its catalog) the recipe services (save, edit, fetch) and opens a recipe by name. ui_notebooks.js owns the Combos workspace (filling the page; its list or one combo's editor, with Back to the list) and combo persistence; ui_combo_hero.js is the head of a combo's editor (its picture: the image it was kept from with See the picture, else its model's cover; the name with Rename; chips of what it holds; Put on canvas and More; no Save, every change saves itself), also over node-structure combos; ui_combo_models.js is the editor's models (the base model, the chosen main model and LoRAs as rows, Change / Add opening a grid of compatible models read only then); ui_notebook_editor.js puts them together with the prompt and owns unfolded card editing (modularized into single-responsibility sub-functions adhering to the 50-line rule: sticky top action toolbar with floating More popover dropdown and timed two-step delete safety guard, unfolded companion models card with unconstrained multi-column tile flow eliminating nested gallery scrollbars, prompt composer with dynamic field-sizing and compact inline find & replace toolbar, and unified dark slim scrollbar ergonomics with complete bilingual dictionary coverage in locales.js), and notebook_canvas.js puts a combo on the canvas as a new wired group of nodes (following the pointer, or at a dropped card's position; Esc takes a following group off again); it never changes nodes already there. Combos are a rail page. ui_recipe_detail.js is a workflow's details, built around its values (styles styles/29-workflow-detail.css): a bar (Back, the name, the models' state, Open, ⋯ edit and export), then ui_recipe_sets.js's left column (the workflow's own values, the saved sets unlike them with their key values, Save the canvas, New; then all pictures and versions) and the chosen view on the right. ui_recipe_set_view.js is one set: Apply to canvas, ⇄ (with the workflow's own or the canvas), ⋯ (copy as a new set, rename, delete); the cover, notes and tags for the workflow's own (ui_recipe_info.js, which also holds the name and the models' state); the workflow's focus values (重点参数: recipe_focus.js keeps them in the recipe's params and tells comparisons which values they are, ui_recipe_focus.js draws them with their notes and the ☆ on each node value); the main values; the prompts; the pictures made with these values; the models (the fold says whether all are here) and every node's values, folded, each opening as the viewer last left it (this browser's storage); a tip while the workflow has no set, and one pointing at ⇄ on a set until it is used. Narrow (docked) details turn the left column into one row of pills (a container query). A new set is named after the workflow with the next number (nextSetName). ui_recipe_parameters.js holds what the views share: prompt roles (automatic or set by hand) and their boxes, every node's values (unnamed ones labelled by their node type's widgets, comfyWidgetLabels), the new set's editor. prompt_boxes.js is the one place that finds prompt boxes on the live canvas: a multiline STRING input by the node's ComfyUI definition, whatever it is called; its role is the box's own name (positive / negative) or else the wiring (outputs followed to an input named positive / negative). It also plans which box takes which text and finds a box's opposite-role partner on the same sampler. prompt_drop.js is the prompt drag on the canvas: boxes outlined by role, the box under the pointer as the target, the text a release writes previewed over it (and its partner), and a hint saying what release writes where. node_material_actions.js extracts prompt envelopes without model file paths and writes them (fillPrompt); text never crosses roles unless the user picked the box; writes are one undo step. Within recipe detail, ui_recipe_versions.js owns history comparison/restore, ui_recipe_gallery.js owns the picture grid (thumbnails, 参数, ⇄ to compare) and the all-pictures view, ui_recipe_models.js owns the overview's model list (preview, presence under the saved name, note, download page; finding missing models is Model Check's) and the recipe cover, ui_recipe_metadata.js owns inline persistence, and ui_recipe_detail_dom.js owns the DOM/copy helpers shared by detail subviews. recipe_identity.js derives model references from native loaders plus a table of verified all-in-one loader layouts (ALL_IN_ONE_LOADER_SPECS) and two stack nodes by their rows (rgthree's Power Lora Loader, Easy-Use's LoRA stack; nodeModelValues), all mirrored in api/recipe_schema.py; other third-party widgets stay parameters. References are keyed by (node_id, widget_index, category, saved_value). recipe_parser.js summarizes models, LoRAs, samplers and prompts (linked prompt nodes before embedded loader prompts) and keeps the summary in step with widget edits using the same node rules; which LoRAs a node loads is recipe_loras.js, and reading a node's boxes recipe_widgets.js. ui_recipe_catalog.js is the Workflows page: one bar (search, the filter menu with kind and tag, the count, grid or list, share and import, save the canvas), the list, the empty page's three-step guide (renderRecipeEmptyGuide) and the catalog-wide model readiness check (resolveCatalogRecipeReadiness). ui_recipe_cards.js is one card: the cover with the models' state (getRecipeReadiness: a dot, or words when some are missing) and 功能模块 for a partial workflow, the name, a line of steps, sampler, LoRAs and size, then its model; Open and ⋯ (edit, export, delete) as two small buttons in the cover's corner on hover; a press anywhere else opens the details, a drag opens it on the canvas. Opening a workflow on the canvas hides the browser and leaves the Workflows list in place. Its styles are styles/28-workflows.css. ui_popup_menu.js is the small menu under a button they share, ui_recipe_save_dialog.js is saving the canvas as a workflow (the cover chosen on the left from the canvas, the current cover or recent pictures as thumbnails; name, tags, notes and the fingerprint choice on the right; the name defaults to the canvas's saved workflow name), ui_recipe_dialogs.js the edit dialog, and ui_recipe_media.js owns shared cover helpers. Detail sessions synchronize detected model availability back to owner.recipeRecords via syncRecipeReferencesToCatalog.

• ui_prompt_composer.js owns the standalone Prompt Studio drawer (dock side, width, Esc); ui_prompt_workbench.js fills it: the top bar (tags or text view, the meanings' language) and saving a box as a card. ui_prompt_target.js decides what is edited, the prompt boxes of the prompt node last selected on the canvas or a positive / negative draft, follows the selection and the boxes' text, and owns the studio's Undo; ui_prompt_box_editor.js is one box as tags (select, weight, edit, remove, reorder, drop, type, translate to English) or text. prompt_tags.js splits and joins a prompt's tags keeping their separators, and prompt_gloss.js looks up and keeps the tags' meanings in the picked language. ui_prompt_source_deck.js owns the card list (three built-in cards and the saved prompts, drawn as notebook pages: the role on the spine, the first tags, a ribbon on the one open as the reference), search, new-card form, library sync and renaming / deleting a saved prompt; prompt_material_source.js reads saved prompts as cards and saves one; ui_prompt_reference.js is the reference column a clicked card opens in, between the cards and the boxes (its tags taken one by one or all, ticks on those the box has; it widens the drawer while open, and takes the cards' place where three columns do not fit); ui_prompt_card_popover.js owns the card preview (hover corridor, pin, Copy / Add / Rename / Delete); prompt_card_drag.js lets a card or a box be dragged out of the drawer onto a canvas prompt box or empty canvas (through material_drag.js and prompt_drop.js), passing through inside the drawer so the boxes still take it. prompt_composition.js holds the starter cards, composes a saved plan's text and names and sorts prompts.

• ui_node_prompts.js is the current-node panel's prompt boxes: role and text, with Edit in Prompt Studio. The studio uses ui_lifecycle.js for global listeners, request cancellation and resize cleanup. Translation requests go through translation_service.js.

• ui_dialog.js owns the plugin's own alert / confirm / prompt dialogs (anomalousAlert, anomalousConfirm, anomalousPrompt), used instead of the browser's native ones; an alert can carry a line to copy (copy), and copyText also works on a page served over plain http. ui_prompt_toast.js is the short toast (optionally with an action, such as Undo after a drop) shared across the plugin.

• canvas_history.js asks ComfyUI's Ctrl+Z history for a step after each canvas write Anomalous makes (applied values, drops, created or inserted nodes, recipes): ComfyUI takes steps on mouse-up and key-up, and a drag-and-drop ends in neither.

• model_policies.js mirrors model_policies.py for the frontend: which folder types a loader widget holds, which are never physically renamed, and which need a workflow-carried hash before Model Check recovers them.

• ui_dom.js provides small DOM/JSON helpers; material_inspector.js owns the image workbench's metadata and node-parameter rendering; png_metadata.js reads the workflow a PNG's text chunks carry, in the browser (the gallery detail's fallback).

• ui_first_run.js is Home's first-run setup while nothing is scanned (check that Civitai answers through api/network_check.py, the optional key, a scan of every model, the tour); a card, never a popup, hidden per browser.

• model_check.js checks the open workflow's models (drop-downs naming model files, and switched-on Power Lora Loader rows through lora_nodes.js) against this computer (Model Check's verdicts, no DOM; the feature was called Model Doctor, and code and CSS still say "doctor") and puts a found file into its node; ui_doctor.js is the Model Check page and ui_doctor_banner.js the bar over the canvas when an opened workflow misses models (it also owns the check-on-open preference that Settings → Workflows and the bar's "Don't show again" set). model_download.js finds a missing model's source, decides where its file goes (the download settings, {base} = its base model's folder), follows the downloads and puts each finished file into its nodes (the placement rules are download_places.js, without imports so they are tested alone); ui_model_download.js is the page's Download buttons, progress and the dialog that shows and changes where each file goes. ui_node_assistant.js owns the current-node panel (model actions, LoRA insertion, model cards and history), ui_node_model_picker.js owns native combo replacement, ui_node_parameters.js renders the panel's parameters section (each saved set as a card with the picture made with it and where it came from, values as bars or old → new, or all sets side by side), and node_parameter_sets.js merges the node type's saved values (material files and recipe parameter sets, each source with its origin) and works out what each would change on the node, keeping seeds, model files and missing choices, and asks /anomalous/parameter_pictures for the recent pictures made with the sets' values; saved values (not a recipe's) are deleted there. It also keeps, in this browser's storage (anomalous_applied_sets, the newest 100 by workflow and node), which set was last put into a node, for the panel's line on where the values came from. model_picker.js, node_material_actions.js, and graph_splice.js own the remaining explicit graph changes.

• A model's download link lives in its user layer (source_url in <model>.anomalous.json, via /anomalous/update_metadata), the same field the model editor edits; for the open workflow's models it is also kept in workflow.extra.anomalous_model_sources, so shared workflows carry it. Workflow models are located here through /anomalous/resolve_paths_to_previews.

• locales.js is the shared runtime string catalog. Existing inline bilingual UI strings remain migration debt; new strings belong in the catalog.

• styles.css is the ordered import manifest for web/styles/*.css, which own presentation and theme overrides. Color values, dimensions and visual design descriptions are not duplicated as architectural contracts.

Cross-system invariants

These rules are intentionally summarized here and specified in the linked topic documents.

1. Identity is provenance, not naming. Model Check may use a cryptographic hash, exact byte size under the allowed category policy, and target category. Paths, filenames, display names, previews, and fuzzy similarity are never identity evidence.
2. Filesystem input is untrusted. Backend request paths must pass the shared containment and filename helpers. Checking only for .. is insufficient on Windows and in the presence of alternate separators, UNC paths, or symlinks.
3. User files are changed transactionally and conservatively. Recipe writes, imports, graph mutations, and sidecar operations validate before mutation and either complete coherently or restore the prior state.
4. The event loop stays responsive. Recursive walks, hashing, metadata parsing, and other potentially large disk operations run off the aiohttp event loop. UI rendering and media loading are bounded and cancellable.
5. Host state is preserved. Browser panels are mutually exclusive, Workspace/model-detail transitions are recoverable, and graph edits use ComfyUI's change/callback contracts.
6. Runtime strings are localized safely. User-visible copy comes from locales.js; dynamic values stay outside dictionaries and enter the DOM as text. Only allowlisted rich content goes through safe_dom.js.
7. Optional integrations fail locally. Missing graph APIs, metadata, network availability, or an optional resolver may disable that capability but must not make the main extension disappear.
8. Presentation data is not authority. Covers, thumbnails, summaries, cached names, and workflow fingerprints never replace the authoritative serialized workflow or model provenance record.

Data and compatibility boundaries

• Runtime settings and newly saved API keys live in api/config.json. scraper.py may read the legacy root config.json only as a compatibility fallback. API keys are not stored in browser localStorage.
• Recipes, Parameter Notebooks, and Material Library records/assets are user data outside the extension directory. They are never bundled with or silently migrated into the plugin source.
• The extension may integrate with Civitai and optional translation services only through explicit product behavior. External content and dependencies keep their own terms.
• Project code and documentation use the MIT license. TRADEMARKS.md separately defines the project-name and official-branding boundary.
• Internal property names and established routes may remain stable when a user-facing surface is renamed. Do not churn compatibility contracts merely to match presentation wording.

Change and snapshot protocol

The per-commit requirements (which document to update, the structure check, verification, snapshots and pushing) live in section 0 of AGENTS.md and are not repeated here. Update this entry point only when the system map, cross-system invariants, or reading map change; everything else goes in the narrowest topic document.

Decision records explain enduring choices; they are not a chronological diary. Git history is the authoritative record of implementation changes. Planning-only documents must be clearly labeled as proposals and must not describe unshipped behavior as current architecture.