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.