* feat(cli): add workflow and project workflow commands
Wrap the existing /api/issue-workflows endpoints and the project workflow
switch so agents and scripts can read and change workflows without the
web UI. Permission checks stay on the server.
Refs #9698
Co-authored-by: multica-agent <[email protected]>
* docs(skill): teach the workflow CLI in the multica-platform skill
Workflow edits are rare, so the commands live in the projects reference
instead of the per-turn brief.
Co-authored-by: multica-agent <[email protected]>
* fix(cli): keep the mapping plan when a workflow write needs status mappings
On a 409 workflow_status_mapping_required, project workflow set and
workflow update now print the server's code and full plan to stdout
(JSON, or a table with --output table) and the message to stderr, and
still exit non-zero. The default formatter kept only the first message.
Also fix the zh CLI reference wording for tasks vs runs.
Co-authored-by: multica-agent <[email protected]>
* fix(cli): keep error bodies up to 64 KiB so structured errors parse
newHTTPError kept only 4 KiB of an error response. A workflow's 409
status mapping plan lists one row per status in use and passes 4 KiB at
around 45 statuses; the cut body no longer parsed, so the CLI fell back
to a generic message and dropped the plan.
Co-authored-by: multica-agent <[email protected]>
---------
Co-authored-by: multica-agent <[email protected]>
