Repository navigation
feat(llm): add bounded Anthropic Messages transport - #103
Merged
Merged
Conversation
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
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.
The LLM provider contract now has an Anthropic Messages implementation for direct structured actions and strict game tools. Requests record explicit effort and thinking policy, cache the immutable briefing, and optionally use server-side tool-result clearing while preserving local history and signed blocks.
The client uses a fixed HTTPS endpoint with sensitive credential headers, bounded bodies and timeouts, and no automatic retries, redirects, or ambient proxies. Responses retain provider content and separate uncached input, output, cache reads, and both cache-write lifetimes. Refusal/output exhaustion remain completions with usage; transport errors contain no raw provider diagnostics. Hosts must reserve budget before calls and retain uncertain billing reservations after failures.
Validation: 15 tests pass, including loopback HTTP tests for both modes, history preservation, cache accounting, invalid input/response, large and chunked responses, body deadlines, cancellation, no hidden retries, and redirect credential isolation. Clippy with warnings denied, formatting, and workspace dependency checks pass. No paid API calls were made. Match scheduling and durable budget integration follow separately.
SemVer: additive feature (minor).