Add runtime provider controls and searchable AI routing

Manage provider keys at runtime, route current-information questions through server-side search with safe fallback, and scope OOBE usage claims to grants.
2026-08-22 16:33:17 +08:00
parent f8fa93dc48
commit 9fb947aa7d
43 changed files with 2079 additions and 80 deletions
@@ -170,8 +170,10 @@ Gateway text requests may include the optional stable `taskKind` values document
 `docs/openapi.yaml`. The server maps `capability + taskKind` to a deterministic execution policy;
 it never infers task type from user content. Polish and transform tasks explicitly disable DeepSeek
 thinking and do not retry an empty buffered result. AI questions and agent planning explicitly use
-high-effort thinking. Search and tools remain disabled for every task because no safe, billable
-implementation is configured.
+high-effort thinking. Ordinary AI questions allow model-selected DeepSeek Responses web search;
+`current_information_question` requires web search. Search failures fall back to Chat Completions
+before any result is emitted. Other tools remain disabled, and search usage is billed only through
+the provider-reported LLM input and output Token counts.

 Store production values in 1Panel's secret/environment facility. The Compose environment receives
 them at runtime because this application does not read Docker `/run/secrets/*` files directly.