generated from coulomb/repo-seed
The previous strict=True default rejected the activity-core daily-triage schema (and most real-world application schemas) because OpenAI strict mode requires additionalProperties:false on every object and every property in the required list. Application-supplied schemas typically do not meet that bar — adding additionalProperties recursively at the adapter would be surprising and may break callers that rely on extra fields. Flipping strict to False keeps the schema as a soft constraint; the model still produces structured output and the activity-core canary's 400 from OpenRouter goes away. Callers who need strict enforcement can pass response_format directly via model_params, where the adapter's pass-through handling preserves the strict flag they set. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
8.3 KiB
8.3 KiB