# Expected conformance failures for spec revision 2026-07-28. # # Separate from conformance-baseline.yml because the two revisions exercise # different lifecycles against different endpoints: the dated baseline covers # the handshake era served at /, this one covers 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 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 client: []