test(conformance): baseline server-stateless WARNING-only sep-2575 SHOULDs (fixture armed in follow-up)

Author: felixweinberger

test/conformance/expected-failures.2026-07-28.yaml

@@ -67,6 +67,10 @@ client:
 
 server:
     # --- Carried-forward scenarios (also run by the 2025 legs) ---
+    # WARNING-only: see the matching entry in expected-failures.yaml — the
+    # sep-2575 list_changed-on-listen SHOULD checks; fixture armed in a
+    # follow-up change.
+    - server-stateless
     # Pre-existing fixture/baseline bug: the fixture tool's schema is a plain
     # Zod object with none of the JSON Schema 2020-12 keywords the scenario
     # checks; it fails identically at 2025 in `--suite all` (not a 2026-path

test/conformance/expected-failures.yaml

@@ -49,6 +49,14 @@ client:
 
 server:
     # --- Draft-spec scenarios (in `--suite draft`; the default `active` suite is green) ---
+    # WARNING-only: with the listChanged capability now advertised in
+    # server/discover, server-stateless runs three additional SHOULD-level
+    # checks (sep-2575-server-sends-{tools,prompts,resources}-list-changed-on-
+    # subscription) that the conformance fixture cannot yet satisfy because it
+    # is not wired to publish list_changed events to listen streams. The
+    # fixture is armed in a follow-up change, after which this entry burns
+    # down.
+    - server-stateless
     # SEP-2243 (HTTP header standardization): the reject cells the SDK does
     # answer now use -32001 (HeaderMismatch), but missing-header enforcement
     # (Mcp-Method, Mcp-Name) and the Mcp-Name cross-check are not implemented,