Teknium a6079dd350 feat(providers): GLM-5.2 native reasoning_effort controls (#58884) ... Port from Kilo-Org/kilocode#11555: GLM-5.2 exposes a native reasoning_effort knob with two enabled levels (high / max) on its OpenAI-compatible endpoints. Previously the zai profile (direct Z.AI /api/paas/v4) used the base ProviderProfile and emitted nothing, and the OpenCode Go profile only handled Kimi K2 / DeepSeek — so a user's effort preference for GLM-5.2 was silently dropped on both routes. - zai: ZaiProfile maps effort onto high/max (xhigh/max -> max, lower -> high) - opencode-go: same mapping for GLM-5.2, alongside existing Kimi/DeepSeek - alias spellings recognized (glm-5.2 / glm-5-2 / glm-5p2, vendor-prefixed) - disabled / no effort leaves the server default untouched		2026-07-05 13:48:01 -07:00
..
test_custom_profile.py	fix(custom-provider): emit reasoning_effort at the live profile path	2026-07-04 14:19:44 +05:30
test_deepseek_profile.py
test_kimi_profile.py
test_minimax_profile.py
test_ollama_cloud_profile.py
test_opencode_go_profile.py	feat(providers): GLM-5.2 native reasoning_effort controls (#58884)	2026-07-05 13:48:01 -07:00
test_zai_profile.py	feat(providers): GLM-5.2 native reasoning_effort controls (#58884)	2026-07-05 13:48:01 -07:00