corezoid-process-tech-writerlisted

# Corezoid Process Tech Writer Always produce **two outputs** for every process: 1. Markdown documentation file at `.processes/<name>-docs.md` 2. Enriched process JSON (same file, `description` fields filled in) at `.processes/<name>-enriched.json` --- ## Step 0 — Load the process If the user provides a file path, read it directly. If they provide a process name or ID, use `pull-process` to fetch it first. --- ## How to extract information from the process JSON ### Inputs Read the `params` array. Each entry has: - `name` — parameter name - `type` — data type - `descr` — description (may be empty — infer from context) - `flags` — `"required"` flag means mandatory; `"input"` = input param, `"output"` = output param - `regex` — validation pattern (document if non-empty) ### Outputs Find all nodes with `api_rpc_reply` logic in `condition.logics`: - `throw_exception: false` → success response — document `res_data` keys and types - `throw_exception: true` → error response — document what triggers it (node title, `exception_reason` if present) ### Process flow Walk `scheme.nodes` following `go` entries from the Start node (`obj_type: 1`): - Start → node with `id` matching the `to_node_id` in Start's `go` logic - Continue following `go` entries to map the happy path - Note branches at Condition nodes or `go_if_const` entries - Note error paths via `err_node_id` references ### External dependencies - API Call nodes (`api` logic): extract `url`, `method`, `extra_headers` - `{