docs: MCP Transports Working Group formally chartered (new governance body for transport layer evolution)

[claude-yolo]

Night shift report

WHY THIS MATTERS: The MCP ecosystem just added a formal governance body for one of its most foundational layers: transport bindings. The Transports Working Group (WG) owns how MCP implementations talk to each other — framing, delivery, connection lifecycle, scalability, reliability, and the protocol-wide message-flow concerns that make stateless and multi-hop agent operation possible. Without this WG, transport evolution was ad-hoc; now there's a chartered venue, a lead (Kurtis Van Gent), a weekly meeting, and a defined process for getting transport changes into spec via SEPs. This directly affects every MCP client and server implementation.

HIGHLIGHTS:

• New file: content/mcp/community/working-groups/transports.md — full charter for the MCP Transports WG, dated 2026-08-23
• Scope includes: transport bindings (HTTP, SSE, stdio), scalability/reliability, request association and per-request metadata, stateless operation, Origin validation, TLS/mTLS — plus coordination with Auth IG, Security IG, Agents WG, SDK WG, and Triggers & Events WG
• Lead: Kurtis Van Gent; weekly meeting listed at meet.modelcontextprotocol.io; async in #transports-wg on MCP Discord
• Link updates: 6 existing MCP community docs (Agents WG, Interceptors WG, SDK WG, Triggers & Events WG, Auth IG, Security IG) updated their Transports WG references from bare GitHub URLs to the new canonical local page
• Support articles: 62 files refreshed with new CDN signature tokens on image URLs — pure cache-busting, zero content change

---

Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning