add-api-endpoint

name	add-api-endpoint
description	Add a new HTTP endpoint end-to-end across the Go (Huma) backend and the Electron TS renderer. Use when the user asks to add a route, expose a new API, or wire a new request/response type from Go to TS. Covers the mandatory `Go struct → huma.Register → openapi → codegen → typed client` chain.

Architectural invariants (do not violate)

• Business logic lives only in Go under /internal. Electron renderer just consumes the generated client.
• Request/response TS types come only from electron/src/api/schema.ts (auto-generated from openapi.yaml). Never hand-write them.
• Endpoints must be registered through Huma's huma.Register(api, op, handler). Bare net/http handlers never appear in OpenAPI and are invisible to TS.

Workflow

1. Define the Go types and handler in internal/api/api.go (or a sub-file in the same package).

   • Input struct: path/query/header tags drive OpenAPI parameters.
   • Output struct must wrap the JSON body in a Body field (Huma convention).
   • Annotate fields with json:"...", example:"...", doc:"..." so the generated TS is self-documenting.
   • Keep the handler thin; push real logic into a sub-package of /internal.

2. Register the operation in api.Register(api huma.API):

   huma.Register(api, huma.Operation{
       OperationID: "kebab-case-id",       // becomes the TS operation key
       Method:      http.MethodGet,        
       Path:        ,
       Summary:     ,
       Description: ,
       Tags:        []{},
   }, handlerFn)