Repository navigation
Enable bounded v17 context selection with immutable runtime binding - #224
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 SlopSearX read-only caller can now select bounded-production-v17, which supplies the finite immutable context-target manifest. The option and all workflow/admission runtime pins change together to dd01a24. The resolver validates exact profile and limits digests, manifest bounds, source revision policy, and claim cap before dispatch.
Legacy-v14 remains the default; v14 and v16 profile bytes and existing limits are unchanged. This manual read-only path does not publish reviews or execute PR code.
Validation: 68 focused tests passed in both author and root runs; independent selector and pin reviews CLEAR. Actual provider-free PR305 preparation admitted all 42 required obligations with zero provider calls or target execution; optional gaps and dynamic runtime-stage demand remain explicit. Runtime source passed 23 enabled exact-head checks and merged bytes match the reviewed tree; post-merge verification continues separately.