Fix 8 Responses API references in unified-llm-spec.md + add Rust exemplar#6
Open
bkrabach wants to merge 1 commit intostrongdm:mainfrom
Open
Fix 8 Responses API references in unified-llm-spec.md + add Rust exemplar#6bkrabach wants to merge 1 commit intostrongdm:mainfrom
bkrabach wants to merge 1 commit intostrongdm:mainfrom
Conversation
…ust exemplar Spec fixes — 8 places where reference tables used Chat Completions API field names but §2.7 mandates the Responses API: S-1: §7.3 tool call item 'id' → 'call_id' S-2: §7.4 tool definition: nested → flat format S-3: §3.9 usage fields: prompt_tokens → input_tokens, etc. S-4: §7.8 tool result: 'tool role messages' → function_call_output items S-5: §7.8 stream termination: 'data: [DONE]' → response.completed event S-6: §3.8 finish reasons: Chat Completions → Responses API status field S-7: §5.3 named tool choice: nested → flat format S-8: §7.8 Gemini auth: note both query param and header supported README: Added Implementations section with Rust exemplar link
jaytaylor
added a commit
to jaytaylor/attractor-tcl
that referenced
this pull request
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
8 places in
unified-llm-spec.mdwhere reference tables use Chat Completions API field names but §2.7 mandates the Responses API. The prose sections are already correct — only the reference tables needed updating.Also adds an Implementations section to README linking to a Rust exemplar.
Spec Fixes
"id"→"call_id"prompt_tokens→input_tokens, etc.function_call_outputitemsdata: [DONE]→response.completedeventHow found
Built a Rust implementation (bkrabach/unified-llm-client-rust) — 12 rounds of adversarial audit, 141/141 DoD, 925 tests (54 live API). Implementation correctly targets the Responses API in all cases; spec tables were the discrepancy.
README
Added Implementations section with link to the Rust exemplar.