veloGB10 v0.4.2
veloGB10 v0.4.2 — HOTFIX: accept OpenAI multipart content
Fix: ChatMessage.content deserialized as Option, but the OpenAI spec allows content to
be a STRING or an ARRAY of content parts (text / image_url). Agent clients (OpenAI agent SDK, Pi
harness) send the array form, which serde rejected with 422
(messages[N].content: invalid type: sequence, expected a string). Purely request-schema; the
engine/serve path does not change.
- string -> used verbatim
- null/absent -> None (agents send content: null on the assistant tool_calls turn)
- array -> extract {type:text,text:...} parts; single part verbatim, multiple joined with newline
Adds tests/hotfix_content/ fixtures covering the accepted shapes.
Source: dev repo @ 72e20be. Built from the public tree (self-contained), binary sha256
d7f0ae3a7eb49ad528a5c574946e9a07f1974cedb6312e5f1210cd4a3e850566.
Downloads
- velogb10-v0.4.2-gb10-sm121.tar.gz - engine binary + all PTX kernel artifacts + TP launch scripts
- SHA256SUMS.txt - checksums
- PROVENANCE.txt - build provenance