3 Commits

Include renames

Author	SHA1	Message	Date
Ilker ManapandClaude Opus 5.5	a95c519bc5	The admin API described in OpenAPI 3.1: generated from a route table by docgen, served at /api/v1/openapi.json ... adminapi.Routes lists every endpoint with its query parameters and Go values of the bodies it reads and answers with; internal/docgen/openapi turns that into docs/admin-api.openapi.json by reflection, the way encoding/json encodes the types, with the fields' comments as descriptions. A test fails when an endpoint is registered and not in the table, another when the committed document is stale. The binary embeds it and serves it with the token. Handlers that wrote map literals and decoded anonymous structs now use named types, so the document can see them. GET /api/v1/models/{name} answers with a model's whole definition as it is in force, which a tool managing it needs. docs/admin-api.md: reaching the API, the token, what a request must carry. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-04 23:47:59 +02:00
Ilker ManapandClaude Opus 5.5	9ab93a0aa6	Watch the cluster and edit every setting from the console ... The console gains live views of nodes, GPUs, models, replicas, usage and agent logs, and a settings tree over every key of server.yaml (agent.yaml on a node), generated from the configuration structs: values with their defaults and doc comments, edited in dialogs, saved only once the service's own loader accepts them, comments kept. The generator now tells blocks apart by package, which brings the TLS, engine and supervisor settings back into the reference. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-10-03 22:54:09 +02:00
Ilker ManapandClaude Opus 5	100f10ac17	Generate the configuration reference, and fail when it goes stale ... There was no reference. Four narrative documents explain how to install and operate llmgw, and the only way to learn that `lease_ttl` exists was to read the one that happened to mention it — or the struct. Written by hand it would have been wrong within a fortnight. Six settings arrived in the last two weeks alone: store, servers, lease_ttl, the two retention windows, min_disk_gb. A reference nobody maintains is worse than none, because it is the same list with the setting you came to look up quietly missing from it. So it is derived from the structs, with the field comments as the descriptions — which means the only way for it to be wrong is for the code to be wrong, and it makes the comments worth writing twice over. 1163 lines, 24 blocks, 87 keys. Two tests keep that true after everyone has forgotten this exists. One regenerates and compares, so adding a setting without regenerating is a failure rather than an omission — checked by adding one and watching it fail. The other walks the tree for koanf tags and fails on a configuration file that is in neither the source list nor the short list of structs an operator never writes, because a list is a thing to forget. The generator finds the repository from its own path rather than the working directory, so `go generate ./...` produces the same document from anywhere. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-27 07:43:30 +02:00