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 updates and rolling them across a fleet A page of its own, plus the settings, the endpoints, and a section of troubleshooting built around the messages an update actually prints. States plainly why the hub sends an intent rather than a command, and that restarting the service is the operator's command's job.