Hoist versioning/revisions info to top level

Author: jspahrsummers

docs/specification/2024-11-05/_index.md

@@ -1,5 +1,5 @@
 ---
-linkTitle: Revision 2024-11-05
+linkTitle: 2024-11-05 (Final)
 title: Model Context Protocol specification
 cascade:
   type: docs

docs/specification/2024-11-05/revisions/2024-11-05.md

@@ -1,5 +1,5 @@
 ---
-linkTitle: Revision 2025-03-26
+linkTitle: 2025-03-26 (Latest)
 title: Model Context Protocol specification
 cascade:
   type: docs

docs/specification/2024-11-05/revisions/_index.md

@@ -7,17 +7,27 @@ weight: 80
 The Model Context Protocol uses string-based version identifiers following the format
 `YYYY-MM-DD`, to indicate the last date backwards incompatible changes were made.
 
-The current protocol version is **2024-11-05**. [See all
-revisions]({{< ref "/specification/2024-11-05/revisions" >}}).
-
 {{< callout type="info" >}} The protocol version will _not_ be incremented when the
 protocol is updated, as long as the changes maintain backwards compatibility. This allows
 for incremental improvements while preserving interoperability. {{< /callout >}}
 
+## Revisions
+
+Revisions may be marked as:
+
+- **Draft**: in-progress specifications, not yet ready for consumption.
+- **Current**: the current protocol version, which is ready for use and may continue to
+  receive backwards compatible changes.
+- **Final**: past, complete specifications that will not be changed.
+
+The **current** protocol version is [**2025-03-26**]({{< ref "2025-03-26" >}}).
+
+## Negotiation
+
 Version negotiation happens during
-[initialization]({{< ref "/specification/2024-11-05/basic/lifecycle#initialization" >}}).
-Clients and servers **MAY** support multiple protocol versions simultaneously, but they
-**MUST** agree on a single version to use for the session.
+[initialization]({{< ref "2025-03-26/basic/lifecycle#initialization" >}}). Clients and
+servers **MAY** support multiple protocol versions simultaneously, but they **MUST**
+agree on a single version to use for the session.
 
 The protocol provides appropriate error handling if version negotiation fails, allowing
 clients to gracefully terminate connections when they cannot find a version compatible