corezoid-alias-manager

# Corezoid Alias Manager ## What aliases are An alias is a human-readable `short_name` (e.g. `payment-service`, `send-otp`) that maps to a process (`conv`). Aliases serve two purposes: 1. **Process reference in JSON** — use `@alias-name` as `conv_id` instead of a numeric process ID. This makes processes portable across environments and removes hardcoded IDs. 2. **External HTTP entry point** — each alias generates a `callback_hash` used to send tasks to the process via the API Gateway URL. Alias naming rules (same as Corezoid short names): - Only lowercase letters `[a-z]`, digits `[0-9]`, and hyphens `-` - Must be at least 3 characters - Must be unique within the stage - Good: `payment-checkout`, `send-otp`, `create-user-v2` - Bad: `MyAlias`, `PAYMENT`, `a` --- ## MCP Tools | Tool | Purpose | |------|---------| | `create-alias` | Create an alias and link it to a process in one step | > **Note:** `list`, `modify`, `delete`, and `unlink` operations are not yet exposed as > MCP tools. Use the direct API calls documented below to perform them. --- ## Using aliases in process JSON Once an alias exists, replace the numeric `conv_id` with `@alias-name` in any node that calls another process: ### Call a Process node (`api_rpc`) ```json { "type": "api_rpc", "conv_id": "@payment-checkout", "extra": { "amount": "{{amount}}", "currency": "{{currency}}" }, "extra_type": { "amount": "number", "currency": "string" }, "err_node_id": "<error_node_id>" } ``` ### Cop...