refactor: auto-close PRs that skip the intake requirements

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,75 @@
+name: Bug report
+description: Report a bug in the Go MCP SDK
+type: Bug
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to report a bug. Keep it short: what happened, what you expected, and how to reproduce it.
+
+        Every box in the checklist below should be ticked; see [CONTRIBUTING.md](https://github.com/modelcontextprotocol/go-sdk/blob/main/CONTRIBUTING.md#how-issues-get-in). Questions belong in [Discussions](https://github.com/modelcontextprotocol/go-sdk/discussions), and security vulnerabilities must be [reported privately](https://github.com/modelcontextprotocol/go-sdk/blob/main/SECURITY.md).
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      description: Only tick a box if it's true; false statements may get you blocked from the repository.
+      options:
+        - label: "I searched the existing issues, and this has not been reported before."
+          required: false
+        - label: "This is a real problem that I ran into myself, using the latest release of the SDK."
+          required: false
+        - label: "I ran into it in a production system, not in a toy example, a benchmark, or an automated or AI-driven scan of the code."
+          required: false
+        - label: "I (a human) examined the relevant SDK code, and wrote or reviewed every line of this report. It is not unreviewed AI output."
+          required: false
+        - label: "This report is brief and concise, and sticks to the facts needed to understand the problem."
+          required: false
+
+  - type: textarea
+    id: description
+    attributes:
+      label: What happened?
+      description: What you did, what you saw, and what you expected to see instead.
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproduction
+    attributes:
+      label: How to reproduce
+      description: The smallest program or the exact steps that trigger the problem with the latest release.
+      render: go
+    validations:
+      required: true
+
+  - type: input
+    id: production
+    attributes:
+      label: Where did you hit this?
+      description: One line on the system you hit it in, and how it uses the SDK.
+    validations:
+      required: false
+
+  - type: input
+    id: sdk-version
+    attributes:
+      label: Go MCP SDK version
+    validations:
+      required: true
+
+  - type: input
+    id: go-version
+    attributes:
+      label: Go version
+      description: Output of `go version`.
+    validations:
+      required: true
+
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: Only the lines relevant to the problem.
+      render: text

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Questions and design discussion
+    url: https://github.com/modelcontextprotocol/go-sdk/discussions
+    about: Ask questions and discuss ideas in GitHub Discussions.
+  - name: Security vulnerabilities
+    url: https://github.com/modelcontextprotocol/go-sdk/blob/main/SECURITY.md
+    about: Report vulnerabilities privately, never in a public issue.

.github/ISSUE_TEMPLATE/enhancement.yml

@@ -0,0 +1,50 @@
+name: Enhancement
+description: Suggest an improvement to the Go MCP SDK
+type: Enhancement
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to suggest an improvement. Keep it short: what you're trying to do, what's stopping you, and what would help.
+
+        Every box in the checklist below should be ticked; see [CONTRIBUTING.md](https://github.com/modelcontextprotocol/go-sdk/blob/main/CONTRIBUTING.md#how-issues-get-in). Changes to the exported API go through the [proposal process](https://github.com/modelcontextprotocol/go-sdk/blob/main/CONTRIBUTING.md#proposals). Open-ended ideas belong in [Discussions](https://github.com/modelcontextprotocol/go-sdk/discussions).
+
+  - type: checkboxes
+    id: checklist
+    attributes:
+      label: Checklist
+      description: Only tick a box if it's true; false statements may get you blocked from the repository.
+      options:
+        - label: "I searched the existing issues, and this has not been reported before."
+          required: false
+        - label: "This is a real problem that I ran into myself, using the latest release of the SDK."
+          required: false
+        - label: "I ran into it in a production system, not in a toy example, a benchmark, or an automated or AI-driven scan of the code."
+          required: false
+        - label: "I (a human) examined the relevant SDK code, and wrote or reviewed every line of this report. It is not unreviewed AI output."
+          required: false
+        - label: "This report is brief and concise, and sticks to the facts needed to understand the problem."
+          required: false
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem are you trying to solve?
+      description: What you're trying to do, and what in the SDK is stopping you.
+    validations:
+      required: true
+
+  - type: input
+    id: production
+    attributes:
+      label: Where did you hit this?
+      description: One line on the system you hit it in, and how it uses the SDK.
+    validations:
+      required: false
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: What would help?
+      description: The change you'd like, and any alternatives you considered.

.github/pull_request_template.md

@@ -1,3 +1,9 @@
+<!--
+Pull requests from outside the maintainer team need to link an open issue that
+a maintainer has assigned to you (or one labeled `help wanted`); others are
+closed automatically until that's in place. See CONTRIBUTING.md for details.
+-->
+
 ### PR Guideline
 
 Typically, PRs should consist of a single commit, and so should generally follow
@@ -26,3 +32,7 @@ Additionally:
 - For a pervasive change, use "all" in the title instead of a package name.
 - The PR description should provide context (why this change?) and describe the changes
   at a high level. Changes that are obvious from the diffs don't need to be mentioned.
+- Link the issue with `Fixes #N`, or `Updates #N` for a partial fix. You must be
+  assigned to that issue (or it must be labeled `help wanted`).
+- Disclose any AI assistance in one line, and be ready to explain the change in
+  your own words.