Iter 31 — parallels the iter 25 WebSocket sync docs with the matching
HTTP surface. Adds 2 rows to the REST API table + a worked "Get fleet
mesh state" example showing the sample JSON for two C6 boards (leader
+ follower) so operators see the leader's near-zero offset alongside
the follower's §A0.10-measured 1.16 s delta in the same response.
Also covers the 404 paths the iter 29 handlers actually emit:
- {"error": "unknown_node", "node_id": N}
- {"error": "no_sync", "node_id": N, "hint": "..."}
The "hint" field is verbatim so operators searching docs for the
string they see in curl output land here.
Links back to the existing "Per-node mesh sync (ADR-110)" section
for field meanings instead of duplicating them — one source of truth.
Co-Authored-By: claude-flow <ruv@ruv.net>
473c5d11db