tasks/required-task-error: anchor -32003 checks to sep-2663.yaml rows#10
Merged
panyam merged 1 commit intoJun 9, 2026
Merged
Conversation
The two checks in required-task-error.ts each verified a distinct normative requirement that sep-2663.yaml already declared, but the check IDs (tasks-required-task-error-code, tasks-required-task-error-data-shape) used the tasks-* flow-gate prefix and went untracked by the traceability manifest. Promote both check IDs to sep-2663-*: - tasks-required-task-error-code → sep-2663-server-returns-32003-when-required - tasks-required-task-error-data-shape → sep-2663-server-returns-32003-data-shape Split the existing YAML entry to mirror the split. The spec sentence glues two observable requirements with a trailing colon (the JSON-RPC code, and the data-shape payload that names the missing extension); each gets its own row so each is verifiable independently. Remove the now-stale tasks-required-task-error-code reference from the sep-2663.yaml flow-gate comment block — that check is no longer a flow-gate. No behavior change. 270/270 vitest still pass.
This was referenced Jun 9, 2026
This was referenced Jun 9, 2026
tasks/capability: anchor extension-advertised check to sep-2663-migrate-from-legacy-capabilities
#13
Merged
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.
First in a series of small per-check ID-rename PRs against PR 262. Each PR promotes a
tasks-*check ID tosep-2663-*(orsep-2243-*etc.) so the conformance traceability manifest can link the check to its anchoring RFC-2119 sentence 1:1.This one covers the two
required-task-error.tschecks that already had a clean YAML match.Summary
Renames
tasks-required-task-error-code→sep-2663-server-returns-32003-when-requiredtasks-required-task-error-data-shape→sep-2663-server-returns-32003-data-shapeYAML split
sep-2663-server-returns-32003-when-requiredrow's text was a single MUST sentence with a trailing colon ("...MUST return an error with the code -32003 (Missing Required Client Capability), indicating the required extension in the error response:"). The colon and the spec's example payload tell us the sentence carries two observable requirements: the JSON-RPC error code, and the data shape that names the missing extension.sep-2663-server-returns-32003-when-required— the JSON-RPC code requirementsep-2663-server-returns-32003-data-shape— the payload shape requirementComment cleanup
tasks-required-task-error-codefrom the flow-gate comment block insep-2663.yaml— it's no longer a flow-gate.Reviewer's guide
src/scenarios/server/tasks/required-task-error.ts:106-107src/scenarios/server/tasks/required-task-error.ts:173-174src/seps/sep-2663.yamlCapability Negotiationsectionsrc/seps/sep-2663.yamlline 154Test plan
npm test— 270/270 passgrepcross-check — everysep-2663-*code ID is now declared insep-2663.yaml