Split draft-spec scenarios into their own suite#317
Merged
Conversation
- add --suite draft to the server command, selecting scenarios whose source.introducedIn is the draft protocol version - exclude draft scenarios from the default active suite until the draft spec is published as a dated release - derive the client command's draft suite from source.introducedIn so the non-auth draft scenarios (SEP-2243/2575/2322/2106) are included alongside the auth ones - keep everything-server self-test coverage for draft scenarios in all-scenarios.test.ts (active + non-pending draft) - document available suites in the README and add suite-membership tests
- SEP-986: SEP/SEP-986.md no longer exists in the spec repo; point at the Tool Names section of the published 2025-11-25 tools page instead - SEP-990: the ext-auth spec file is enterprise-managed-authorization.mdx, not enterprise-oauth.mdx Fixes #313
commit: |
This was referenced May 26, 2026
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.
What
Commit 1 — draft suite split
--suite draftto theservercommand: every scenario whosesource.introducedInis the draft protocol version (currently 19 scenarios: SEP-2575 stateless, SEP-2549 caching, SEP-2243 header validation, SEP-2322 input-required-result, SEP-2164).draftsuite is now derived fromsource.introducedIninstead of the hand-maintained auth-only list, so the non-auth draft scenarios (SEP-2243/2575/2322/2106) are included alongside the auth ones (17 scenarios).activeserver suite until the draft is published as a dated release; they remain selectable via--suite draftand--suite all.all-scenarios.test.tsstill exercises the draft scenarios against the everything-server (active + non-pending draft), so self-test coverage is unchanged..claude/,.sdk-under-test/) from vitest/prettier so stray local checkouts can't pollute runs.Commit 2 — spec reference URL fixes (fixes #313)
SEP/SEP-986.mdpath no longer exists in the spec repo).enterprise-managed-authorization.mdx, the actual filename in ext-auth.Relationship to
--spec-version--spec-versionremains the cumulative filter ("run everything that applies to the spec revision I target");--suite draftselects only the draft delta. They compose:--suite all --spec-version draftis roughly the previous behavior.Behavior change: the server command's default
activesuite no longer includes draft scenarios, soserver --url … --spec-version draftwithout--suiteno longer runs them — use--suite draft(just the delta) or--suite all --spec-version draft(everything applicable to a draft implementation). Draft scenarios also stop counting toward tier-check, which keys offactive.Test plan
npm test— full suite greenspec-version.test.tscases assert every draft-introduced scenario is selected by its draft suite and that none remain inactivenode dist/index.js server --suite draft --url …runs the 19 draft scenarios;client --suite draftthe 17 client-side ones