Promote SEPs to a top-level docs tab

- Move docs/community/seps/ to docs/seps/
- Update render-seps.ts to generate a standalone "SEPs" tab instead of a
  group under Community, inserted before the Community tab
- Add redirects from /community/seps[/:slug*] to /seps[/:slug*]
- Update internal links in extensions docs to point to new /seps/ paths

:house: Remote-Dev: homespace

Author: localden

docs/community/seps/index.mdx

@@ -370,6 +370,42 @@
           "registry/terms-of-service"
         ]
       },
+      {
+        "tab": "SEPs",
+        "pages": [
+          "seps/index",
+          {
+            "group": "Final",
+            "pages": [
+              "seps/414-request-meta",
+              "seps/932-model-context-protocol-governance",
+              "seps/973-expose-additional-metadata-for-implementations-res",
+              "seps/985-align-oauth-20-protected-resource-metadata-with-rf",
+              "seps/986-specify-format-for-tool-names",
+              "seps/990-enable-enterprise-idp-policy-controls-during-mcp-o",
+              "seps/991-enable-url-based-client-registration-using-oauth-c",
+              "seps/994-shared-communication-practicesguidelines",
+              "seps/1024-mcp-client-security-requirements-for-local-server-",
+              "seps/1034--support-default-values-for-all-primitive-types-in",
+              "seps/1036-url-mode-elicitation-for-secure-out-of-band-intera",
+              "seps/1046-support-oauth-client-credentials-flow-in-authoriza",
+              "seps/1302-formalize-working-groups-and-interest-groups-in-mc",
+              "seps/1303-input-validation-errors-as-tool-execution-errors",
+              "seps/1319-decouple-request-payload-from-rpc-methods-definiti",
+              "seps/1330-elicitation-enum-schema-improvements-and-standards",
+              "seps/1577--sampling-with-tools",
+              "seps/1613-establish-json-schema-2020-12-as-default-dialect-f",
+              "seps/1686-tasks",
+              "seps/1699-support-sse-polling-via-server-side-disconnect",
+              "seps/1730-sdks-tiering-system",
+              "seps/1850-pr-based-sep-workflow",
+              "seps/1865-mcp-apps-interactive-user-interfaces-for-mcp",
+              "seps/2085-governance-succession-and-amendment",
+              "seps/2133-extensions"
+            ]
+          }
+        ]
+      },
       {
         "tab": "Community",
         "pages": [
@@ -391,42 +427,6 @@
               "community/antitrust"
             ]
           },
-          {
-            "group": "SEPs",
-            "pages": [
-              "community/seps/index",
-              {
-                "group": "Final",
-                "pages": [
-                  "community/seps/414-request-meta",
-                  "community/seps/932-model-context-protocol-governance",
-                  "community/seps/973-expose-additional-metadata-for-implementations-res",
-                  "community/seps/985-align-oauth-20-protected-resource-metadata-with-rf",
-                  "community/seps/986-specify-format-for-tool-names",
-                  "community/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o",
-                  "community/seps/991-enable-url-based-client-registration-using-oauth-c",
-                  "community/seps/994-shared-communication-practicesguidelines",
-                  "community/seps/1024-mcp-client-security-requirements-for-local-server-",
-                  "community/seps/1034--support-default-values-for-all-primitive-types-in",
-                  "community/seps/1036-url-mode-elicitation-for-secure-out-of-band-intera",
-                  "community/seps/1046-support-oauth-client-credentials-flow-in-authoriza",
-                  "community/seps/1302-formalize-working-groups-and-interest-groups-in-mc",
-                  "community/seps/1303-input-validation-errors-as-tool-execution-errors",
-                  "community/seps/1319-decouple-request-payload-from-rpc-methods-definiti",
-                  "community/seps/1330-elicitation-enum-schema-improvements-and-standards",
-                  "community/seps/1577--sampling-with-tools",
-                  "community/seps/1613-establish-json-schema-2020-12-as-default-dialect-f",
-                  "community/seps/1686-tasks",
-                  "community/seps/1699-support-sse-polling-via-server-side-disconnect",
-                  "community/seps/1730-sdks-tiering-system",
-                  "community/seps/1850-pr-based-sep-workflow",
-                  "community/seps/1865-mcp-apps-interactive-user-interfaces-for-mcp",
-                  "community/seps/2085-governance-succession-and-amendment",
-                  "community/seps/2133-extensions"
-                ]
-              }
-            ]
-          },
           {
             "group": "Roadmap",
             "pages": [
@@ -569,6 +569,14 @@
     {
       "source": "/docs/extensions/apps",
       "destination": "/extensions/apps/overview"
+    },
+    {
+      "source": "/community/seps",
+      "destination": "/seps"
+    },
+    {
+      "source": "/community/seps/:slug*",
+      "destination": "/seps/:slug*"
     }
   ],
   "contextual": {

docs/docs.json

@@ -147,7 +147,7 @@ Check the [client matrix](/extensions/client-matrix) for current implementation
   <Card
     title="SEP-990"
     icon="file-lines"
-    href="/community/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o"
+    href="/seps/990-enable-enterprise-idp-policy-controls-during-mcp-o"
   >
     Original proposal: Enable Enterprise IdP Policy Controls
   </Card>

docs/extensions/auth/enterprise-managed-authorization.mdx

@@ -69,7 +69,7 @@ To promote an experimental extension to official status, it goes through the sta
 
 ## Creating Extensions
 
-The lifecycle for official extensions follows a SEP-based process. For full details, see [SEP-2133: Extensions](/community/seps/2133-extensions).
+The lifecycle for official extensions follows a SEP-based process. For full details, see [SEP-2133: Extensions](/seps/2133-extensions).
 
 1. **Propose**: Create a SEP in the main MCP repository using the [standard SEP guidelines](/community/sep-guidelines) with type **Extensions Track**.
 2. **Implement**: Build at least one reference implementation in an official SDK — this is required before the SEP can be reviewed.