…ashwin/mcp

Refactor to use MCP on client rather than custom protocol

dcc30be Merge pull request modelcontextprotocol#16 from modelcontextprotocol/ashwin/protocol
05a3e54 fix protocol version in client
73c66f4 Merge pull request modelcontextprotocol#13 from modelcontextprotocol/justin/uris
5cad4b5 Merge pull request modelcontextprotocol#12 from modelcontextprotocol/justin/spec-updates
ec96ffc Treat URIs as 'URL' type
f3a8fb8 yarn build
69daade Update to latest protocol version

git-subtree-dir: packages/mcp-typescript
git-subtree-split: dcc30be

…rpus through the era module

The 2026 comparison now pins the 2026-era WIRE artifacts against the anchor
exactly: resultType-required result wrappers (with the SEP-2549 cacheable
fields where the anchor requires them), envelope-required wire-true request
views, the forked Tool/SamplingMessage/ToolResultContent payloads, response
envelopes, and discover. The 72-name burn-down list (with its structurally
permanent envelope stratum) is RETIRED; what remains is a feature-owned
pending map (32 entries, each naming its owner: MRTR #13, subscriptions #14,
validation ladder #8, plus the inlined Error) that is stale-checked in both
directions and reaches zero as the owners land.

The 2025 comparison retires all 20 @ts-expect-error affordances: the
shared-tier adjudications (tool schema typing, capability blobs, the
extensions key, sampling metadata, the PromptArgument/PromptReference title
gap) now live as documented 2025 wire-view types in
wire/rev2025-11-25/wireTypes.ts, compared against the frozen anchor exactly
and in both directions, with key parity included for the previously
suppressed names. The title parse gap is recorded in the project baseline
bug log rather than silently changed.

Corpus: the SEP-2549 pending entries burned (the anchor-exact 2026 forks
accept the array-shape examples — they are real pins now), and 2026 result
fixtures now exercise resultType/envelope requiredness through the era
module.

…rpus through the era module

The 2026 comparison now pins the 2026-era WIRE artifacts against the anchor
exactly: resultType-required result wrappers (with the SEP-2549 cacheable
fields where the anchor requires them), envelope-required wire-true request
views, the forked Tool/SamplingMessage/ToolResultContent payloads, response
envelopes, and discover. The 72-name burn-down list (with its structurally
permanent envelope stratum) is RETIRED; what remains is a feature-owned
pending map (32 entries, each naming its owner: MRTR #13, subscriptions #14,
validation ladder #8, plus the inlined Error) that is stale-checked in both
directions and reaches zero as the owners land.

The 2025 comparison retires all 20 @ts-expect-error affordances: the
shared-tier adjudications (tool schema typing, capability blobs, the
extensions key, sampling metadata, the PromptArgument/PromptReference title
gap) now live as documented 2025 wire-view types in
wire/rev2025-11-25/wireTypes.ts, compared against the frozen anchor exactly
and in both directions, with key parity included for the previously
suppressed names. The title parse gap is recorded in the project baseline
bug log rather than silently changed.

Corpus: the SEP-2549 pending entries burned (the anchor-exact 2026 forks
accept the array-shape examples — they are real pins now), and 2026 result
fixtures now exercise resultType/envelope requiredness through the era
module.

…rpus through the era module

The 2026 comparison now pins the 2026-era WIRE artifacts against the anchor
exactly: resultType-required result wrappers (with the SEP-2549 cacheable
fields where the anchor requires them), envelope-required wire-true request
views, the forked Tool/SamplingMessage/ToolResultContent payloads, response
envelopes, and discover. The 72-name burn-down list (with its structurally
permanent envelope stratum) is RETIRED; what remains is a feature-owned
pending map (32 entries, each naming its owner: MRTR #13, subscriptions #14,
validation ladder #8, plus the inlined Error) that is stale-checked in both
directions and reaches zero as the owners land.

The 2025 comparison retires all 20 @ts-expect-error affordances: the
shared-tier adjudications (tool schema typing, capability blobs, the
extensions key, sampling metadata, the PromptArgument/PromptReference title
gap) now live as documented 2025 wire-view types in
wire/rev2025-11-25/wireTypes.ts, compared against the frozen anchor exactly
and in both directions, with key parity included for the previously
suppressed names. The title parse gap is recorded in the project baseline
bug log rather than silently changed.

Corpus: the SEP-2549 pending entries burned (the anchor-exact 2026 forks
accept the array-shape examples — they are real pins now), and 2026 result
fixtures now exercise resultType/envelope requiredness through the era
module.

…rpus through the era module

The 2026 comparison now pins the 2026-era WIRE artifacts against the anchor
exactly: resultType-required result wrappers (with the SEP-2549 cacheable
fields where the anchor requires them), envelope-required wire-true request
views, the forked Tool/SamplingMessage/ToolResultContent payloads, response
envelopes, and discover. The 72-name burn-down list (with its structurally
permanent envelope stratum) is RETIRED; what remains is a feature-owned
pending map (32 entries, each naming its owner: MRTR #13, subscriptions #14,
validation ladder #8, plus the inlined Error) that is stale-checked in both
directions and reaches zero as the owners land.

The 2025 comparison retires all 20 @ts-expect-error affordances: the
shared-tier adjudications (tool schema typing, capability blobs, the
extensions key, sampling metadata, the PromptArgument/PromptReference title
gap) now live as documented 2025 wire-view types in
wire/rev2025-11-25/wireTypes.ts, compared against the frozen anchor exactly
and in both directions, with key parity included for the previously
suppressed names. The title parse gap is recorded in the project baseline
bug log rather than silently changed.

Corpus: the SEP-2549 pending entries burned (the anchor-exact 2026 forks
accept the array-shape examples — they are real pins now), and 2026 result
fixtures now exercise resultType/envelope requiredness through the era
module.