fix(sdk): retain nearby values in semantic queries - #72
Open
gabriel wants to merge 3 commits into
Open
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
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.
A query for an output label could omit the generated value beneath it when the value used different words. Semantic reads now retain up to two following blocks in the same structural region and report query coverage separately from whole-page coverage. Existing character and section limits still apply.
Action decoding also rejects unknown fields instead of silently dropping them.
Also documents the companion REL chat changes: observation-scoped references, semantic representations, bounded action deadlines, and error recovery.
Validation: 20 rel-client tests passed; rel-client Clippy passed with warnings denied. The new regression checks generated output beneath a matching label and prevents crossing into another heading or footer.
The public Chat guide also documents the live Bedrock follow-up in https://github.com/rel-me/rel/pull/410: self-contained writing uses a short prompt with no browser tools, unavailable calls return bounded feedback, and token accounting includes tool-only and recovered inferences. This follow-up changes documentation only in this repository; the previously validated SDK code is unchanged.