sync: cloud's woven document was behind — resync to ebd0851da
`sync.py --check` is the staleness gate on the one spec here that is not authored
here, and it was red: cloud/openapi.yaml lagged hanzoai/cloud's origin/main. Every
SDK, doc page and tool generated from this repo was therefore describing a router
that had already moved.
Resynced and re-merged. The published document:
paths 1738 -> 1739
operations described 1278 -> 1861 (77% of 2428)
tags described 236 of 264
paths taken by cloud 298, source-true
The described-operations jump is the point. That prose is not written here — it is
the apps' own Go doc comments, carried through cloud's weave into this document and
out to every generator. Re-running the sync is what moves it; nothing was authored
by hand in this commit.
234 authored shapes stay load-bearing (bodies, responses and parameters cloud takes
a route without declaring). That number falls to 0 on its own as those handlers
become typed `zip.Get[In,Out]` ops — it is a measure of the migration's remaining
distance, not a defect to patch here.
Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in: