docs: update the README banners

[claude]

Requested by Felix Weinberger · Slack thread

Before: the README opened with launch-week wording and a [!WARNING] about pull requests.

After: the first banner says what main is, where v1 lives and how long it gets fixes, and where to report a problem; the second is a [!NOTE] stating the pull request limit as configured: one open pull request at a time for contributors without write access, drafts not counted.

README only, no changeset.

🤖 Generated with Claude Code

https://claude.ai/code/session_012VRbFCp41otcScXE1YY3es

---

Generated by Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 07c724d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/@modelcontextprotocol/client@2940

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2940

@modelcontextprotocol/core

npm i https://pkg.pr.new/@modelcontextprotocol/core@2940

@modelcontextprotocol/server

npm i https://pkg.pr.new/@modelcontextprotocol/server@2940

@modelcontextprotocol/server-legacy

npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2940

@modelcontextprotocol/express

npm i https://pkg.pr.new/@modelcontextprotocol/express@2940

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2940

@modelcontextprotocol/hono

npm i https://pkg.pr.new/@modelcontextprotocol/hono@2940

@modelcontextprotocol/node

npm i https://pkg.pr.new/@modelcontextprotocol/node@2940

commit: 07c724d

[claude]

I reviewed this PR and found no bugs; since it is a docs-only banner rewrite with two factual claims the repo cannot confirm, a quick maintainer look is still worthwhile.

What was reviewed:

• Link targets: .github/ISSUE_TEMPLATE/v2-feedback.yml, docs/migration/upgrade-to-v2.md, and CONTRIBUTING.md all exist; issues/new/choose is a standard GitHub path.
• The "stable release line" and v1.x branch claims match CONTRIBUTING.md and the pre-existing banner (server package is at 2.3.0).
• The v2 release date (2026-07-27) is new wording and nothing in the repo (changelogs are undated, shallow clone has no tags) confirms it — a maintainer can.
• README.md:12 points to CONTRIBUTING.md right after stating the PR limit, but CONTRIBUTING.md does not mention the limit (it does cover "open an issue first", which is what the sentence is about), so this reads as a soft pointer rather than a contradiction.

Extended reasoning...

The change touches only README.md, rewriting the IMPORTANT and NOTE callout banners at the top; no code, config, or security-sensitive surface is involved. Every link target referenced by the new text resolves to a file or template in the repo, and the branch/stability claims agree with CONTRIBUTING.md. Two points decided defer over approve: the hard release date 2026-07-27 and the "one open PR, drafts excluded" policy are stated as fact but are not verifiable from repository contents, and the file falls under the catch-all CODEOWNERS entry for the typescript-sdk team.