docs: clarify the session/update variant set is not exhaustive - #1858
Open
somtri wants to merge 1 commit into
Open
docs: clarify the session/update variant set is not exhaustive#1858somtri wants to merge 1 commit into
somtri wants to merge 1 commit into
Conversation
The v1 prompt-turn page walks a turn through five session/update variants while schema/v1/schema.json defines eleven, and nothing on the page marks the walkthrough as partial. Point at the SessionUpdate schema reference as the authoritative list, and cover unrecognized variants on the extensibility page. Refs agentclientprotocol#1694
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.
Fixes #1694.
The prompt-turn page walks a turn through five
session/updatevariants, whileschema/v1/schema.jsondefines eleven. Nothing marks the walkthrough as partial, so it reads as the full set.Adds a Note pointing at the
SessionUpdateschema reference, plus a short section inextensibility.mdxon unrecognized variants, which that page didn't cover. Thedraft/copies get the same change, matching 8750b93.Two calls worth flagging: I kept the extensibility wording advisory rather than SHOULD, since
SessionUpdateis a closedoneOfwith no catch-all. And v2 has the same gap (9 shown against 17) which I left alone, happy to add it here or in a follow-up.The StopReason question in the issue is a separate protocol matter, untouched here.