Marius van Niekerk
fe5f6a9388
The API migration needed to stop carrying two parallel contracts: typed Huma handlers on the server and hand-assembled frontend request paths in the UI. That split made enums, request bodies, response shapes, and error handling easy to drift, and review feedback showed the first migration pass still left some runtime parity and generated-client boundary gaps. This PR moves the server API onto grouped typed Huma route registration, exposes OpenAPI 3.1 for introspection, generates the frontend TypeScript client from that contract, and routes normal JSON frontend calls through generated services. Streaming, import, and download paths stay explicit where the generated JSON abstraction is not appropriate. It also addresses review follow-ups around route-group ownership, generated-code metadata, import response content types, secret-scan SSE parity, and generated-client error normalization. Validation performed locally: - go test -count=1 ./... - npm run generate:api - npm run check - npm test -- --run - git diff --check Co-authored-by: Marius van Niekerk <mariusvniekerk@users.noreply.github.com>
5 lines
43 B
TOML
5 lines
43 B
TOML
version = 1
|
|
|
|
[project]
|
|
name = "agentsview"
|