docs: an install has no way to try the admin api on a laptop #23

The admin interface needs a public host name and a real certificate before it answers anything: port 80 on that name redirects, the session cookie is Secure and carries the __Host- prefix, and the service refuses any Host but the one it was configured with. So there is no localhost walkthrough — trying it locally takes a name that resolves, a certificate that browser or curl will accept, and a host override.

The README now says this plainly rather than letting a reader discover it, which was the finding. What it does not do is offer a way: a documented local-CA recipe, or a development mode that accepts a name without TLS, are both plausible and both have costs — the second is a switch that must never be reachable on a real install.

Worth a decision before anyone writes a quickstart that cannot be followed.