classifier.cloud_fallback was manual-YAML-edit-only: referenced in the gaming-mode explanation and the local_compute.enabled validation error, but with no portal control. Add a Cloud Fallback card to the Controls page (near the Local Compute toggle that explains why it is needed), backed by a new POST /admin/api/cloud-fallback-config endpoint that persists the whole block atomically via _persist_many_to. The GET side reuses admin_classifier_config_get, adding a cloud_fallback field to report current state. The write endpoint validates base_url and model are both required and not blank (mirroring the present-but-blank check written for cloud_primary) and treats null as clearing the optional block. Frontend mirrors the cloud_primary field shape and the send-null-instead-of-empty-block lesson. Tests mirror the cloud_primary admin write coverage.
7.2 KiB
7.2 KiB