docs(ha): fix RPC endpoints, init ordering, and snap_count CLI flag

Replace incorrect CometBFT RPC calls (port 26657/status) with the
actual ev-node HTTP API (port 7331 /health/ready, /raft/node) and
EVM execution layer (cast block latest) throughout both guides.

Align single-to-ha Step 2 init ordering with cluster-setup: create
passphrase file before evm init so the signer key is encrypted from
the start, and pass --evnode.node.aggregator and passphrase_file flags.

Fix Step 9a fallback kill in single-to-ha to use mapfile cardinality
check, matching the pattern already applied in cluster-setup.

Add --evnode.raft.snap_count=3 to the CLI start example to match
the YAML config block.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: auricom

docs/guides/ha/cluster-setup.md

@@ -231,6 +231,7 @@ Start all five nodes as close together as possible. The order does not matter bu
   --evnode.raft.send_timeout="50ms" \
   --evnode.raft.trailing_logs=18000 \
   --evnode.raft.snapshot_threshold=5000 \
+  --evnode.raft.snap_count=3 \
   --evnode.p2p.listen_address="/ip4/0.0.0.0/tcp/26656" \
   --evnode.p2p.peers="/ip4/10.0.0.2/tcp/26656/p2p/<PEER_ID_NODE_2>,/ip4/10.0.0.3/tcp/26656/p2p/<PEER_ID_NODE_3>,/ip4/10.0.0.4/tcp/26656/p2p/<PEER_ID_NODE_4>,/ip4/10.0.0.5/tcp/26656/p2p/<PEER_ID_NODE_5>" \
   --evnode.signer.passphrase_file=/etc/ev-node/passphrase \
@@ -262,24 +263,37 @@ INF raft: entering follower state  leader=node-1
 INF block applied from raft log    height=1 hash=0xabc...
 ```
 
+### Check node health
+
+Verify each node's HTTP API is responding:
+
+```bash
+# ev-node exposes its health endpoint on port 7331 by default
+curl http://10.0.0.1:7331/health/ready
+
+# Check which node is the current leader
+curl http://10.0.0.1:7331/raft/node | jq '{node_id, is_leader}'
+```
+
 ### Check block production
 
-Query the RPC endpoint of any node to confirm blocks are being produced:
+For EVM chains, query the execution layer to confirm blocks are being produced:
 
 ```bash
-curl http://10.0.0.1:26657/status | jq '.result.sync_info.latest_block_height'
+# Run from any node; the height should increase each time
+cast block latest --rpc-url http://10.0.0.1:8545
 ```
 
-Increment a few seconds and check again — the height should be increasing.
+Repeat after a few seconds — the block number should be increasing.
 
 ### Verify all nodes are synced
 
-Query each node; all five should report the same `latest_block_height` (or within 1–2 blocks of each other):
+Query each node; all five should report the same block height (or within 1–2 blocks of each other):
 
 ```bash
 for ip in 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5; do
   echo -n "$ip: height="
-  curl -s http://$ip:26657/status | jq -r '.result.sync_info.latest_block_height'
+  cast block latest --rpc-url http://$ip:8545 | jq -r '.number'
 done
 ```
 

docs/guides/ha/single-to-ha.md

@@ -63,11 +63,20 @@ On each of the four new machines, install the same ev-node binary version as the
 ./evm version
 ```
 
+Create the passphrase file before initializing so the signer key is encrypted from the start:
+
+```bash
+# On each new node
+sudo mkdir -p /etc/ev-node
+echo -n "<YOUR_PASSPHRASE>" | sudo tee /etc/ev-node/passphrase > /dev/null
+sudo chmod 600 /etc/ev-node/passphrase
+```
+
 Initialize each new node's home directory:
 
 ```bash
-# On each new node — do NOT pass --evnode.node.aggregator here yet
-./evm init
+# On each new node
+./evm init --evnode.node.aggregator=true --evnode.signer.passphrase_file /etc/ev-node/passphrase
 ```
 
 ---
@@ -122,8 +131,8 @@ rsync -avz ~/.evm/data/ user@10.0.0.5:~/.evm/data/
 After the copy, note the **latest block height** — this is your reference point:
 
 ```bash
-# Note the height before shutdown
-cast block --rpc-url http://<EV_RETH_IP>:<EV_RETH_TCP>
+# Note the height before shutdown — replace 8545 with your EVM RPC port
+cast block latest --rpc-url http://10.0.0.1:8545 | jq -r '.number'
 ```
 
 **Restart the existing sequencer now** so the chain keeps producing blocks while you prepare the remaining nodes (Steps 6–8). The chain will run uninterrupted until the planned cutover in Step 9.
@@ -239,7 +248,17 @@ This is the planned maintenance window. The chain pauses block production from w
 
 ```bash
 # On node-1 (existing sequencer)
-systemctl stop ev-node    # or kill -SIGTERM $(pgrep evm)
+# Preferred: use systemd if the node runs as a service
+sudo systemctl stop ev-node
+
+# Fallback: stop the process directly
+mapfile -t PIDS < <(pgrep -f "evm start")
+if [ "${#PIDS[@]}" -ne 1 ]; then
+  echo "Expected exactly 1 evm PID, found ${#PIDS[@]}: ${PIDS[*]}"
+  exit 1
+fi
+echo "Stopping PID ${PIDS[0]}"
+kill -SIGTERM "${PIDS[0]}"
 ```
 
 Confirm it has stopped:
@@ -310,14 +329,14 @@ INF block applied from raft log  height=<N+1>
 
 ### Verify block height continuity
 
-The new cluster must continue from exactly where the old sequencer left off. Query the RPC:
+The new cluster must continue from exactly where the old sequencer left off. Query the EVM execution layer:
 
 ```bash
 # From the existing sequencer's last known height (noted in step 5)
 LAST_HEIGHT=<height-before-shutdown>
 
-# Query node-1 (or any node)
-NEW_HEIGHT=$(cast block --rpc-url http://<EV_RETH_IP>:<EV_RETH_TCP>)
+# Query node-1 (or any node) — replace 8545 with your EVM RPC port
+NEW_HEIGHT=$(cast block latest --rpc-url http://10.0.0.1:8545 | jq -r '.number')
 
 echo "Last old height: $LAST_HEIGHT"
 echo "New cluster height: $NEW_HEIGHT"
@@ -330,7 +349,7 @@ echo "New cluster height: $NEW_HEIGHT"
 ```bash
 for ip in 10.0.0.1 10.0.0.2 10.0.0.3 10.0.0.4 10.0.0.5; do
   echo -n "$ip: height="
-  curl -s http://$ip:26657/status | jq -r '.result.sync_info.latest_block_height'
+  cast block latest --rpc-url http://$ip:8545 | jq -r '.number'
 done
 ```