regenerate from cloud@5126939 — the client leaves the hand-merged lineage

pkg/hanzoai/cloud goes +2186 -2126 ~175: 1700 paths / 2354 operations / 2186
schemas, 182 api modules and 2172 model modules, against the 239/1116 it carried
from hanzo.yaml. The document is hanzoai/cloud's own emission now, pinned in a
new .spec-lock by commit and sha256, and generate.py reaches it by value —
--skip-validate-spec means the 1012 missing-`responses` errors no longer write
zero files, so a client can be cut from the authority instead of a projection of
it.

Two renamings come with that, and both are the fix rather than the damage. IAM's
types are namespace-qualified (iam.Role, iam.Application, 95 of them) because a
bare `Role` was two unrelated shapes wearing one name. And the <svc>_ prefix is
gone from every operationId, so every generated method lost it.

The prefix is what broke the examples, and the gate saw only two thirds of it.
Four flows failed on their imports; `money` and `tools` PASSED while every call
in them named a method that no longer existed — an import resolves the names in
the `from … import` line and a method is looked up at call time. All five flows
now name operations that exist, checked by resolving each one as an attribute,
and hanzo.yml records that ceiling so the next reader does not trust the gate
for more than it says.

`chat` is removed, which is a measurement and not a preference: cloud declares
POST /v1/chat/completions with no requestBody and no responses at all, so the
generated method takes no body and returns None — the one call a chat example
exists to make cannot be expressed. Inventing the type, or hand-rolling the HTTP
inside a generated client, is the drift these SDKs exist to prevent; js-sdk
dropped its own chat flow at 2.0.7 for exactly this. It returns the release
cloud gives that route a body.

Two smoke assertions were already red before this regeneration and are now true
again: they pinned AIApi/APIKeysApi/MCPApi and AdminApi.plugin_admin_*, names
from the retired lineage. The surface is all still there under AiApi/KeysApi/
McpApi and AdminApi.admin_plugins.

tests/test_zap_transport.py still errors, exactly as it did before: it imports
`Hanzo` from hanzoai, which the hand-written package does not define. That is
not this document's business and is untouched.

Minor rather than patch: every generated method changed name.

Co-authored-by: Hanzo Dev <[email protected]>

examples/store/__main__.py

@@ -1,8 +1,8 @@
 """store — a KV round-trip: provision a store, read it back, delete it.
 
-    POST   /v1/kv          cloud_post_v1_kv         provision
-    GET    /v1/kv/{name}   cloud_get_v1_kv_name     read back
-    DELETE /v1/kv/{name}   cloud_delete_v1_kv_name  tear down
+    POST   /v1/kv          post_v1_kv         provision
+    GET    /v1/kv/{name}   get_v1_kv_name     read back
+    DELETE /v1/kv/{name}   delete_v1_kv_name  tear down
 
 This is the PROVISIONING plane. The per-key data plane the spec also describes
 (``/v1/kv/keys/{key}``) is not mounted anywhere — GET 404s and PUT/DELETE 405 at
@@ -18,7 +18,7 @@ rather than leaving it billable for the next run to collide with.
 
 import time
 
-from hanzoai.cloud import CloudProvisionRequest, KvApi
+from hanzoai.cloud import ProvisionRequest, KvApi
 
 from examples.client import client, run
 
@@ -29,15 +29,15 @@ def main() -> None:
     with client() as api:
         kv = KvApi(api)
 
-        kv.cloud_post_v1_kv(CloudProvisionRequest(name=NAME))
+        kv.post_v1_kv(ProvisionRequest(name=NAME))
         print(f"provisioned {NAME}")
 
         try:
-            store = kv.cloud_get_v1_kv_name(NAME)
+            store = kv.get_v1_kv_name(NAME)
             print(f"read back: {store.name} · {store.kind} · status {store.status}")
             print(f"  host {store.host}:{store.port}")
         finally:
-            kv.cloud_delete_v1_kv_name(NAME)
+            kv.delete_v1_kv_name(NAME)
             print(f"deleted {NAME}")