927ccdd161
## Motivation and Context The `json-schema-2020-12-preservation` client scenario (SEP-1613, SEP-2106; not scored for 2026-07-28, as it was added after the requirements anchor) failed only because the conformance client had no branch for it: an unknown scenario aborts after connecting, so the harness never observed a `tools/list` nor the schema echo it diffs. The client itself already preserves the vocabulary the scenario checks (`$schema`, `$defs` with `$anchor`, `$ref`, `allOf`/`anyOf`, `if`/`then`/`else`, `additionalProperties`): `Client::Tool#input_schema` is the parsed `tools/list` response untouched, with no dereferencing, validation-time rewriting, or keyword stripping, the same fixture-echo approach the TypeScript and Python conformance clients take. The new branch lists the tools and echoes the focal tool's observed `inputSchema` verbatim through `json_schema_echo`, and the expected-failures entry is removed. ## How Has This Been Tested? The scenario passes 9/9 at its default 2025-11-25 wire. On top of the modern-lifecycle client selection (the SEP-2322 driver branch) it also passes 9/9 at `--spec-version 2026-07-28`, where the SEP-2106 keyword checks are failure-gated instead of skipped. `bundle exec rake` is green, with the conformance task passing its baseline check on both legs, and RuboCop reports no offenses. ## Breaking Changes None. The change is confined to the conformance client and its baseline; the shipped gem is untouched.
19 lines
870 B
YAML
19 lines
870 B
YAML
server: []
|
|
client:
|
|
# Pending client-side support for the 2026-07-28 stateless lifecycle: the conformance client
|
|
# still connects through the legacy handshake and has no SEP-2322 MRTR driver yet.
|
|
- request-metadata
|
|
- sep-2322-client-request-state
|
|
# SEP-2243 client-side custom-header mirroring and invalid-tool header gating
|
|
# are not implemented in `MCP::Client::HTTP` yet.
|
|
- http-custom-headers
|
|
- http-invalid-tool-headers
|
|
# Client-side JSON Schema handling: `$ref` values must reach the caller unresolved,
|
|
# and the conformance client does not run the scenario over the modern lifecycle yet.
|
|
- json-schema-ref-no-deref
|
|
# Unimplemented authorization extensions.
|
|
- auth/dpop
|
|
- auth/dpop-nonce
|
|
- auth/wif-jwt-bearer
|
|
# Fails one check added to the suite after the 0.2.0-alpha.10 requirements anchor.
|
|
- auth/authorization-server-migration
|