Strengthen API compatibility across various gateways and external API integrations by addressing inconsistencies in OpenAI-compatible interface implementations, /models endpoint availability, and support for different API endpoints like responses versus chat/completions.
# [Feature]: 加固 Provider / Gateway 兼容性与外部 API 接入 / Harden provider-gateway compatibility and external API integration ## Problem / pain point / 问题 Open CoDesign 已经支持多 provider、自定义 OpenAI-compatible endpoint、keyless provider、以及外部配置导入,但 API 兼容性仍然偏“隐式”: - 不同 gateway 只实现了部分 OpenAI-compatible 接口 - 有些 endpoint 有 `/models`,有些没有 - 有些支持 `responses`,有些只支持 `chat/completions` - `system` / `developer` role 行为不一致 - reasoning 支持依赖 provider 和 model - 外部配置导入正在增多,但每个来源仍然有独立逻辑 Open CoDesign already supports multiple providers, custom OpenAI-compatible endpoints, keyless providers, and external config import. The remaining pain is compatibility hardening: - different gateways partially implement OpenAI-compatible APIs - some endpoints expose `/models`, some do not - some providers support `responses`, others only `chat/completions` - role handling differs across gateways - reasoning support depends on provider/model - external imports are growing, but each source still has bespoke logic ## Proposed