Retire wording tied to pre-2.0 milestones
Several docstrings, comments, and story READMEs still describe work as "expected before v2 is final", "planned before beta", or "revisit before beta" — milestones that passed when 2.0 shipped.
Motivation and Context
The provisional middleware/dispatcher surface stays provisional, but the caveat now says what it means going forward — "may change in a 2.x minor release" — instead of pointing at a milestone in the past. The stale beta TODOs on the stories are dropped, and the middleware story is corrected: it claimed MCPServer has no public middleware accessor yet, but MCPServer.middleware (and the middleware= constructor argument) shipped in #3201.
How Has This Been Tested?
Wording only. ruff and pyright clean via pre-commit.
Breaking Changes
None.
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
- Documentation update
Checklist
- I have read the MCP Documentation
- My code follows the repository's style guidelines
- New and existing tests pass locally
- I have added appropriate error handling
- I have added or updated documentation as needed
Additional context
Two adjacent notes were left alone on purpose: stories/error_handling ("the contract is under design") and stories/README.md ("hosting surface that are still moving") — neither names a milestone, and whether they still hold is a separate call.