fix(sidebar): add explicit order to all protocol pages so Performance sorts last

Author: marc0olo

docs/concepts/protocol/consensus.md

@@ -1,6 +1,8 @@
 ---
 title: "Consensus"
 description: "How ICP subnets reach agreement on message ordering through block making, notarization, and finalization."
+sidebar:
+  order: 2
 ---
 
 The consensus protocol allows every node in a subnet to agree on which messages to process and in what order. Each subnet runs its own independent instance of the protocol. The output of each consensus round is a single finalized block of ordered messages that every node then executes deterministically, producing the same state transition on each.

docs/concepts/protocol/execution.md

@@ -1,6 +1,8 @@
 ---
 title: "Execution Layer"
 description: "How ICP deterministically executes canister code using WebAssembly, deterministic time slicing, and concurrent execution."
+sidebar:
+  order: 4
 ---
 
 The execution layer is the topmost layer of the ICP core protocol stack. It is responsible for executing canister code after message routing has inducted messages into canister input queues. Code runs in a [WebAssembly](https://webassembly.org/) (Wasm) virtual machine deployed on every subnet node. Wasm bytecode executes deterministically and at near-native speed, both of which are essential properties for a replicated system.

docs/concepts/protocol/message-routing.md

@@ -1,6 +1,8 @@
 ---
 title: "Message Routing"
 description: "How ICP routes messages between canisters across subnets, certifies subnet state, and enables secure cross-subnet communication."
+sidebar:
+  order: 3
 ---
 
 Message routing is the lower of the two upper layers of the ICP protocol stack. It sits above consensus and below execution, orchestrating the flow of messages from finalized blocks into canister input queues, triggering execution, routing the resulting inter-canister messages, and certifying subnet state.

docs/concepts/protocol/peer-to-peer.md

@@ -1,6 +1,8 @@
 ---
 title: "Peer-to-Peer Layer"
 description: "How ICP nodes broadcast artifacts and exchange protocol messages using the Abortable Broadcast primitive and QUIC transport."
+sidebar:
+  order: 1
 ---
 
 The peer-to-peer (P2P) layer is the bottommost layer in the ICP protocol stack. It is responsible for secure and reliable communication between the nodes of a subnet, providing the foundation on which all higher protocol layers depend.

docs/concepts/protocol/state-synchronization.md

@@ -1,6 +1,8 @@
 ---
 title: "State Synchronization"
 description: "How ICP nodes join or re-join a subnet by downloading certified checkpoints instead of replaying the full block history."
+sidebar:
+  order: 5
 ---
 
 State synchronization allows nodes to join a running subnet or recover from downtime without replaying every message ever executed. Instead, the protocol creates periodic certified checkpoints that capture a complete snapshot of the subnet state. A node that needs to catch up downloads a recent checkpoint and replays only the blocks produced since that checkpoint.