comfyui-mcp 0.51.51 → 0.51.52

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7978,7 +7978,24 @@ export function buildPanelToolDefs() {
7978
7978
  // signal rather than an inference.
7979
7979
  const reply = parseToolResultJson(loaded);
7980
7980
  const remintedInstance = reply?.loaded === true && reply?.format === "api";
7981
- return remintedInstance ? appendNote(loaded, noteStaleFenceAfterLoad()) : loaded;
7981
+ if (!remintedInstance)
7982
+ return loaded;
7983
+ // #1478 — ADOPT the instance this load just proved, rather than warning about it.
7984
+ //
7985
+ // The note below is the right answer only while we cannot know the new uuid. Panel
7986
+ // 0.14.39+ publishes `workflow_uuid` on this very reply
7987
+ // (comfyui-mcp-panel#1225), which is the same race-proof shape
7988
+ // `refreshFenceFromOwnReply` already trusts for workflow_save / workflow_save_as /
7989
+ // workflow_new (#1161): read from the command's OWN reply, never re-derived from
7990
+ // whatever is active now — a re-derivation rejected as a P1 here more than once,
7991
+ // because the active workflow can move during the await.
7992
+ //
7993
+ // It validates before adopting (canonical uuid or nothing), so a malformed or
7994
+ // absent field leaves the fence alone and falls through to the warning. That
7995
+ // matters: anyone on a panel below 0.14.39 still has the original bug, and
7996
+ // withdrawing the note for them would make it silent.
7997
+ const refreshed = refreshFenceFromOwnReply(ctx, loaded);
7998
+ return refreshed ? loaded : appendNote(loaded, noteStaleFenceAfterLoad());
7982
7999
  }
7983
8000
  catch (err) {
7984
8001
  return fail(err);