Address review: retired-feature wording, lock description, roadmap tracking claim

No-Verification-Needed: doc-only change

Author: maxisbey

RELEASE.md

@@ -10,7 +10,7 @@ move; this is the mechanics.
    `[tool.hatch.metadata.hooks.uv-dynamic-versioning].dependencies`.
 2. Regenerate the lock with `uv lock` (or `uv lock --upgrade-package <package>`
    to move just that package's locked version). The committed `uv.lock` is a
-   normal, newest-allowed resolution; the `lowest-direct` resolution that
+   normal (default-strategy) resolution; the `lowest-direct` resolution that
    proves the floors still work is applied only by its CI matrix leg at test
    time and is never committed.
 

ROADMAP.md

@@ -8,7 +8,7 @@ v2 implements the [2026-07-28 specification](https://modelcontextprotocol.io/spe
 
 ## Not yet implemented
 
-Extensions and optional client-auth mechanisms not yet implemented are tracked in the issue tracker; those the conformance suite already exercises also appear in its expected-failures baseline, [`.github/actions/conformance/expected-failures.yml`](.github/actions/conformance/expected-failures.yml), which burns down as each lands. The main ones:
+Of the extensions and optional client-auth mechanisms not yet implemented, those the conformance suite already exercises appear in its expected-failures baseline, [`.github/actions/conformance/expected-failures.yml`](.github/actions/conformance/expected-failures.yml), which burns down as each lands. The main ones:
 
 * **Tasks extension** (`io.modelcontextprotocol/tasks`, [SEP-2663](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/seps/2663-tasks-extension.md)) — deferred at 2.0 because the 2026-07-28 design is wire-incompatible with the earlier in-core Tasks; tracked in [#2806](https://github.com/modelcontextprotocol/python-sdk/issues/2806).
 * **DPoP-bound access tokens** ([SEP-1932](https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1932)) in the OAuth client.

VERSIONING.md

@@ -22,7 +22,7 @@ Allowed in a minor:
 
 * additions — functions, defaulted parameters, classes, fields, enum members,
 * changes to provisional or experimental APIs,
-* new deprecation warnings, and the eventual removal of protocol features the specification has retired,
+* new deprecation warnings, and retired protocol features ceasing to work on connections that negotiate a revision without them (their Python names stay, deprecated, until a major),
 * raising a dependency floor the SDK needs (see the [dependency policy](DEPENDENCY_POLICY.md)) when the dependency's changes don't reach you through the SDK's API, or dropping a Python version after its upstream end-of-life — both called out in the release notes,
 * bug fixes, including ones that make the SDK match its documented or specified behavior.