Document why a node cannot change its own address A name is pinned to the address it first announced, and the reason is worth stating rather than leaving as a surprising refusal: the hub sends a person's token to whatever address a node gave it.
Bring the wiki up to the current warden Installing by name works now, so the pages say so instead of explaining why it does not. Adds what the fleet gained since they were written: pool and listeners across every node, a name two machines both hold, --node forwarding on register, release and heartbeat, the dashboard's fleet mode, and the new heartbeat command. Records that forwarding takes a person's token rather than the cluster one, and why. Also that the dashboard shows this machine's ports with no warden running at all, which was the last place the two ways of asking the same question still disagreed.
Document the fleet-wide view warden ls --all, warden get node/service, and the two new endpoints. Also corrects the token model: the cluster token now opens read endpoints too, because a hub asking its nodes what they hold is exactly that. The pages said reading took the human token, which is no longer true.
Write the wiki Nine pages: what warden is, how to install it, running it on one machine, seeing and freeing ports without a server, running a cluster, and three reference pages. Plus a troubleshooting page built around the messages warden actually prints, so a reader can search for what they saw.