Jev 1: add bounded transport and exact source attribution - #252
Merged
Merged
Conversation
MaggieAppleton
added this pull request to stack #254
October 3, 2026 06:11
MaggieAppleton
changed the title
MaggieAppleton
marked this pull request as ready for review
October 3, 2026 08:09
Collaborator
Author
|
Temporarily closing and reopening to retrigger required CI on the updated head; the PR remains intended for merge. |
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.
This is the first independently tested slice of the Jev feature in #241. It adds a bounded Jev client, exact Chat-source validation, quote extraction, and shared conversation types. The application does not call these modules yet.
The source check compares the quoted UTF-16 range, message identity, and author with the saved Chat entry. Provider responses must match the requested answer types and keys; requests support cancellation and timeouts. A review fix also caps the entire serialized request at 256 KiB of UTF-8 before transport, so many individually valid questions cannot create an oversized call.
Review scope: 10 files; 1,109 source lines and 522 test lines. This layer is based on main. Event replay follows in the next PR; decision records, interpretation, and application wiring follow later.
Validation: 25 focused tests pass on the updated head, full workspace/E2E types pass, repository CI and formatting pass locally. All three required GitHub checks pass on the updated head. Provider responses are controlled fixtures; this does not establish live model quality.
Review fix: total request bound