130f6f1e9a
Prevent unsupported developer-role API failures by making provider role compatibility explicit and covered by regression safeguards. - Add explicit supportsDeveloperRole capability to custom provider metadata/types and wire it through provider registration. - Update CLI custom-provider registration behavior and tests to persist and validate developer-role compatibility settings. - Add/adjust engine regression coverage for openai-completions message role conversion, including reasoning-model fallback behavior. - Document the new custom provider setting and add a published changeset for @runfusion/fusion. Files changed: .changeset/fn-5834-developer-role-compat.md | 5 ++ docs/settings-reference.md | 2 +- packages/cli/src/commands/__tests__/custom-provider-registry.test.ts | 44 +++++++++++- packages/cli/src/commands/custom-provider-registry.ts | 9 ++- packages/core/src/types.ts | 5 ++ packages/engine/src/__tests__/custom-providers-openai-completions.test.ts | 84 +++++++++++----------- 6 files changed, 106 insertions(+), 43 deletions(-) Fusion-Task-Id: FN-5834 Fusion-Task-Lineage: 4edc80c9-5e60-41e4-bce1-662d18255d88
6 lines
434 B
Markdown
6 lines
434 B
Markdown
---
|
|
"@runfusion/fusion": minor
|
|
---
|
|
|
|
Custom OpenAI-compatible providers now register with explicit conservative role compatibility: Fusion defaults `compat.supportsDeveloperRole` to `false` so reasoning-capable models emit the legacy `system` role instead of relying on provider URL auto-detection. Advanced users can opt in per provider with `supportsDeveloperRole: true` when their endpoint explicitly supports the `developer` role.
|