Update to Corezoid

{
  "description": "Safely pauses, resumes, or moves existing Corezoid processes and folders. Use only when the user explicitly asks to pause/unpause/resume/activate a process or to move/relocate/reorganize a specific process or folder. Trigger on \"pause process\", \"resume process\", \"move process\", \"move folder\", \"поставь процесс на паузу\", \"сними с паузы\", \"возобнови процесс\", \"перемести процесс\", \"перемести папку\", \"перенеси процесс\", or \"перенеси папку\". Do not activate merely because a review, edit, cleanup, or refactor is in progress; those are not authorization to mutate lifecycle or location.\n",
  "included_files": [],
  "name": "corezoid-lifecycle",
  "skill_md_contents": "---\nname: corezoid-lifecycle\ndescription: >\n  Safely pauses, resumes, or moves existing Corezoid processes and folders.\n  Use only when the user explicitly asks to pause/unpause/resume/activate a\n  process or to move/relocate/reorganize a specific process or folder. Trigger\n  on \"pause process\", \"resume process\", \"move process\", \"move folder\",\n  \"поставь процесс на паузу\", \"сними с паузы\", \"возобнови процесс\",\n  \"перемести процесс\", \"перемести папку\", \"перенеси процесс\", or\n  \"перенеси папку\". Do not activate merely because a review, edit, cleanup,\n  or refactor is in progress; those are not authorization to mutate lifecycle\n  or location.\n---\n\n# Corezoid Lifecycle and Move Operations\n\nUse this skill for deliberate operational changes to existing Corezoid\nobjects. These tools act on live server state and require explicit user intent.\n\nRead `${CLAUDE_PLUGIN_ROOT}/docs/process/process-lifecycle-and-move.md` before\nthe first lifecycle/move operation in a session.\n\n## Non-negotiable authorization rule\n\nNever pause, resume, or move an object automatically.\n\nThe following are not authorization:\n\n- a process appears unused;\n- a review or refactor is in progress;\n- edits/tests have completed;\n- a folder layout looks untidy;\n- pausing or moving would be a convenient safety precaution.\n\nThe user must directly ask for the specific action. If the exact object or\ndestination is ambiguous, resolve candidates read-only and ask the user to\nchoose. Do not infer a target.\n\n## Required two-step workflow\n\nFor all four tools:\n\n1. Resolve and repeat back the exact object ID/title. For moves, also resolve\n   the exact destination ID/path.\n2. Call the tool with `apply=false` (or omit `apply`).\n3. Present the dry-run, including current state/location, target, operational\n   effects, and the exact confirmation token.\n4. Ask for explicit confirmation. Do not invent confirmation from earlier\n   general approval. The token is reconstructable and is not itself evidence\n   that the user approved the operation.\n5. Only after confirmation, call `apply=true` with the exact token returned by\n   the fresh dry-run.\n6. Report the tool's verified result. If it says verification failed or state\n   may already have changed, stop and run a new dry-run; never retry blindly.\n\n## Pause a process\n\nUse:\n\n```text\npause-process(process_id=<id>)\npause-process(process_id=<id>, apply=true,\n              confirm=\"process#<id>:<live_status>->paused\")\n```\n\nExplain before confirmation:\n\n- Corezoid will reject new task creation with `conveyor_is_not_active`.\n- The graph and deployment are unchanged.\n- Already-running or parked tasks are not modified by this tool and must be\n  inspected separately.\n- Pause is temporary admission control, not evidence that a process is safe\n  to delete.\n\nPause can support a user-chosen maintenance/observation window. Never choose\nthat window on the user's behalf.\n\n## Resume a process\n\nUse:\n\n```text\nresume-process(process_id=<id>)\nresume-process(process_id=<id>, apply=true,\n               confirm=\"process#<id>:<live_status>->active\")\n```\n\nBefore confirmation, verify with the user that maintenance is complete and\nthat the process may receive traffic. New tasks can arrive immediately from\nAPI callers, schedules, callbacks, and other processes. Never auto-resume just\nbecause this session originally paused the process.\n\n## Move a process\n\nUse:\n\n```text\ncz-structure {\"action\": \"move-process\", \"args\": {\"process_id\": <id>, \"destination_folder_id\": <folder>}}\ncz-structure {\"action\": \"move-process\", \"args\": {\"process_id\": <id>, \"destination_folder_id\": <folder>,\n                    \"apply\": true, \"confirm\": \"<exact context-bound token from the fresh dry-run>\"}}\n```\n\nThe operation reparents the existing process. It preserves the same ID and\ngraph; it does not copy, import, or deploy.\n\nIf the dry-run reports a project/stage/root context change, explain the alias,\nenvironment-variable, access, and deployment risks. Proceed only after the\nuser accepts those risks, adding `allow_cross_stage=true` to the confirmed\ncall.\n\n## Move a folder\n\nUse:\n\n```text\ncz-structure {\"action\": \"move-folder\", \"args\": {\"folder_id\": <id>, \"destination_folder_id\": <folder>}}\ncz-structure {\"action\": \"move-folder\", \"args\": {\"folder_id\": <id>, \"destination_folder_id\": <folder>,\n                    \"apply\": true, \"confirm\": \"<exact context-bound token from the fresh dry-run>\"}}\n```\n\nOnly normal folders can be moved. The action rejects projects/stages, self-move,\nand moving a folder into a descendant. For cross-stage/root moves, the risks\napply to every descendant and `allow_cross_stage=true` is required after the\nuser accepts them.\n\n## After a move\n\nThe MCP tool does not relocate local mirror files/directories. Re-pull the\ndestination and verify it before removing any stale local copy. Local cleanup\nalso requires explicit user intent; never delete the old local path merely\nbecause the server move succeeded.\n"
}