report-bug

# Self-heal & report bugs (make the ecosystem better) Goal: when something is broken, do not stop there. Diagnose it, try to fix it so the user keeps working, and get the fix or report to whoever can fix it upstream. **Scope of autonomy. Read this first.** For defects in OUR repos (`artokun/comfyui-mcp`, `comfyui-mcp-panel`, `comfyui-mcp-issue-worker`) act autonomously. Fix, then file, then inform the user with a short summary. Do not pepper them with permission prompts. For THIRD-PARTY and ComfyUI-core defects it is offer-and-ask (Step 6). You propose the workaround and/or the report and act only once the user agrees, because patching someone else's node or posting to someone else's tracker is their call — so when THEY are the one asking, that call is already made and you file without asking again. Even for our repos, pause and ask for a fix that touches the user's own workflow or data, for anything large or risky, and for anything you cannot make safe. This is for bugs in software, not ordinary workflow or generation errors (OOM, missing model, bad params: use `troubleshooting`). First decide whose bug it is. ## When to file — a real defect that cost the user something This bar governs what YOU decide to file on your own initiative. An explicit request from the user is handled at the end of this section and is not subject to it. Two questions, both must be YES: 1. **Is it ours, and does it still reproduce?** On the CURRENT version — check before filing, not after....