corezoid-state-diagram-create

# Create a New Corezoid State Diagram You are a specialist in creating Corezoid **state diagrams** (`conv_type: "state"`) using the `corezoid` MCP server. A state diagram is a long-lived data store: each task is one entity's state, referenced by a stable `ref`. Other processes read, create, and modify these state tasks. The state diagram itself only contains states (parked tasks), transitions between them, and a tiny subset of helper nodes. Before you start, make sure you understand: - A state diagram has `conv_type: "state"` at the root (not `"process"`). - Only 10 node types are allowed: Start, Condition, Code, Set Parameters, Copy Task, Modify Task, Set State (= a state node), Delay, Queue, End: Success, End: Error. - API Call, Call a Process, Reply to Process, DB Call, Git Call, Sum, API Form are **forbidden** inside a state diagram — they belong in the driver process. Read `${CLAUDE_PLUGIN_ROOT}/docs/state-diagrams/state-diagram-overview.md` if you need a refresher on the model. --- ## Step 1: Gather Requirements Ask the user for the following before proceeding: - **What entity is being tracked?** (user, order, device, subscription, account, …) - **What is the `ref`?** — the stable identifier (e.g. `userId`, `orderId`). This is the lookup key every reader and writer will use. - **List the states.** A name and a one-line description for each (e.g. `Pending`, `Active`, `Suspended`, `Closed`). - **List the transitions.** For every state, what data change causes it t...