add MCP conformance tests to goose CI (combines #10800 + #10801) (#10940)

Signed-off-by: Jack Amadeo <jackamadeo@squareup.com> Co-authored-by: Jack Amadeo <jackamadeo@squareup.com>
2026-08-20 21:51:53 +00:00
parent 810bb68fff
commit 2f5169af35
18 changed files with 1380 additions and 126 deletions
@@ -0,0 +1,13 @@
+# MCP conformance baseline: known-failing client scenarios.
+#
+# Spec version:        2025-11-25
+# Conformance version: 0.1.16
+#
+# Scenarios listed here are allowed to fail (or emit warnings) without failing
+# CI. The conformance runner will error if any of these scenarios start passing
+# (stale entry) or if a scenario not listed here fails (unexpected failure), so
+# keep this list in sync as behavior changes.
+#
+# All scenarios currently pass; keep this file so CI flags any regression as an
+# unexpected failure.
+client: []
@@ -0,0 +1,13 @@
+# MCP conformance baseline: known-failing client scenarios.
+#
+# Spec version:        2025-11-25
+# Conformance version: 0.2.0-alpha.10
+#
+# Scenarios listed here are allowed to fail (or emit warnings) without failing
+# CI. The conformance runner will error if any of these scenarios start passing
+# (stale entry) or if a scenario not listed here fails (unexpected failure), so
+# keep this list in sync as behavior changes.
+#
+# All scenarios currently pass; keep this file so CI flags any regression as an
+# unexpected failure.
+client: []
@@ -0,0 +1,13 @@
+# MCP conformance baseline: known-failing client scenarios.
+#
+# Spec version:        2026-07-28
+# Conformance version: 0.2.0-alpha.10
+#
+# Scenarios listed here are allowed to fail (or emit warnings) without failing
+# CI. The conformance runner will error if any of these scenarios start passing
+# (stale entry) or if a scenario not listed here fails (unexpected failure), so
+# keep this list in sync as behavior changes.
+#
+# All scenarios currently pass; keep this file so CI flags any regression as an
+# unexpected failure.
+client: []