comfyui-mcp 0.50.80 → 0.50.82

package/dist/orchestrator/ask-answer-journal.js

@@ -227,7 +227,7 @@ export class AskAnswerJournalImpl {
     /**
      * Which browser-tab INCARNATION currently holds a panel tab (#486).
      *
-     * A `wf:<hash>` tab id names a saved workflow, so it recurs: a second browser
+     * A `wf:` route tab id names a saved workflow, so it recurs: a second browser
      * tab opening that workflow takes the key over. Anything that holds or settles
      * per-tab state must therefore be scoped to (tab, incarnation) — otherwise the
      * newcomer reads, reports and ACKS the departed tab's bookkeeping, and the

package/dist/orchestrator/index.js

@@ -2256,7 +2256,7 @@ export async function runPanelOrchestrator() {
     // receipt for the ordinary path and must treat every answer as possibly lost;
     // with it, "the model read this" is a fact and only the genuinely unconfirmed
     // ones are held open (#486).
-    // #486 — a `wf:<hash>` tab id names a WORKFLOW, so a second browser tab can
+    // #486 — a `wf:` route tab id names a WORKFLOW, so a second browser tab can
     // take it over. The journal scopes every per-tab debt to whoever is actually
     // holding the key, so the newcomer can neither be told nor settle the
     // departed tab's owed disclosure.
@@ -2266,7 +2266,7 @@ export async function runPanelOrchestrator() {
     // warning is owed), so it needs a LIFECYCLE end instead: a tab leaving the
     // bridge's connection map surfaces whatever it is still owed and retires it.
     // Journal entries survive — a disconnect is usually a reload.
-    // #486 — a DIFFERENT browser tab taking over a recurring `wf:<hash>` key is a
+    // #486 — a DIFFERENT browser tab taking over a recurring `wf:` route key is a
     // CONVERSATION BOUNDARY, exactly like New chat or a provider switch: the
     // newcomer never asked the previous occupant's questions, so its answers must
     // stop being recoverable and stop being pushed. closeAsks downgrades and

package/dist/orchestrator/panel-tools.js

@@ -7905,6 +7905,44 @@ export function buildPanelToolDefs() {
             if (mode === "pinned" && pinnedWorkflowUuid) {
                 refreshWorkflowUuid(ctx, { workflow_uuid: pinnedWorkflowUuid });
             }
+            // #888 — make the SCOPE PIN follow the named workflow.
+            //
+            // Pinning wrote the workflow-target store above and, until now, nothing
+            // else. But after a mixed-origin turn the thing refusing every subsequent
+            // scope-addressed command is a DIFFERENT piece of state — the turn-origin
+            // pin, left ambiguous (`null`) by the #884 fence. So this tool reported
+            // success truthfully while the actual blocker went untouched, and the next
+            // `panel_graph_outline` returned the identical ambiguity error.
+            //
+            // The advice to do this is already in the code: the repin handler's own
+            // refusal says "Name the workflow instead — panel_set_workflow_target with
+            // a path, or panel_open_workflow — and the pin follows it." It did not
+            // follow, because only `mode:"current"` ever reached that handler.
+            //
+            // Routed through the SAME handler, so the P0 safety gate is shared rather
+            // than re-implemented: a pin that still reaches a live tab of this
+            // conversation is never displaced, however explicit the request. This can
+            // only ever recover a pin that is dead or ambiguous.
+            //
+            // Best-effort by construction: the pin store write above has already
+            // succeeded and is what the caller asked for. A repin that cannot happen
+            // must not retract it, so the outcome is reported, never thrown.
+            let scopeRepin;
+            if (mode === "pinned" && pinPath && isScopeAddress(ctx.tabId)) {
+                // The PATH, never a tab id derived from it. `wf:<path>` is the saved
+                // workflow HANDLE; a real tab id is a bridge ROUTE, `wf:<route>:<path>`
+                // (panel #640). The first cut of this fix compared the handle against
+                // routes, so it never matched and refused every time — inert, while a
+                // source-text "wiring" assertion passed, because grepping for a call
+                // cannot tell reachable code from dead code. The handler now does the
+                // matching against the routes the bridge actually holds.
+                try {
+                    scopeRepin = ctx.bridge.repinScopeToWorkflow?.(ctx.tabId, pinPath);
+                }
+                catch {
+                    scopeRepin = undefined; // never worse than the pre-#888 silence
+                }
+            }
             ctx.bridge.push({ type: "workflow_target", target }, ctx.tabId);
             // #770/#803/#716 — ROUTING is only half of "follow the tab that's live now".
             // rebindToActiveTab is a NO-OP whenever the bound tab is still REACHABLE, which
@@ -8037,12 +8075,23 @@ export function buildPanelToolDefs() {
                     `binding.\n\nAPPLIED (do not repeat this part): the workflow target is now ` +
                     `mode:"current"${rebindNote ? `.${rebindNote}` : "."}\n\nNOT APPLIED:${fence.note}`);
             }
+            // #888 — SAY what the scope repin did. A silent success is as unhelpful
+            // here as the silent refusal #1077 fixed: the whole complaint is that
+            // pinning reported success while routing stayed ambiguous, so "the routing
+            // ambiguity is cleared" is the one fact that makes this reply actionable.
+            // A refusal carries its own reason out for the same reason.
+            const scopeRepinNote = typeof scopeRepin === "string"
+                ? ` This session's turn routing was AMBIGUOUS (a reconnect delivered messages from several workflows at once) and is now pinned to this workflow, so graph tools will resolve deterministically.`
+                : scopeRepin && typeof scopeRepin === "object" && scopeRepin.reason
+                    ? ` NOTE — the workflow target was set, but this session's turn routing was NOT re-pinned: ${scopeRepin.reason}.`
+                    : "";
             return ok({
                 ...target,
                 ...(deferredBind ? { deferred: true } : {}),
                 ...(fence ? { graph_binding: fence.binding } : {}),
                 ...(fenceRebind ? { graph_binding_status: fenceRebind.status } : {}),
-                note: hint + rebindNote + (fence?.note ?? ""),
+                ...(typeof scopeRepin === "string" ? { turn_routing: "repinned" } : {}),
+                note: hint + rebindNote + (fence?.note ?? "") + scopeRepinNote,
             });
         }),
         def("panel_new_workflow", "Open a brand-new BLANK workflow in a NEW TAB. Use this whenever the user wants a 'new workflow' / 'fresh canvas' / 'start over for a new project'. This does NOT touch their current workflow — it opens a separate tab. NEVER use panel_clear for a new workflow (panel_clear wipes the CURRENT graph and is only for 'clear/reset this canvas').", {}, async (_args, ctx) => {