Skip to content

exercise-wire: a wire-parity check that fails on #1355, #1515 and #1546 today #1555

Closed

Description

@panyam

Mission #1552's exercise is green today while three of its bugs are live, so it can't tell the mission's progress.

Baseline @ 6d743af3: make testconf-stateless 30/0, make testconf-agents 28/28 and 4/4. Neither drives what the bugs need:

Work

  • 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.
  • A make exercise-wire target running those checks plus testconf testconf-stateless testconf-agents, logged on Mission: a 2026-07-28 client gets spec-correct results from mcpkit on both wires #1552.

Done when

make exercise-wire exists and fails today on #1355, #1515 and #1546, each row naming its ticket.

Activity

  1. added
    P1Next up for an active mission (cap 5 per mission)
    mission_wire_2026_07_28Mission: 2026-07-28 wire correctness on both wires
    on Oct 16, 2026
  2. panyam commented on Oct 18, 2026

    @panyam
    OwnerAuthor

    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.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1Next up for an active mission (cap 5 per mission)mission_wire_2026_07_28Mission: 2026-07-28 wire correctness on both wires

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions