roadmap: move WebTransport to Done

ROADMAP.md

@@ -20,7 +20,6 @@ third-party ownership of data.
         - [📮 Offline message queue / postbox](#📮-offline-message-queue--postbox)
         - [🤖 libp2p as a WASM library](#🤖-libp2p-as-a-wasm-library)
     - [Evolve](#evolve)
-        - [✈️ WebTransport](#✈️-webtransport)
         - [⏱ Full Observability](#⏱-full-observability)
         - [🧪 Automated compatibility testing](#🧪-automated-compatibility-testing)
         - [Stream Migration Protocol](#stream-migration-protocol)
@@ -39,6 +38,7 @@ third-party ownership of data.
         - [🏹 RPC and other common node communication patterns](#🏹-rpc-and-other-common-node-communication-patterns)
     - [Done](#done)
         - [🕸 Hole punching on TCP and QUIC](#🕸-hole-punching-on-tcp-and-quic)
+        - [✈️ WebTransport](#✈️-webtransport)
 
 ## Visionary
 
@@ -227,26 +227,6 @@ model.
 
 This is the stuff pushing the existing libp2p stack forward.
 
-### ✈️ WebTransport
-
-**Status**: In progress
-
-**What?** WebTransport is a browser-API offering low-latency, bidirectional
-client-server messaging running on top of QUIC. The browser API allows the
-establishment of connections to servers that don't have a TLS certificate
-signed by a certificate authority if the hash of the certificate is known in
-advance.
-
-**Why?** This allows libp2p nodes running in the browser (using js-libp2p) to
-connect to the rest of the libp2p network.
-
-**Links:**
-
-- [IETF draft](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/)
-- [W3C Browser API](https://w3c.github.io/webtransport/)
-- [libp2p spec discussion](https://github.com/libp2p/specs/pull/404)
-- [webtransport-go](https://github.com/marten-seemann/webtransport-go/)
-
 ### ⏱ Full Observability
 
 **What?** libp2p should expose a wide set of metrics, making it easy to
@@ -670,3 +650,24 @@ to the rest of the system.
   vision](https://github.com/libp2p/specs/blob/master/connections/hole-punching.md).
 
 - [NAT traversal tracking issue](https://github.com/libp2p/specs/issues/312).
+
+
+### ✈️ WebTransport
+
+**Status**: In progress
+
+**What?** WebTransport is a browser-API offering low-latency, bidirectional
+client-server messaging running on top of QUIC. The browser API allows the
+establishment of connections to servers that don't have a TLS certificate
+signed by a certificate authority if the hash of the certificate is known in
+advance.
+
+**Why?** This allows libp2p nodes running in the browser (using js-libp2p) to
+connect to the rest of the libp2p network.
+
+**Links:**
+
+- [IETF draft](https://datatracker.ietf.org/doc/draft-ietf-webtrans-http3/)
+- [W3C Browser API](https://w3c.github.io/webtransport/)
+- [libp2p spec discussion](https://github.com/libp2p/specs/pull/404)
+- [webtransport-go](https://github.com/marten-seemann/webtransport-go/)