show_text_party can show stale stacked blocks when UI text keeps list payload

[iqdoctor]

Summary

show_text_party.notify() writes node["widgets_values"] = [text] directly.

In practice, this can leave stale stacked output in the Show Text UI after repeated runs / node recreation workflows.

Why this likely happens

• show_text_party is intentionally list-aware (INPUT_IS_LIST = True, OUTPUT_IS_LIST = (True,)), so text can be a list payload.
• The current code writes the incoming object directly into widgets_values without resetting state.
• Reusing mutable values here can keep stale visual content in the widget.

Expected behavior

Show Text should reflect only current execution output, while preserving list semantics (no forced scalar conversion).

Suggested fix

In show_text_party.notify():

1. clear previous widget content,
2. write a deep-copied current value.

This keeps list behavior intact and prevents stale content artifacts in UI.

(Reference context: Comfy list-processing semantics are explicitly documented for INPUT_IS_LIST / OUTPUT_IS_LIST in Comfy's node typing and docs links.)

[iqdoctor]

Update after additional production validation:

The initial fix (reset widget values before write) reduced stale UI state, but did not fully remove stacked output in all list/nested-list payload cases.

Final patch now also normalizes Show Text UI rendering to the latest item only:

• add _last_text_value(...) for list/nested-list inputs,
• write scalar latest value into widgets_values,
• return ui.text as a single latest string item,
• keep result unchanged to preserve list semantics for graph outputs.

PR updated: #233 (head includes follow-up commit ac9e71b).

[iqdoctor]

PR #233 narrowed to a focused one-commit fix based on final root cause (list UI payload handling). Branch was rewritten from main and now only changes tools/show_text.py.