Build a concrete ComfyUI pre-import checklist from a saved file

Keep two files with deliberately different roles

Use saved-valid.json as the supported saved-structure control and private-fields.json as the unknown-node/privacy exercise. Both are project-authored fixtures, not model packages or promised runnable graphs. The first has one saved KSampler entry and zero links; the second is a three-node API prompt with one fictional unknown implementation.

For a file received from someone else, retain the original download, its source URL or sender context, and any supplied version/license notes privately. If you received a PNG, extract the exact workflow and prompt occurrences first. A screenshot, a preview file or a missing field cannot supply a graph that was never stored.

• Download the saved-workflow control — One full saved KSampler node, no connections and an exact 18446744073709551615 numeric seed token. Passing the implemented structure checks is not a runnable-generation claim.
• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.
• Extract an actual stored graph first — Keep UI workflow and API prompt roles distinct; original downloads contain references rather than model files.

Run the same inspection checklist on each input

1. Step 1

   Record the representation and original

   Choose each JSON in the direct viewer. Record workflow-0.4 for saved-valid.json and api-prompt for private-fields.json, then preserve Download original JSON if you need an exact local copy. Browse node inputs and connections without running them. An unrecognized or malformed document stops this inventory path.

   Inspect the saved representation

2. Step 2

   Record static results with their limits

   Choose each file in the static checker. saved-valid.json is checked with one node, no connections and no diagnostics. private-fields.json has zero errors, one custom_definition_unchecked warning and one connection. Keep that warning visible; the validator does not check installed plugins, socket semantics or model availability.

   Check the implemented structural subset

3. Step 3

   Record resources and unanswered implementations

   In the viewer, inspect Model and resource references, Unresolved entries and Node types and compatibility questions. The private-fields fixture names one literal checkpoint path and has one unresolved custom node. Save its scoped reference list privately. Ask for the exact model file/version and the authoritative implementation/version for the unknown type; the tool does not scan your computer or create installation URLs.

4. Step 4

   Prepare only the information needed for help

   Generate the default support report for private-fields.json, review the complete preview and download it separately. Its three aliases, one dependency reference and one unresolved entry omit the original identity, model path and prompt by default. Add specific optional text only after reading the fresh preview.

   Preview a scoped support handoff

Keep a decision record instead of a safety badge

This record is the deliverable. A checked structure, known catalog name or hash does not establish that importing or executing an external graph is safe. The local tools do not provide an execution sandbox, install extensions, fetch model URLs or prove that a workflow will generate the pictured result.

Stop or ask when the input cannot answer the question

Unknown JSON shape, invalid UTF-8, duplicate identities, unsupported versions, subgraphs or a processing limit require an intact supported export or further manual investigation. An empty graph has no node inventory; it is not a successful reproduction. Connected/custom resource values remain unresolved rather than becoming a claim that no models are needed.

If two revisions are supplied, compare them under the saved-ID rules before deciding what changed. If they were renumbered, keep added/removed rows unmatched instead of inferring equivalence. Continue outside these tools only after you understand the source and the unresolved dependencies; nothing in this checklist executes the input.

• Compare two actual saved revisions — Exact values, connection changes and renumbering are explicit in the downloadable difference.

Sources and reproducible inputs

• Download the saved-workflow control — One full saved KSampler node, no connections and an exact 18446744073709551615 numeric seed token. Passing the implemented structure checks is not a runnable-generation claim.
• Download the fictional private-fields JSON — Self-authored three-node API prompt with a fictional person, model path, prompt, title and custom field. It is inspected locally and never executed.
• Official workflow 0.4 schema at fixed docs revision 7ca6a40804ef — Primary reference for saved node fields and six-element link tuples. The local validator implements a stated subset rather than full JSON Schema conformance.
• Official workflow 1.0 schema at the same fixed docs revision — A separate versioned format with state, saved nodes and object-form links. The local subset reports named-slot and subgraph coverage limits instead of certifying runtime compatibility.
• Official base-node definitions at fixed revision ce1e922d8623 — The site's reference catalog contains the 65 names in this revision's base NODE_CLASS_MAPPINGS. Core extras, frontend-only nodes, custom installations and later revisions are outside its scope.
• Official API prompt example at fixed core revision — Reference for named class_type/inputs and stored [node ID, output slot] connections. Only the literal example JSON was inspected; the Python and network code were not run.