go/doc concatenates EVERY comment attached to a `package` clause, in file
order — so a file header on an alphabetically-earlier file becomes the
package doc. `go doc ./apps/visor` opened "board.go — GET /v1/fleet"; platform
opened with applylive.go, deploy with actions.go. Detach the 43 file headers
with a blank line so the one product paragraph is the whole package doc — the
text that becomes the OpenAPI tag, the MCP door prose and the CLI group help.
Four docs named the wrong thing or claimed something untrue:
deploy said "Package gitops" — it is Hanzo CD at /v1/deploy
goja said "Package gojahost"
do said DigitalOcean is Hanzo's EXCLUSIVE cloud venue; venue links
DigitalOcean, AWS, GCP and Azure. do is the HOUSE account
membership cited cloud.SetLiveSource and apps/ installing it; both are gone
(22f4fc64) and nothing calls K8s — say so, the outage it fixes is
not fixed
And platform pointed at a Goa design module that emits 15 ops against the 30
the router registers — a second source that has already drifted; say which one
is the contract. clients/<app> paths in these docs are now apps/<app>.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
hanzo-dev
eb46d92d81