28 lines
1.4 KiB
YAML
28 lines
1.4 KiB
YAML
# Conformance scenarios not yet passing against the Python SDK on main.
|
|
# CI exits 0 if only these fail, exits 1 on unexpected failures or stale entries.
|
|
#
|
|
# Baseline established against the harness pinned via CONFORMANCE_PKG in
|
|
# .github/workflows/conformance.yml. New conformance releases are adopted by
|
|
# deliberately bumping that pin and reconciling both this file and
|
|
# expected-failures.2026-07-28.yml in the same change.
|
|
#
|
|
# Entries are grouped by SEP. As each SEP lands in the SDK the corresponding
|
|
# scenarios start passing and MUST be removed from this list (the runner fails
|
|
# on stale entries), so the baseline burns down per milestone.
|
|
|
|
client:
|
|
# --- Draft-spec scenarios (in `--suite draft`, also part of `--suite all`) ---
|
|
# SEP-2243 (HTTP standardization): no client Mcp-Param-* support yet — needs the
|
|
# tool-schema-cache vs per-call tool_definition design (S8).
|
|
- http-custom-headers
|
|
|
|
# --- Pre-existing scenarios that fail on checks added after conformance 0.1.15 ---
|
|
# SEP-990 (enterprise-managed authorization extension): no fixture handler /
|
|
# client support for the token-exchange + JWT bearer flow.
|
|
- auth/enterprise-managed-authorization
|
|
|
|
server:
|
|
# --- Draft-spec scenarios (in `--suite draft`; the `active` suite is green) ---
|
|
# SEP-2322 (multi-round-trip requests / IncompleteResult): the prompt pipeline
|
|
# cannot return InputRequiredResult from MCPServer yet (tools/call can).
|
|
- input-required-result-non-tool-request
|