Sergey Kozyrenko 4c0f4204ca feat(pconfig): validate agent config ranges on create/update (refs #288) ...

The GraphQL createProvider/updateProvider path applied no field validation, so
a direct API call (bypassing the browser's native HTML5 form validation) could
persist nonsensical values (temperature 99, negative price, an inverted
min/max length window, a reasoning budget over the 32000 engine cap).

Add ProviderConfig.Validate()/AgentConfig.Validate(), called after
patchProviderConfig in both CreateProvider and UpdateProvider. It is deliberately
permissive — 0 means "unset" and provider-specific tuning ranges remain the LLM
API's responsibility — so it only rejects universally-invalid values and never a
valid provider-specific config. Found during comprehensive provider QA.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-21 16:46:21 +07:00

..

cmd

feat(minimax): add MiniMax provider with full app/UI/installer parity (refs #328)

2026-06-21 15:24:04 +07:00

docs

feat(bedrock): support external config and model catalog paths (refs #233)

2026-06-20 08:30:10 +07:00

fern

…

gqlgen

…

migrations

feat(minimax): add MiniMax provider with full app/UI/installer parity (refs #328)

2026-06-21 15:24:04 +07:00

pkg

feat(pconfig): validate agent config ranges on create/update (refs #288)

2026-06-21 16:46:21 +07:00

sqlc

…

go.mod

…

go.sum

…