The colour and the words are both settable, one event at a time
Thirteen events, three scopes, and what each one actually looks like
The firewall: four backends, the rollback, and what a rule from the registry may never do
Bring the wiki up to 0.2.0: events, webhooks, projects, proxy export, groups
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.
Document setup, settings, and the Python client Configuration opened with fifteen environment variables and a .env in whatever directory the process started in, which stopped being sensible advice the moment the command could be installed globally. It now opens with `warden setup`, and explains the source order rather than pretending there is only one. The Python client had a table of method names on the API page and nothing that showed anyone how to use it. It gets a page: asking for a port at startup, finding a neighbour, leases and heartbeats, every method, what comes back, which exception means what, and reading the machine with no warden running at all.
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.
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.