Trim CONTRIBUTING.md per review: restore intro, drop trusted-group mentions

No-Verification-Needed: docs only
Signed-off-by: Max Isbey <224885523+maxisbey@users.noreply.github.com>

Author: maxisbey

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing
 
-Thanks for your interest in the MCP Python SDK. This document explains how the project takes contributions and why, and then how to set up a development environment if you're working on a change we've agreed on.
+Thank you for your interest in contributing to the MCP Python SDK! This document provides guidelines and instructions for contributing.
 
 ## Before You Start
 
@@ -24,21 +24,19 @@ Otherwise a bot labels the PR `missing-issue-link`, leaves a comment explaining
 
 Whether to assign an issue, and to whom, is a [maintainer](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/MAINTAINERS.md#python-sdk) call, and it depends on our capacity at the time as much as on the change itself. Comments that only ask to be assigned don't factor into it, so please skip those (and don't have an agent post them). What does help is engaging with the issue itself: confirming the reproduction, asking about the intended behaviour, or briefly describing the approach you'd take. If you reported the issue and would like to fix it yourself, mention that in the issue — the reporter has first call if we do take an outside PR for it.
 
-Maintainers and a small group of trusted regular contributors are exempt from this check, as are Dependabot and the project's own automation. A maintainer can also let a specific PR through by reopening it.
-
 ### Who We'd Love to Hear From
 
 - **You've hit a real bug.** If you've run into a bug that affects your use case, that's extremely helpful for us to hear about. Talking through why it's a problem for you — rather than just that it is one — helps us both design the right fix and prioritise it, and a minimal reproduction makes it far more likely we can act quickly.
-- **You'd like to learn the codebase or contribute regularly.** You're welcome, with one honest caveat: how much mentoring and review we can offer depends entirely on maintainer capacity, which is very limited at the moment, so replies may be slow and we may not be able to take everything on. The best way to start is by filing and triaging issues well and engaging on existing ones; people who do that consistently are added to the trusted-contributor group and skip the gate. `good first issue` still needs assignment for the same reason — we'd like a short conversation first. You can find us in [#python-sdk-dev on the MCP Contributors Discord](https://discord.gg/6CSzBmMkjX).
-- **You maintain another MCP SDK or work on the spec.** Say so on the issue or in #python-sdk-dev; a maintainer can reopen a specific PR past the gate, and this is exactly who the trusted-contributor group is for.
+- **You'd like to learn the codebase or contribute regularly.** You're welcome, with one honest caveat: how much mentoring and review we can offer depends entirely on maintainer capacity, which is very limited at the moment, so replies may be slow and we may not be able to take everything on. The best way to start is by filing and triaging issues well and engaging on existing ones. `good first issue` still needs assignment — we'd like a short conversation first. You can find us in [#python-sdk-dev on the MCP Contributors Discord](https://discord.gg/6CSzBmMkjX).
+- **You maintain another MCP SDK or work on the spec.** Say so on the issue or in #python-sdk-dev; a maintainer can reopen a specific PR past the gate.
 
 ### AI-Assisted Contributions
 
 We use AI tooling constantly and have no problem with you using it too. What matters is that a person is accountable for the result:
 
 - **Disclose it.** One line in the PR or issue description.
 - **Own it.** You can explain the change and the reasoning in your own words, and when a maintainer asks a question the answer comes from you rather than being pasted from a chat window.
-- **Keep a human in the loop.** Issues, PRs, and comments generated by an agent without a person who has actually hit the problem and read the output may be closed without warning. If you have an agent filing PRs against open issues autonomously, please turn it off for this repository — that pattern is the reason the gate above exists.
+- **Keep a human in the loop.** Issues, PRs, and comments generated by an agent without a person who has actually hit the problem and read the output may be closed without warning. If you have an agent filing PRs against open issues autonomously, please turn it off for this repository.
 - **Keep issues short and factual.** What happened, what you expected, and how to reproduce it.
 
 Undisclosed AI contributions may be closed, and repeated cases can lead to a block from the `modelcontextprotocol` org. The org-wide [AI contribution policy](https://github.com/modelcontextprotocol/modelcontextprotocol/blob/main/AI_POLICY.md) also applies.