agent-platform release v3.12.0

model-manager.lmstudio.endpoint / .agentHost and the lmstudio backend in the connectivity chart’s model-manager wiring: an LM Studio on the host (llama.cpp on GPU and CPU, MLX on Apple silicon) as a serving backend. templates/model-manager/validate.yaml accepts the name and, as for ollama and lemonade, fails the render when the endpoint is missing or carries no scheme; _helpers.tpl gains modelManager.lmstudioEndpoint and the lmstudio arms of hostEndpoint/hostTargets, so the model-manager NetworkPolicy opens egress to the LM Studio host in both flavors. Requires model-manager >= 0.19.0, and that is a pin to move rather than a backend to select: values.yaml forwards the whole model-manager block — lmstudio included — to every release, and the key does not exist before 0.19.0, whose schema is additionalProperties: false, so a chart pinned below it rejects the values outright even on an installation that never touches LM Studio (examples/customer-bom.yaml floors it accordingly). LM Studio serves no delete (lms rm is host-only), so that call answers 501 unsupported.