Files
zeekay fd4da20ec5 test(gen): commit end-to-end proof artifacts (TS + OpenAPI + Go)
Force-added past .gitignore's out/ as reproducible proof that one .zap
schema mechanically produces every surface:
- out/ts/tasks/tasks_zap.ts   Tier-2 zero-copy View/Client/Server; tsc --noEmit
  clean against @zap-proto/zap under strict (noUnusedLocals, verbatimModuleSyntax).
- out/{ts,go}/tasks/tasks.openapi.json  OpenAPI 3.1.0; openapi-spec-validator OK;
  4/4 methods as POST /tasks/<method>; 9 referenced structs in components.schemas.
- out/go/tasks  oapi-codegen Tier-1 client + go.mod + offline request-forming
  test: go vet/build/test all green (forms POST https://api.hanzo.ai/tasks/*).
- out/docs/{ts,go}/tasks.mdx  generated SDK doc stubs.

Regenerate: bin/zapsdk ts schemas/tasks.zap ; bin/zapsdk go schemas/tasks.zap
2026-07-05 13:29:14 -07:00

11 lines
469 B
Plaintext

---
title: go SDK
description: Generated ZAP SDK — quickstart and typed-client usage.
---
{/* Generated by zap-proto/gen from schemas/tasks.zap. DO NOT EDIT — regenerate: bin/zapsdk go schemas/tasks.zap */}
# go SDK
ZAP-native transport is primary; HTTPS/WS/SSE is the fallback. Install, construct the client, pick a transport, call a method. For the full endpoint reference see the [canonical API reference](/docs/api) — this page does not re-list endpoints.