Repository navigation
fix: use supported model output allowances by default - #97
Merged
Merged
Conversation
pavelhov
marked this pull request as ready for review
November 12, 2026 18:59
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.
Summary
Ordinary model turns use their known output allowance by default, including existing configurations and requests with a smaller client cap. Native Fable 5.2 gets 128,000 tokens, removing the effort-dependent 32,768-token default that interrupted long coding turns.
The default
model-maxpolicy selects known capacity ahead of caller and configured totals. This can increase usage or lower an oversized requested total. SetoutputTokenPolicytorequestto honor caller caps and configured fallback budgets. Capacity metadata must match the provider destination. Unknown capacities use request and adapter fallbacks. Context compaction has its own maintenance budgets.This also prepares package version 0.1.27 for the official signed updater release.
Validation
Security review
Reviewed native Messages mutation, destination-scoped capacity metadata, mixed-wire routing, private provenance fields, cancellation, and credential boundaries. Private routing fields are request-local and strict configuration validation rejects them on disk.
Release preparation uses the existing external Ed25519 trust anchor and pinned Sparkle 2.9.6 tools. Signing material uses owner-only files and stdin. Universal archive identity and signatures will be verified against the qualified source commit, downloaded draft assets, and the published updater discovery URL. The release is an ad-hoc, unnotarized preview.