GGUF jobs 2 and 3:
Switched off `unsloth studio run` and over to `UNSLOTH_API_ONLY=1
unsloth studio` + login flow. Reason: studio.run() resolves the tool
policy through unsloth_cli/_tool_policy.resolve_tool_policy, which
defaults to True on loopback. That means set_tool_policy(True) gets
applied process-wide, and every /v1/chat/completions request is
routed through the server-side agentic loop -- so Job 2's standard
function-calling test never gets a structured tool_calls response
(the model uses web_search instead) and Job 3's response_format
test gets non-JSON SSE chunks back. API-only mode leaves
tool_policy=None, which is what each request's `enable_tools` flag
(or absence thereof) needs to be honoured.
Job 1:
Anthropic SDK retry: the SDK sends `x-api-key` by default, but
Studio's auth layer is HTTPBearer-only. Override via
default_headers={"Authorization": f"Bearer {KEY}"}, which is the
shape the integration docs suggest.
UI smoke:
Drop the "history must persist after reload" assertion; Studio's
thread autosave is async and doesn't reliably land within the CI
budget. Keep the assertion that matters: the chat composer mounts
again after a reload and the JWT survived (no /login redirect),
which is what the 2026.5.1 chat regression actually broke.
4b69262c38