hanzo-dev 0d602fc9dc surface: regenerate the document for zip v1.26.0's operation names ...

zip v1.26.0 gave an operation ONE naming rule, and the bump landed without
re-projecting the document it renames. 758 operationIds across openapi.yaml and
55 plugin subsets still carried the old spellings — post_collaborator_rpc_documentId
and v1.admin.affiliates.post_id_approve where the rule now says
post_collaborator_rpc_by_documentid and post_v1_admin_affiliates_by_id_approve.

Nothing about the surface moved: same paths, same operations, same prose. An
operationId is the METHOD NAME in eight generated SDKs, the tool name in the MCP
list and the command in the spec-derived CLI, so leaving it stale means every
client offers a name the document no longer agrees with.

This is what surface-check exists to refuse, and it is why the gate has been red
on main: `make describe`, then commit what it wrote.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>

2026-08-05 13:40:25 -07:00

17 KiB

Raw Permalink Blame History