Merge branch 'main' into Matvey-Kuk/add-archestra-mcp-apps-support

Author: Matvey-Kuk

docs/clients.mdx

@@ -676,7 +676,7 @@ ChatFrame is a cross-platform desktop chatbot that unifies access to multiple AI
 <McpClient
   name="ChatGPT"
   homepage="https://chatgpt.com"
-  supports="Tools, Apps, DCR"
+  supports="Tools, Apps, DCR, CIMD"
   instructions="https://platform.openai.com/docs/guides/developer-mode"
 >
 
@@ -1059,6 +1059,25 @@ Genkit is a cross-language SDK for building and integrating GenAI features into
 
 </McpClient>
 
+<McpClient
+  name="GitHub Copilot CLI"
+  homepage="https://github.com/features/copilot/cli/"
+  supports="Tools, Discovery, Instructions, Sampling, Elicitation, DCR, OAuth Client Credentials, Tasks"
+  instructions="https://docs.github.com/copilot/how-tos/use-copilot-agents/use-copilot-cli#add-an-mcp-server"
+>
+
+GitHub Copilot CLI runs a GitHub-native agent in your terminal that works directly with your issues and pull requests, executes across a `/fleet` of parallelized subagents, and carries you from `/plan` to merged code.
+
+**Key features:**
+
+- Work with issues, branches, and pull requests through GitHub's native `/mcp` server.
+- Use `/model` and `/fleet` to execute in parallel or run multiple models at once.
+- Start with a `/plan`, refine work in your `/IDE`, and ship a pull request on GitHub.
+- Extend Copilot CLI with custom MCP server integrations, skills, and plugins.
+- Runs on macOS, Linux, and Windows and inherits organization Copilot policies and governance settings.
+
+</McpClient>
+
 <McpClient
   name="GitHub Copilot coding agent"
   homepage="https://docs.github.com/en/copilot/concepts/about-copilot-coding-agent"

docs/community/sep-guidelines.mdx

@@ -64,7 +64,7 @@ flowchart TD
     InReview --> Decision
     Decision --> Accepted
     Decision --> Rejected
-    Accepted -->|"Reference implementation complete"| Final
+    Accepted -->|"Reference implementation +<br/>conformance test complete"| Final
 ```
 
 ### Step-by-Step Process
@@ -97,18 +97,18 @@ flowchart TD
 
 8. **Resolution**: The SEP may be `accepted`, `rejected`, or returned for revision. The sponsor updates the status.
 
-9. **Finalization**: Once accepted, the reference implementation must be completed. When complete and incorporated into the specification, the sponsor updates the status to `final`.
+9. **Finalization**: Once accepted, the reference implementation must be completed. For Standards Track SEPs with observable protocol behavior, a [conformance test](#conformance-test-requirement) must also be merged. When complete and incorporated into the specification, the sponsor updates the status to `final`.
 
 ### SEP Statuses
 
 | Status       | Meaning                                          |
 | ------------ | ------------------------------------------------ |
 | `draft`      | Has a sponsor, undergoing informal review        |
 | `in-review`  | Ready for formal Core Maintainer review          |
-| `accepted`   | Approved, awaiting reference implementation      |
+| `accepted`   | Approved, awaiting implementation + conformance  |
 | `rejected`   | Declined by Core Maintainers                     |
 | `withdrawn`  | Author withdrew the proposal                     |
-| `final`      | Complete with reference implementation           |
+| `final`      | Complete with implementation and conformance     |
 | `superseded` | Replaced by a newer SEP                          |
 | `dormant`    | No sponsor found within 6 months; can be revived |
 
@@ -214,6 +214,31 @@ For a SEP to be accepted it must meet these criteria:
 
 Once a SEP has been accepted, the reference implementation must be completed. When complete and incorporated into the main repository, the status changes to "Final".
 
+## Conformance Test Requirement
+
+For **Standards Track SEPs** that introduce or modify observable protocol behavior, a conformance scenario must be merged into the [conformance repository](https://github.com/modelcontextprotocol/conformance) before the SEP can reach `Final` status.
+
+**What's required:**
+
+- A conformance scenario tagged with the SEP number, targeting the conformance repository's draft spec-version tag
+- A structured traceability file (`sep-NNNN.yaml`) mapping each MUST/MUST NOT and SHOULD/SHOULD NOT in the SEP's Specification section to either a check ID or a documented exclusion (with a tracking issue if it's a framework gap)
+- The scenario passes against the SEP's reference implementation
+
+**What's exempt:**
+
+- Process and Informational SEPs
+- Standards Track SEPs with no observable protocol behavior (documentation clarifications, non-validating schema annotations, implementation-hardening recommendations)
+
+**Who does what:**
+
+- The **sponsor** ensures a conformance scenario is written and verifies the traceability file covers every MUST/MUST NOT and SHOULD/SHOULD NOT in the SEP
+- The **conformance repository maintainers** review the scenario PR for technical correctness
+- The test **author** can be anyone: the SEP author, an SDK maintainer, a community contributor
+
+Writing a conformance scenario during SEP drafting (before Core Maintainer review) is encouraged but not required, since it often surfaces ambiguities in normative language that are cheaper to fix early.
+
+See [SEP-2484](/seps/2484-conformance-tests-required-for-final-seps) for the full specification including the traceability file format and dispute process.
+
 ## After Rejection
 
 Rejection is not permanent. You can:

docs/docs.json

@@ -99,6 +99,12 @@
               "extensions/auth/oauth-client-credentials",
               "extensions/auth/enterprise-managed-authorization"
             ]
+          },
+          {
+            "group": "MCP Tasks",
+            "pages": [
+              "extensions/tasks/overview"
+            ]
           }
         ]
       },
@@ -322,9 +328,8 @@
                     "group": "Utilities",
                     "pages": [
                       "specification/draft/basic/utilities/cancellation",
-                      "specification/draft/basic/utilities/ping",
                       "specification/draft/basic/utilities/progress",
-                      "specification/draft/basic/utilities/tasks",
+                      "specification/draft/basic/utilities/subscriptions",
                       "specification/draft/basic/utilities/mrtr"
                     ]
                   }
@@ -342,12 +347,14 @@
                 "group": "Server Features",
                 "pages": [
                   "specification/draft/server/index",
+                  "specification/draft/server/discover",
                   "specification/draft/server/prompts",
                   "specification/draft/server/resources",
                   "specification/draft/server/tools",
                   {
                     "group": "Utilities",
                     "pages": [
+                      "specification/draft/server/utilities/caching",
                       "specification/draft/server/utilities/completion",
                       "specification/draft/server/utilities/logging",
                       "specification/draft/server/utilities/pagination"
@@ -421,20 +428,34 @@
               "seps/2148-contributor-ladder",
               "seps/2149-working-group-charter-template",
               "seps/2243-http-standardization",
-              "seps/2567-sessionless-mcp"
+              "seps/2260-Require-Server-requests-to-be-associated-with-Client-requests",
+              "seps/2567-sessionless-mcp",
+              "seps/2577-deprecate-roots-sampling-and-logging",
+              "seps/2663-tasks-extension"
             ]
           },
           {
             "group": "Accepted",
             "pages": [
               "seps/2207-oidc-refresh-token-guidance",
-              "seps/2260-Require-Server-requests-to-be-associated-with-Client-requests"
+              "seps/2322-MRTR",
+              "seps/2549-TTL-for-list-results",
+              "seps/2575-stateless-mcp"
+            ]
+          },
+          {
+            "group": "In-Review",
+            "pages": [
+              "seps/2468-recommend-issuer-claim-for-auth"
             ]
           },
           {
-            "group": "Approved",
+            "group": "Draft",
             "pages": [
-              "seps/2322-MRTR"
+              "seps/2106-json-schema-2020-12",
+              "seps/2164-resource-not-found-error",
+              "seps/2484-conformance-tests-required-for-final-seps",
+              "seps/2596-spec-feature-lifecycle-and-deprecation"
             ]
           }
         ]
@@ -667,6 +688,10 @@
       "source": "/docs/extensions/apps",
       "destination": "/extensions/apps/overview"
     },
+    {
+      "source": "/docs/extensions/tasks",
+      "destination": "/extensions/tasks/overview"
+    },
     {
       "source": "/community/seps",
       "destination": "/seps"

docs/extensions/overview.mdx

@@ -51,6 +51,12 @@ Official extensions live inside the [Model Context Protocol GitHub organization]
 
 To get started building MCP Apps, see the [quickstart guide](/extensions/apps/build#getting-started) or read the full [MCP Apps documentation](https://apps.extensions.modelcontextprotocol.io/api/documents/Quickstart.html).
 
+### MCP Tasks
+
+| Extension                               | Description                                                                                                   |
+| --------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| [MCP Tasks](/extensions/tasks/overview) | Asynchronous task execution for long-running operations, with polling, mid-flight input, and durable handles. |
+
 ## Experimental Extensions
 
 Experimental extensions provide an incubation pathway for [Working Groups and Interest Groups](/community/working-interest-groups) to prototype ideas and collaborate on extension concepts before formal SEP submission.