78a8926f17- Rename conformance-baseline.yml to conformance-baseline-2025-11-25.yml so both baseline files carry their spec revision symmetrically, and bring conformance-server/conformance-client up to the same rigor (--suite all, pinned CONFORMANCE, baseline check) as the draft targets - score.php now takes a required spec-version and writes <suite>-conformance-<spec-version>.json, so 2025-11-25 and 2026-07-28 each get their own badge instead of only the dated one - conformance-weekly.yaml generates and publishes badges for both matrix entries instead of gating on 2025-11-25 only, and drops the now-stale unversioned badge files from the badges branch - README shows all four badges alongside the existing packagist/CI/PHP version/license row - Trimmed workflow comments to the minimum needed
68 lines
2.7 KiB
YAML
68 lines
2.7 KiB
YAML
# Expected conformance failures for spec revision 2026-07-28.
|
|
#
|
|
# Separate from conformance-baseline-2025-11-25.yml because the two revisions
|
|
# exercise different lifecycles against different endpoints: the other file
|
|
# covers the handshake era served at /, this one the modern (SEP-2575) era
|
|
# served at /stateless.
|
|
#
|
|
# Entries are per-check (scenario:check-id) rather than whole scenarios, so a
|
|
# scenario that is mostly conformant keeps reporting the parts that work and a
|
|
# new regression inside it still fails the run.
|
|
#
|
|
# Run with:
|
|
# make conformance-draft-server
|
|
# make conformance-draft-client
|
|
|
|
server:
|
|
# --- Pre-existing, not lifecycle-specific ----------------------------------
|
|
# Neither is caused by (or fixable in) the modern lifecycle; both reproduce
|
|
# on the handshake endpoint. Listed so the draft run is honest.
|
|
#
|
|
# json-schema-2020-12 wants a `json_schema_2020_12_tool` fixture that neither
|
|
# conformance server defines, so the scenario has nothing to exercise.
|
|
# resources-templates-read is the single remaining wire-schema failure: the
|
|
# fixture emits a resource-template URI in a shape the schema rejects, on
|
|
# both revisions.
|
|
- json-schema-2020-12:json-schema-2020-12-tool-found
|
|
- resources-templates-read:wire-schema-valid
|
|
|
|
# The client does not speak 2026-07-28 at all yet: it still opens with
|
|
# `initialize` regardless of revision, so it never reaches the stateless wire
|
|
# (no per-request `_meta`, no Mcp-Method/Mcp-Name headers, no client-side
|
|
# requestState) — and separately, the SDK ships no OAuth client, so every
|
|
# scenario driving an authorization flow has nothing to exercise.
|
|
client:
|
|
- request-metadata
|
|
- http-standard-headers
|
|
- http-custom-headers
|
|
- http-invalid-tool-headers:sep-2243-invalid-tool-tools-list-gate
|
|
- http-invalid-tool-headers:sep-2243-client-reject-invalid-tool
|
|
- sep-2322-client-request-state
|
|
- tools_call:tool-add-numbers
|
|
- json-schema-2020-12-preservation:json-schema-2020-12-client-tool-found
|
|
- json-schema-2020-12-preservation:json-schema-2020-12-client-echo-completed
|
|
|
|
- auth/metadata-default
|
|
- auth/metadata-var1
|
|
- auth/metadata-var2
|
|
- auth/metadata-var3
|
|
- auth/metadata-issuer-mismatch
|
|
- auth/basic-cimd
|
|
- auth/pre-registration
|
|
- auth/scope-from-www-authenticate
|
|
- auth/scope-from-scopes-supported
|
|
- auth/scope-omitted-when-undefined
|
|
- auth/scope-step-up
|
|
- auth/scope-retry-limit
|
|
- auth/token-endpoint-auth-basic
|
|
- auth/token-endpoint-auth-post
|
|
- auth/token-endpoint-auth-none
|
|
- auth/offline-access-scope
|
|
- auth/offline-access-not-supported
|
|
- auth/authorization-server-migration:sep-2352-reregister-on-as-change
|
|
- auth/iss-supported
|
|
- auth/iss-not-advertised
|
|
- auth/iss-supported-missing
|
|
- auth/iss-wrong-issuer
|
|
- auth/iss-unexpected
|
|
- auth/iss-normalized
|