panel-node-pack-sync

# Keep the panel node-pack in sync with the orchestrator The orchestrator (`comfyui-mcp`, from npm) and the sidebar panel (`comfyui-agent-panel` on the Comfy Registry, repo `comfyui-mcp-panel`) ship **separately**. Updating one does not update the other. A new orchestrator driving an old panel fails in confusing ways — a bridge command the panel simply doesn't implement, a feature that exists in the docs but not in the sidebar — and those failures are hard for a user to diagnose. This skill closes that gap. ## The two rules that outrank everything else here 1. **Never report a sync that did not happen.** This whole feature sits on top of the fabricate-success fixes (#639/#641): ComfyUI-Manager reports its queue "drained" even when it never enqueued anything, and a `.bak`-style copy in `custom_nodes` can shadow the real panel in the browser. So the only version you may ever tell the user is the one **read back from disk after the fact**. If the tool throws, the sync FAILED — say so plainly. Do not soften it, do not retry it into a success, do not report the version you *intended* to install. 2. **Never move a pinned user.** A pin is a promise. If the user pinned the panel, you **warn and stop**. You do not unpin for them, you do not "just this once", you do not sync anyway because the new version is obviously better. Offer to clear the pin, and act only if they say yes. ## Step 1 — Look before you touch anything ``` install_comfyui(action:'pane...