# Both pre-existing fixture bugs, not lifecycle-specific: json-schema-2020-12
# wants a `json_schema_2020_12_tool` fixture neither conformance server
# defines, and resources-templates-read emits a resource-template URI in a
# shape the schema rejects. Reproduce identically on the 2026-07-28 endpoint
# (see conformance-baseline-2026-07-28.yml).
server:
  - json-schema-2020-12:json-schema-2020-12-tool-found
  - resources-templates-read:wire-schema-valid

client:
  - elicitation-sep1034-client-defaults
  - sse-retry
  # The example client doesn't call add_numbers or echo the tool's inputSchema
  # back, so these checks have nothing to exercise.
  - tools_call:tool-add-numbers
  - 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/basic-cimd
  - 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/pre-registration
  - auth/2025-03-26-oauth-metadata-backcompat
  - auth/2025-03-26-oauth-endpoint-fallback
  - auth/offline-access-scope
  - auth/offline-access-not-supported
  - auth/client-credentials-jwt
  - auth/client-credentials-basic
  - auth/cross-app-access-complete-flow