Skip to content

feat: add sep-2575.yaml requirement traceability#273

Open
pcarleton wants to merge 1 commit into
mainfrom
paulc/sep-2575-traceability
Open

feat: add sep-2575.yaml requirement traceability#273
pcarleton wants to merge 1 commit into
mainfrom
paulc/sep-2575-traceability

Conversation

@pcarleton
Copy link
Copy Markdown
Member

Adds the SEP-2484 requirement-traceability YAML for SEP-2575 (stateless MCP).

Maps the 32 new/changed normative requirements introduced by SEP-2575 to conformance check IDs, plus 3 excluded: rows (client-internal demux, ack-filter handling, architectural state-identifier guidance).

Filtering note

SEP-2575 substantially rewrote transports.mdx and lifecycle.mdx, so the raw added-lines diff contains ~60 RFC-2119 sentences. ~28 of those are pre-existing text that was rewrapped (Origin validation, x-mcp-header, Accept header, X-Accel-Buffering, custom transports, stdio stdout/stdin, shutdown sequence) — confirmed by matching against the deletion side of the spec diff. Those are not in this YAML since they aren't introduced by this SEP.

Breakdown

Generated via /new-sep 2575.

Maps the 32 new/changed normative requirements introduced by SEP-2575
(stateless MCP) to conformance check IDs, plus 3 excluded rows.

Filtered out ~28 pre-existing requirements that were rewrapped in the
transports.mdx/lifecycle.mdx rewrite (Origin header, x-mcp-header, etc.)
by cross-referencing the deletion side of the spec diff.

Reference for #270 (client) and #271 (server).
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 13, 2026

Open in StackBlitz

npx https://pkg.pr.new/@modelcontextprotocol/conformance@273

commit: 576e5d4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant