Add client conformance for SEP-2663 task results - #405
Open
brixton-guns wants to merge 1 commit into
Open
Conversation
brixton-guns
marked this pull request as ready for review
July 20, 2026 07:50
brixton-guns
force-pushed
the
codex/issue-374-client-tasks
branch
from
July 29, 2026 08:27
fbec97c to
5036744
Compare
Add client conformance coverage for CreateTaskResult polling, a positive fixture, and a deliberately broken no-poll client. Layer the Tasks extension on the 2026-07-28 base revision and integrate extension results with wire-schema validation.
brixton-guns
force-pushed
the
codex/issue-374-client-tasks
branch
from
July 29, 2026 09:38
5036744 to
b074c7f
Compare
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
tasks-client-create-handling, where the harness returns a server-directedCreateTaskResultfromtools/calland requires the client to retrieve it withtasks/getsource.extensionId, and allow extension scenarios to declare the core protocol version they layer onWhy
The server suite already covers SEP-2663, but the client suite could not observe the client requirement to handle either a standard result or
CreateTaskResult. This implements the first client scenario proposed in #374.The scenario is black-box: it proves that the client recognizes the task envelope and follows the returned handle with
tasks/get. It does not claim to observe application-level use of the completed result.Alignment with current main
Rebased onto
49103de, incorporating the 11 upstream commits added since the original PR base.DRAFT_PROTOCOL_VERSION(2026-07-28)MISSING_REQUIRED_CLIENT_CAPABILITYcode,-32021CreateTaskResultas a base draftResultenvelope, since Tasks v2 types intentionally live outside the core draft schemawire-schema-validgreen for both the conformant and deliberately broken client pathsValidation
npm run checknpm run buildnpm test— 488 tests passedwire-schema-validsep-2663-client-handles-polymorphic-resultwith the expected diagnostic;wire-schema-validpassesAddresses #374.