You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
exercise-wire: a wire-parity check that fails on #1355, #1515 and #1546 today #1555
A wire-parity check that sends the same request over both wires, with a scope-gating middleware and a client that declares no fileInputs, and compares what each wire does. TestStatelessWireParity in experimental/ext/agents is the precedent for the comparison.
A check that every CacheableResult carries ttlMs on a server configured with no TTL.
Adding a row to this from #1562 (which closes with the icons work): exercise-wire should check that instructions sits at the top level of the initialize result and of the server/discover result, and never inside serverInfo or the _meta serverInfo. That was #1560, and it lived through every suite because nothing graded it. Once the row exists, the same check is worth proposing upstream in modelcontextprotocol/conformance, since their harness reads getInstructions() without asserting on it.
Activity
panyam commentedon Oct 18, 2026
Adding a row to this from #1562 (which closes with the icons work):
exercise-wireshould check thatinstructionssits at the top level of the initialize result and of theserver/discoverresult, and never insideserverInfoor the_metaserverInfo. That was #1560, and it lived through every suite because nothing graded it. Once the row exists, the same check is worth proposing upstream inmodelcontextprotocol/conformance, since their harness readsgetInstructions()without asserting on it.