Module services 

The local services of a repository: what this executable serves, where, and whether anything is answering there now.

Paths are not written here. Each descriptor names the constant that already decides its route — crate::ui::PREFIX, crate::cockpit::PREFIX, crate::capability::HttpExposure::PREFIX, crate::http::swagger::SWAGGER_PATH, crate::web::discover::DOCS_MOUNT and the rest of what crate::http::openapi::infrastructure_routes lists — so a route that moves moves here too, and every_infrastructure_route_is_described fails the build if a new one is added without a name for it. The base address is the shared server’s lease, which is where a running server publishes it and the only place it is true.

Availability is decided by a connection attempt with a hard budget and no name resolution (super::probe); a service that did not answer in time is unknown, never “down”.

Constants

PROBE_BUDGET

How long the connection attempt to a published address may take. Loopback either answers in microseconds or is not there; anything slower is a machine under load, and the snapshot says unknown rather than making a shell prompt wait for it.

Functions

join

A base address and a route, joined without a doubled or missing slash.

published_url

The address the repository’s shared server published, from its lease. Reads one small file and contacts nothing; crate::lease::probe is the version that checks whether the server is really there, and it costs an HTTP round trip.

resolve

The services of the repository at root, with the address a running server published.