3 Commits

Include renames

Author	SHA1	Message	Date
m1saka	2517b4f730	Add OpenAI Responses API (/v1/responses) endpoint ... Translate Responses API requests (input→messages, instructions→system, max_output_tokens→max_tokens, text.format→response_format, flat tools→nested {function:{…}}) to upstream chat/completions, then convert responses back to Responses format (streaming SSE event lifecycle + non-streaming JSON). Verified against OpenAI migration guide and Python SDK Response model: - Echo back required fields parallel_tool_calls/tool_choice/tools - Include content:[] in reasoning items, logprobs:[] in output_text parts - Support function_call/function_call_output multi-turn input items - Map usage fields prompt_tokens→input_tokens, completion_tokens→output_tokens	2026-08-20 10:02:11 +08:00
m1saka	7d8a5b6f74	Update proxy to Zhanlu v1.4.2 provider flow ... The 1.4.2 extension replaced the old signed/encrypted chat gateway with an OpenAI-compatible aigateway. Align the proxy with the new flow: - Use ecloud.10086.cn login/model base URLs, zhanlu_ide plugin headers and v1.4.2 plugin version - Provision the model API key via SM2-signed get-or-create after v1/login profile fetch; store api_key/model_base_url/email in credentials - Chat via Bearer apiKey against {modelBaseUrl}/chat/completions with plain OpenAI SSE passthrough; fetch /v1/models from the gateway model-info endpoint - Force HTTP/1.1 upstream (gateway drops HTTP/2 ALPN negotiation with EOF) - Drop obsolete AES body encryption, model name mapping and vscode headers	2026-08-05 14:55:28 +08:00
M1saka	d4dd3a0f1b	Initial zhanlu OpenAI proxy	2026-07-08 09:13:45 +08:00