zeekay 39699f3800 the front door says how to get it, and every claim in it is measured ...

The install line could not work: `ai.hanzo` is not a group on Maven Central,
and the four `v0.1.0-alpha.*` tags predate this client. README now says what
does work — `-PpublishLocal :hanzo-kotlin-cloud:publishToMavenLocal`, then
`mavenLocal()` — and the quickstart in it was compiled by a project that
resolves the artifact that way, rather than asserted.

The counts were methods called operations. Measured: the document at
`.spec-lock` is 1814 paths / 2479 operations, the tree is 192 API classes and
2461 models, and 2502 methods because 23 operations carry two tags and land in
two classes. `hanzo.yml` quoted 1742 and 1058 paths, both stale.

Every example named an operationId the document had renamed when the default
version left the id — `get_v1_keys` is `get_keys`, `get_v1_kv_by_name` is
`get_kv_by_name`. All six headers now carry ids read off the document. `hello`
catches `ClientException`, so the refusal it exists to demonstrate prints as a
status instead of a stack trace; `agent` defaults to `zen5`, which
catalog.hanzo.ai serves and `zen-1` does not; and the placeholder is `sk-`,
the class `GET /v1/keys` actually mints.

`.devcontainer` installed JDK 17 and the build wants a 21 toolchain, so it
could not build what it shipped with. Nothing referenced it.

2026-08-14 14:22:01 -07:00

..

src/main/kotlin

the front door says how to get it, and every claim in it is measured

2026-08-14 14:22:01 -07:00