- Images without an embedded API graph: the scan now asks recorded
history before skipping a file with no prompt metadata, and the monitor
gives a keyless unlinked image one history-only re-check when its run's
outputs are recorded (a seal notification from the outputs write; at
most 1000 waiting images, each for an hour).
- Run keys: an image is unkeyable when any positive node has no key, so a
two-pass graph is never linked through the other pass; links follow
ComfyUI's is_link exactly.
- A failed save marks the node's run key like an empty editor, so an
older entry of that key can't stand in for this run.
- A placeholder is the latest entry: the image stays unlinked without
falling through to history, the same rule as a popped placeholder.
- An index on execution_run_outputs(filename, subfolder, root_key,
path_style) for the history lookup, added by migration and accepted by
the output schema check (any other index is still refused).
- Repair tool: unlink removes only the link record and only while the
image is still linked to the prompt it was judged on; every run prints
what --apply does.
- Real-host case proves the re-run's PromptManager node was cached.
An LLM fed a PromptManagerPair's prepend_text while its text editor was
empty. The node refused to save (an empty positive raised and logged a
warning), and the image monitor then linked the image to a stale tracker
entry or to the newest prompt in the database.
- Nodes: an empty text editor saves and tracks nothing (prepend and
append text are never the stored prompt), logs at info, and marks the
node's run key empty so no earlier entry can be used for its images.
- Tracker entries carry a run key: a digest of the prompt node and its
whole upstream graph, the identity ComfyUI's cache uses. The monitor
computes the same key from the image's embedded graph and uses a
queued or snapshot entry only when the keys match (a snapshot also
needs a known run with one entry, so a batch's last item is never
applied to every image).
- The recency fallback is gone; anything uncertain stays unlinked and is
logged at info.
- Recorded execution history attributes a file when exactly one run
reported it, the file was written during that run, and the run's
positive contexts name one stored prompt. The monitor and the output
scan use it as their last certain source.
- The scan and pair ingestion treat a resolved pair with an empty stored
positive as unresolved instead of raising.
- tools/review_image_links.py reviews selected links by these rules;
dry run by default, --apply changes only named ids after a backup.
Closes#342
Vito Sansevero