mirror of
https://github.com/JackChen-me/open-multi-agent.git
synced 2026-10-19 01:29:57 -05:00
Two roles failed in 2026-09 with STRUCTURED_OUTPUT_VALIDATION_FAILED on bracket mismatches deep inside long nested output, and the in-run correction failed the same way. #599 moved the nested object to the end of each schema so the model has no boundary to hold, which works around the symptom without changing what the provider guarantees. Set `response_format: { type: 'json_object' }` on the shared role config through `extraBody`. DeepSeek then guarantees that the answer parses as JSON, so the syntax failure class goes away at the source. A direct API probe with the pre-#599 planner schema, thinking at max effort, and a tool turn confirmed that DeepSeek accepts the mode in that combination and returned strict JSON on every run. OMA still validates the answer against the role's schema, so the in-run correction keeps handling schema mismatches. The scripted adapter test asserts that every role carries the mode, and the README documents it next to the shared output ceiling.