You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1d4d2d3
Browse filesBrowse the repository at this point in the historyBrowse files
feat: add specVersion classification to conformance scenarios
Add a SpecVersion type to Scenario and ClientScenario interfaces, enabling
SDK maintainers and the tier-check scoring logic to filter tests by target
spec version.
- Add SpecVersion union type ('2025-03-26' | '2025-06-18' | '2025-11-25' | 'draft' | 'extension')
- Tag all 32 server scenarios and 23 client scenarios with their specVersion
- Add helper functions: listScenariosForSpec, listScenariosUpToSpec, etc.
- Add --spec-version CLI filter to client, server, and list commands
- Date versions are cumulative (2025-11-25 includes all prior)
- draft/extension are exact-match only
- Show [specVersion] tags in list output
- Attach specVersion to tier-check detail entries with per-version breakdown
- Update tier-audit skill docs to reflect new spec version metadata
Copy file name to clipboardExpand all lines: .claude/skills/mcp-sdk-tier-audit/SKILL.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -66,7 +66,9 @@ npm run --silent tier-check -- \
66
66
67
67
If no client-cmd was detected, omit the `--client-cmd` flag (client conformance will be skipped).
68
68
69
-
The CLI output includes server conformance pass rate, client conformance pass rate, issue triage compliance, P0 resolution times, label taxonomy, stable release status, policy signal files, and spec tracking gap. Parse the JSON output to feed into Step 4.
69
+
The CLI output includes server conformance pass rate, client conformance pass rate (with per-spec-version breakdown), issue triage compliance, P0 resolution times, label taxonomy, stable release status, policy signal files, and spec tracking gap. Parse the JSON output to feed into Step 4.
70
+
71
+
The conformance results now include a `specVersion` field on each detail entry, enabling per-version pass rate analysis. The `list` command also shows spec version tags: `node dist/index.js list` shows `[2025-06-18]`, `[2025-11-25]`, `[draft]`, or `[extension]` next to each scenario.
70
72
71
73
### Conformance Baseline Check
72
74
@@ -200,9 +202,12 @@ After the subagents finish, output a short executive summary directly to the use
The `--spec-version` CLI flag filters scenarios cumulatively for date versions:
46
+
47
+
-`--spec-version 2025-06-18` includes `2025-03-26` + `2025-06-18` scenarios
48
+
-`--spec-version 2025-11-25` includes all three dated versions
49
+
-`--spec-version draft` or `--spec-version extension` returns only exact matches
50
+
51
+
The tier-check CLI output includes a per-version breakdown alongside the aggregate pass rate, and groups `draft`/`extension` results separately as informational.
'Tests OAuth flow with Client ID Metadata Documents (SEP-991/URL-based client IDs). Server advertises client_id_metadata_document_supported=true and client should use URL as client_id instead of DCR.';
0 commit comments